How to fix Sql Server Extension Service from terminating unexpectedly

Question

How to fix Sql Server Extension Service from terminating unexpectedly

Santos, Carlos 0

We have two SQL Server 2017 database servers running on Windows Server 2019 Datacenter.

Servers were setup with Always On High Availability (AOHA).

A month ago we started seeing the following error messages in Event Viewer. Both errors show up simultaneously.

User's image

What may be causing this service to failed and restart every 5-10 minutes?

LiHongMSFT-4306 31,566 Reputation points

2024-10-30T02:46:43.63+00:00

Hi @Santos, Carlos

Please review detailed error messages in the SQL Server error log and Windows Event Logs.
Santos, Carlos 0 Reputation points

2024-10-30T18:38:10.2566667+00:00
What would you recommend doing to fix this?

Log Name: Application

Source: .NET Runtime

Date: 10/30/2024 11:16:00 AM

Event ID: 1026

Task Category: None

Level: Error

Keywords: Classic

User: N/A

Computer: ERPDBPROD01

Description:

Application: SqlServerExtension.Service.exe

CoreCLR Version: 8.0.724.31311

.NET Version: 8.0.7

Description: The process was terminated due to an unhandled exception.

Exception Info: System.ArgumentNullException: Value cannot be null. (Parameter 'publicSettings')

at System.ArgumentNullException.Throw(String paramName)

at System.ArgumentNullException.ThrowIfNull(Object argument, String paramName)

at Microsoft.SqlServer.Management.BackgroundJobService.Workers.BackgroundJobEngineWorker.StartAsync(CancellationToken stoppingToken)

at Microsoft.Extensions.Hosting.Internal.Host.<StartAsync>b__15_1(IHostedService service, CancellationToken token)

at Microsoft.Extensions.Hosting.Internal.Host.ForeachServiceT

at Microsoft.Extensions.Hosting.Internal.Host.StartAsync(CancellationToken cancellationToken)

at Microsoft.Extensions.Hosting.HostingAbstractionsHostExtensions.RunAsync(IHost host, CancellationToken token)

at Microsoft.Extensions.Hosting.HostingAbstractionsHostExtensions.RunAsync(IHost host, CancellationToken token)

at Microsoft.SqlServer.Management.SqlServerExtension.Service.ServiceEntry.Main(String[] args)

at Microsoft.SqlServer.Management.SqlServerExtension.Service.ServiceEntry.<Main>(String[] args)

Event Xml:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">

<System>

<Provider Name=".NET Runtime" /> <EventID Qualifiers="0">1026</EventID> <Level>2</Level> <Task>0</Task> <Keywords>0x80000000000000</Keywords> <TimeCreated SystemTime="2024-10-30T18:16:00.251965000Z" /> <EventRecordID>17990893</EventRecordID> <Channel>Application</Channel> <Computer>ERPDBPROD01</Computer> <Security />

</System>

<EventData>

<Data>Application: SqlServerExtension.Service.exe

CoreCLR Version: 8.0.724.31311

.NET Version: 8.0.7

Description: The process was terminated due to an unhandled exception.

Exception Info: System.ArgumentNullException: Value cannot be null. (Parameter 'publicSettings')

at System.ArgumentNullException.Throw(String paramName)

at System.ArgumentNullException.ThrowIfNull(Object argument, String paramName)

at Microsoft.SqlServer.Management.BackgroundJobService.Workers.BackgroundJobEngineWorker.StartAsync(CancellationToken stoppingToken)

at Microsoft.Extensions.Hosting.Internal.Host.<StartAsync>b__15_1(IHostedService service, CancellationToken token)

at Microsoft.Extensions.Hosting.Internal.Host.ForeachServiceT

at Microsoft.Extensions.Hosting.Internal.Host.StartAsync(CancellationToken cancellationToken)

at Microsoft.Extensions.Hosting.HostingAbstractionsHostExtensions.RunAsync(IHost host, CancellationToken token)

at Microsoft.Extensions.Hosting.HostingAbstractionsHostExtensions.RunAsync(IHost host, CancellationToken token)

at Microsoft.SqlServer.Management.SqlServerExtension.Service.ServiceEntry.Main(String[] args)

at Microsoft.SqlServer.Management.SqlServerExtension.Service.ServiceEntry.<Main>(String[] args)

</Data>

</EventData>

</Event>

2 answers

Your answer

LiHongMSFT-4306 31,566 Reputation points

2024-10-30T02:46:43.63+00:00

Hi @Santos, Carlos

Please review detailed error messages in the SQL Server error log and Windows Event Logs.

Answer 1

Khaled Salameh 10

Faced a similar issue, the Service was unable to find the ".SETTINGS" file, this file usually exists in :

C:\Packages\Plugins\Microsoft.AzureData.WindowsAgent.SqlServer\VERSION\RuntimeSettings\1.Settings

In my case, it was in:

C:\Packages\Plugins\Microsoft.AzureData.WindowsAgent.SqlServer\1.1.2769.203\RuntimeSettings\1.Settings

And for some reason, the SqlServerExtension.Service.exe Service was trying to load an older version 1.1.2735.199.

You can identify which version is causing the error by stopping the service "Microsoft Sql Server Extension Service" , then going to "C:\Program Files\Sql Server Extension" using CMD and running SqlServerExtension.Service.exe., when doing so, it should point out which version it is trying to load, see this screenshot:

User's image

As you can see, it is trying to load from Agent Version ending with .199 while the latest is 203, I copied the files from 203 to 199 folder and it worked!

Henrik Dupont 0 Reputation points

2024-11-27T08:41:30.2166667+00:00

You can also check the file HandlerEnvironment.json in "C:\Program Files\Sql Server Extension" where the paths are configured.
TylerH 61 Reputation points

2025-05-23T18:42:56.8266667+00:00

We only have a .199 folder, no .203 folder.

This was caused when we upgraded SQL 2014 from the RTM version to SQL 2014 SP3 CU4 in one go. Most likely there's some migration step that Microsoft forgot to include in one of their updates or service packs that caused this.

Answer 2

Erland Sommarskog 121.4K MVP Volunteer Moderator

First of all, ask yourself what you use the extension for and if it is needed. I know I have it installed on one of my lab machines, because I played with Purview. But maybe the extension is good for other services as well.

If you are using the service for something, does that function normally?

If you don't know for what purpose you are using it, a simple solution is to uninstall it.

Else, I guess you need to open a support case. It is obviously a bug in the product.

Share via

How to fix Sql Server Extension Service from terminating unexpectedly

2 answers

Your answer