mssql: SQL Tools Service component could not start #17739

sfannfcs · 2023-07-11T17:23:48Z

MSSQL Extension Version:1.19.1
VSCode Version:1.79.2
OS Version:Windows 10

Steps to Reproduce:

1.Start VSC
2.

sfannfcs · 2023-07-12T16:14:29Z

error messages we got:
[Info - 9:12:07 AM] Connection to server got closed. Server will restart.
[Info - 9:12:08 AM] Connection to server got closed. Server will restart.
[Info - 9:12:09 AM] Connection to server got closed. Server will restart.
[Info - 9:12:10 AM] Connection to server got closed. Server will restart.
[Error - 9:12:11 AM] Connection to server got closed. Server will not be restarted.

The AzureResourceProvider server crashed 5 times in the last 3 minutes. The server will not be restarted.

mssql: SQL Tools Service component could not start.

mister0822 · 2023-07-14T17:31:10Z

I have this issue as well. Does anyone have any steps to help identify what is causing the SQL Tools Service to not start? The issue is not present on 1.12.0. The service works successfully. This error is displayed with every version after, including the current. I have not found any clues in the extension log files.

cheenamalhotra · 2023-07-14T17:49:10Z

Can you wrap up extension logs by following below steps:

Enable verbose logs by setting: mssql.tracingLevel to All
Reload/Restart VS Code
Let extension load and STS component fail.
Run command: Developer: Open Logs Folder
Navigate to window (latest copy) > exthost
Copy 2 folders from here:
- ms-mssql.mssql
- output_logging_xxx (latest - clean up any unrelated logs from here if needed)

Upload the 2 folders here along with version info.

mister0822 · 2023-07-17T16:58:22Z

Thank you for the response. I have followed the listed steps. ms-mssql.mssql does not exist. Attached is the output_logging folder.
logs_7_17_2023.zip

Before I sent this, I let it upgrade to 1.19.1. VSCode is 1.80.0

clouddots-ben · 2023-07-18T00:03:30Z

I'm having a similar issue. I'm on Windows 11 and installed 1.19.1. but was unable to make a new connection and received error command 'mssql.addObjectExplorer' not found. I uninstalled/removed files from /.vscode/extensions removed the cache from roaming and restarted the machine. Same error. After some googling, I realized that the 64 bit installation of 1.19.1 didn't have the sqltoolsservice included. I tried manually added the service and then I tried installing the x84 version. It included the sqltoolsservice, but I still had the same error of command not found.

damonripper · 2023-07-20T19:08:18Z

Same issue. I see following in output window

Failed to load the dll from [c:\Users\dclark\.vscode\extensions\ms-mssql.mssql-1.19.1\sqltoolsservice\4.7.1.6\Windows\coreclr.dll], HRESULT: 0x800700C1
[Info  - 2:15:26 PM] Connection to server got closed. Server will restart.
Failed to load the dll from [c:\Users\dclark\.vscode\extensions\ms-mssql.mssql-1.19.1\sqltoolsservice\4.7.1.6\Windows\coreclr.dll], HRESULT: 0x800700C1
[Info  - 2:15:26 PM] Connection to server got closed. Server will restart.
Failed to load the dll from [c:\Users\dclark\.vscode\extensions\ms-mssql.mssql-1.19.1\sqltoolsservice\4.7.1.6\Windows\coreclr.dll], HRESULT: 0x800700C1
[Info  - 2:15:26 PM] Connection to server got closed. Server will restart.
Failed to load the dll from [c:\Users\dclark\.vscode\extensions\ms-mssql.mssql-1.19.1\sqltoolsservice\4.7.1.6\Windows\coreclr.dll], HRESULT: 0x800700C1
[Info  - 2:15:27 PM] Connection to server got closed. Server will restart.
Failed to load the dll from [c:\Users\dclark\.vscode\extensions\ms-mssql.mssql-1.19.1\sqltoolsservice\4.7.1.6\Windows\coreclr.dll], HRESULT: 0x800700C1
[Error - 2:15:27 PM] Connection to server got closed. Server will not be restarted.

mister0822 · 2023-07-24T17:25:57Z

Read a thread where 1.18.0 might work better. Confirmed that 1.18.0 gives the same error as [sfannfcs] posted above.

mister0822 · 2023-07-26T16:23:46Z

I see the tag needs more info. Just confirming if there is anything further I can do or provide. Thank you.

mister0822 · 2023-08-02T18:33:30Z

Thanks @cheenamalhotra. We will re-test once the fix above is included in a new release.

mister0822 · 2023-08-08T20:49:42Z

Tested on 1.20.1 and the same issue persists. Output includes:

[Info - 2:17:46 AM] Connection to server got closed. Server will restart.
[Info - 2:17:47 AM] Connection to server got closed. Server will restart.
[Info - 2:17:48 AM] Connection to server got closed. Server will restart.
[Info - 2:17:50 AM] Connection to server got closed. Server will restart.
[Error - 2:17:51 AM] Connection to server got closed. Server will not be restarted.

mssql: SQL Tools Service component could not start.

Source: SQL Server (mssql) (Extension)

EdCallahan · 2023-08-08T20:58:13Z

@mister0822 Do you have a proxy configured in your settings.json? If so, you could try and remove those lines; VSCode will rely on your OS proxy settings in most cases.

See:
#17772 (comment)
https://code.visualstudio.com/docs/setup/network#_proxy-server-support

Only thinking it might be proxy related since 1.20.1 was supposed to help you, and that was an attempted fix re proxy issues.

sfannfcs · 2023-08-08T21:34:11Z

With mssql extension 1.20.1, I have tried all options of proxy support (on, off, fallback, override). exact same error I got:

[Info - 2:28:16 PM] Connection to server got closed. Server will restart.
[Info - 2:28:17 PM] Connection to server got closed. Server will restart.
[Info - 2:28:18 PM] Connection to server got closed. Server will restart.
[Info - 2:28:18 PM] Connection to server got closed. Server will restart.
[Error - 2:28:19 PM] Connection to server got closed. Server will not be restarted.

cheenamalhotra · 2023-08-08T22:18:30Z

@sfannfcs

Does manual downloading help resolve the issue?

Download https://github.com/Microsoft/sqltoolsservice/releases/download/4.8.1.2/microsoft.sqltools.servicelayer-win-x64-net7.0.zip
Extract the content to C:\Users\<user>\.vscode\extensions\ms-mssql.mssql-1.20.1\sqltoolsservice\4.8.1.2\Windows
Restart VS Code

sfannfcs · 2023-08-09T13:44:58Z

@sfannfcs

Does manual downloading help resolve the issue?

Download https://github.com/Microsoft/sqltoolsservice/releases/download/4.8.1.2/microsoft.sqltools.servicelayer-win-x64-net7.0.zip

Extract the content to C:\Users\<user>\.vscode\extensions\ms-mssql.mssql-1.20.1\sqltoolsservice\4.8.1.2\Windows

Restart VS Code

Thanks @cheenamalhotra,
the manual downloading didn't resolve the issue. I got the same error.

damonripper · 2023-08-09T14:02:51Z

Just wanted to report that I am no longer seeing the issue :)

cheenamalhotra · 2023-08-09T17:55:58Z

Thanks @cheenamalhotra, the manual downloading didn't resolve the issue. I got the same error.

Couple of thing to try (in order):

Is there any background process running on the machine that's stopping this extension to load? Try cleaning out any SQLTools/NodeJS related processes if they are running at all.. and restart machine.
Have you tried updating VS Code to latest 1.80?
Can you try installing .NET runtime if this helps?
Try another machine/VM? I wonder if vscode cache is just in a bad state on your machine..

mister0822 · 2023-08-09T23:05:16Z

@cheenamalhotra
I work with @sfannfcs and I am doing the same testing on a different VDI. All VDI machines have this issue. My laptop does not and all the versions of the extensions start properly. VS Code is 1.80. I don't see any processes conflicting, but starting to think this has to be the issue. I did not see any SQLTools/NodeJS related processes. I did try to install the .net runtime. I do see .NET errors in the windows application logs:

.NET runtime events with 1022 event ID, and the following event log message: Failed to CoCreate profiler.

This error appears over and over.

Thank you for your suggestions.

cheenamalhotra · 2023-08-10T17:51:34Z

That's interesting! How are these VDI machines hosted and what installer are you using to install VS Code (User/System/Zip)?
I just tested on a Hyper-V virtual machine (Windows 10) with user installer - and it worked fine without any issues.

Not sure if this applies to you, here're one solution I found that can be tried: https://www.ibm.com/docs/en/tcamfma/6.3.0?topic=workarounds-net-data-collector-event-1022

sfannfcs · 2023-08-11T15:15:06Z

@cheenamalhotra,
cc: @mister0822

Here is our VDI system info. I tried both VSC installers (user/system), both of them have the same issue.

I checked my VDI event log and did find the .NET Runtime issue (Event ID 1022) as mentioned in your link. Here is the error message from the event log: 'NET Runtime version 4.0.30319.0 - Loading profiler failed during CoCreateInstance. Profiler CLSID: '{DA7CFC47-3E35-4c4e-B495-534F93B28683}'. HRESULT: 0x80070241. Process ID (decimal): 11616. Message ID: [0x2504].'

I will try the workaround solution.

mister0822 · 2023-08-24T22:14:10Z

Any further information we can provide?

mister0822 · 2023-09-07T21:50:58Z

Just checking if there is new information.

Watertight-skaat · 2023-11-15T14:53:10Z

I'm now currently getting this.

Logs.zip

cheenamalhotra added the Needs More Info label Jul 14, 2023

cheenamalhotra added Bug Area - Acquisition Triage: Needed labels Jul 17, 2023

cheenamalhotra mentioned this issue Jul 31, 2023

getProxyAgentOptions error #17755

Closed

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

mssql: SQL Tools Service component could not start #17739

mssql: SQL Tools Service component could not start #17739

sfannfcs commented Jul 11, 2023

sfannfcs commented Jul 12, 2023

mister0822 commented Jul 14, 2023

cheenamalhotra commented Jul 14, 2023

mister0822 commented Jul 17, 2023 •

edited

Loading

clouddots-ben commented Jul 18, 2023

damonripper commented Jul 20, 2023

mister0822 commented Jul 24, 2023

mister0822 commented Jul 26, 2023

mister0822 commented Aug 2, 2023

mister0822 commented Aug 8, 2023

EdCallahan commented Aug 8, 2023 •

edited

Loading

sfannfcs commented Aug 8, 2023

cheenamalhotra commented Aug 8, 2023 •

edited

Loading

sfannfcs commented Aug 9, 2023

damonripper commented Aug 9, 2023

cheenamalhotra commented Aug 9, 2023

mister0822 commented Aug 9, 2023

cheenamalhotra commented Aug 10, 2023 •

edited

Loading

sfannfcs commented Aug 11, 2023

mister0822 commented Aug 24, 2023

mister0822 commented Sep 7, 2023

Watertight-skaat commented Nov 15, 2023 •

edited

Loading

mssql: SQL Tools Service component could not start #17739

mssql: SQL Tools Service component could not start #17739

Comments

sfannfcs commented Jul 11, 2023

sfannfcs commented Jul 12, 2023

mister0822 commented Jul 14, 2023

cheenamalhotra commented Jul 14, 2023

mister0822 commented Jul 17, 2023 • edited Loading

clouddots-ben commented Jul 18, 2023

damonripper commented Jul 20, 2023

mister0822 commented Jul 24, 2023

mister0822 commented Jul 26, 2023

mister0822 commented Aug 2, 2023

mister0822 commented Aug 8, 2023

EdCallahan commented Aug 8, 2023 • edited Loading

sfannfcs commented Aug 8, 2023

cheenamalhotra commented Aug 8, 2023 • edited Loading

sfannfcs commented Aug 9, 2023

damonripper commented Aug 9, 2023

cheenamalhotra commented Aug 9, 2023

mister0822 commented Aug 9, 2023

cheenamalhotra commented Aug 10, 2023 • edited Loading

sfannfcs commented Aug 11, 2023

mister0822 commented Aug 24, 2023

mister0822 commented Sep 7, 2023

Watertight-skaat commented Nov 15, 2023 • edited Loading

mister0822 commented Jul 17, 2023 •

edited

Loading

EdCallahan commented Aug 8, 2023 •

edited

Loading

cheenamalhotra commented Aug 8, 2023 •

edited

Loading

cheenamalhotra commented Aug 10, 2023 •

edited

Loading

Watertight-skaat commented Nov 15, 2023 •

edited

Loading