Could not start visual studio due to an error - StreamJsonRpc.ConnectionLostException

Dylan Baird 36

Good afternoon,

I am primarily a Linux user but am excited by some of the GUI features of Visual Studio. Unfortunately I am unable to open Visual Studio. I downloaded the most recent installer and was able to install it without trouble. It will not open and throws the exception mentioned in the title.

The only other information is that it states "The JSON-RPC connection with the remote party was lost before the request could complete."

I'm not sure what connection it is trying to initiate and I have no idea how to go about debugging the IDE... Through the installer I tried repairing the installation which did not work. I then tried uninstalling and deleting all associated files, restarting the computer, then re installing. That did not work either.

I noticeon Github that there are similar issues but they are marked as resolved.

I'm not quite sure where to ask this (so I try here), and I am at a loss of what to do next.

I appreciate any assistance,

Dylan

Anna Xiu-MSFT 31,081 Reputation points Microsoft External Staff

2021-03-15T02:57:42.287+00:00

Hi @Dylan Baird , which version of Visual Studio are you using? Please use the command: devenv /safemode to run your Visual Studio in safe mode. Besides, relaunch your Visual Studio as administrator to check if the error disappears.
Fred Bullmer 11 Reputation points

2021-05-04T18:26:34.483+00:00

I get the same error in 16.9.4, from a CMD as Administrator and /safemode.
Markus Pope 16 Reputation points

2021-05-05T23:01:38.997+00:00

@Anna Xiu-MSFT Same for me. Upgraded to 16.9.4 and I get the same problem described by others. See my additional info below as I found some info in servicehub\logs.
Markus Pope 16 Reputation points

2021-05-05T23:04:15.427+00:00

@Dylan Baird Please do me a favor and look in the %userappdata%\Temp\servicehub\logs folder and see if your logs are similar to mine, referencing a file called System.Numerics.Vectors. This is a file that the .net team has had trouble with because it was apparently versioned in a weird way. I've been trying to figure out where to add an assembly binding and can't seem to figure out where to put the binding redirect.
Markus Pope 16 Reputation points

2021-05-05T23:29:55+00:00

@Dylan Baird See below.
רונן גביאן 5 Reputation points

2023-03-13T09:38:12.18+00:00

Hi all,

Just got similar error message, the solution that worked for me was: closing the VS2022 and run it again as administrator.

It was all about permissions..

Wish you all good.
传彬孙 0 Reputation points

2023-05-13T19:25:05.59+00:00

execute gacutil /u Newtonsoft.Json
JW 10 Reputation points

2023-06-02T18:01:43.63+00:00

This is happening again with Visual Studio 2022 v17.6.2

8 answers

Der Abt 1 Reputation point

2021-07-12T11:30:16.073+00:00
Same for me with VS 2019 10.3. It does not start at all.

I tried EVERYTHING, including installing VS 2019 11.0 Preview -which also brings this error and does not start:
"Visual Studio konnte aufgrund eines Fehlers nicht gestartet werden.
StreamJsonRpc.ConnectionLostException:
Die JSON-RPC-Verbindung mit der Gegenseite ging verloren, bevor die Anforderung abgeschlossen werden konnte."

devenv /ResetSettings
devenv /SafeMode
devenv /Iforgotthisone
ot starting as administrator
did not fix it.

Repair Visual Studio

Install .Net 4.8 Development Components

Remove/Reinstall (later) All Addon Module

Uninstall Visual Studio and Reinstall it.

Install Version 11.0 Preview.

uninstalling everything and then run InstallCleanup.exe -f, redownload the online installer ands install just the .Net development as module: Brings the error during install.

DID NOT HELP.
So I never can get VS to run on my machine anymore unless I reinstall Windows, which I do not want to because of tons of software to reinstall/configure...

Very annoying!
Please sign in to rate this answer.
Fred Bullmer 11 Reputation points

2021-07-12T19:39:49.523+00:00

@Der Abt See Mark's answer from May 05 2021 at 7:40 PM. It has worked for at least two of us.
If it works for you, please bump up his answer to make it easier for others to find it.

Der Abt 1 Reputation point

2021-07-13T12:15:45.263+00:00

On the entire page there is no user "Mark" and no post of May 05 2021
What do I wrong?

Fred Bullmer 11 Reputation points

2021-07-13T20:17:09.847+00:00

Hey, try this link: https://learn.microsoft.com/en-us/answers/questions/313193/could-not-start-visual-studio-due-to-an-error-stre.html?sort=votes

Der Abt 1 Reputation point

2021-07-14T11:05:28.013+00:00

This is this page just sorted by votes.
Again:
There is no User "Mark" and there is no post of May 05 2021

What is wrong?

Markus Pope 16 Reputation points

2021-07-14T16:16:11.077+00:00

I think that may be referring to me. My name is "Markus". My mother still calls me "Mark". In any case, I found a solution to this problem and @Fred Bullmer posted a link to what I did to solve the problem. Basically, it's that crap System.Numerics.Vector assembly that someone on the Microsoft team refuses to fix. So, you have to update bindings to get past the problem. I don't know why it affects some people and not others.

Markus Pope 16 Reputation points

2021-07-14T16:16:48.707+00:00

@Der Abt Here it is again:

Delete all of the logs in %userappdata%\temp\servicehub\logs. (This will be c:\users{your user}\appdata\local\temp\servicehub\logs most likely.)

Start Visual Studio and get the error message saying that JSON-RPC blah blah blah.

Open the log files generated in the servicehub\logs folder.

If you see an error indicating that System.Numerics.Vectors 4.1.3.0 could not be loaded because the version installed doesn't match the manifest, then go to the next step.

Modify the devenv.config file in the C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\Common7\IDE folder (replace with appropriate folder for community or enterprise) and add the following assembly redirect:

<dependentAssembly>
<assemblyIdentity name="System.Numerics.Vectors" publicKeyToken="b03f5f7f11d50a3a" culture="neutral"/>
<bindingRedirect oldVersion="0.0.0.0-4.1.4.0" newVersion="4.1.4.0"/>
</dependentAssembly>

Markus Pope 16 Reputation points

2021-07-14T16:16:58.637+00:00

And...

Modify the Microsoft.Developer.IdentityService.dll.config file in C:\Program Files (x86)\Microsoft Visual Studio\2019\Professional\Common7\ServiceHub\Services\Microsoft.Developer.IdentityService (again replacing professional with community or enterprise) and add the same assembly redirect.

<dependentAssembly>
<assemblyIdentity name="System.Numerics.Vectors" publicKeyToken="b03f5f7f11d50a3a" culture="neutral"/>
<bindingRedirect oldVersion="0.0.0.0-4.1.4.0" newVersion="4.1.4.0"/>
</dependentAssembly>

After I did this, I was able to start Visual Studio Professional. >:( There appears to be some weird conversation going on about the versioning on this specific file dating back a couple of years and apparently no one is willing to address the problem.

Fred Bullmer 11 Reputation points

2021-07-16T13:02:46.31+00:00

Thanks Markus. :)

It's also really troubling to me that he is not seeing any of the messages from May 5th. (Cinco de Mayo?)

I think your other posts on that day was good for the "narrative" of how you found it.

Fred, Freddie, Frederick :D

aka WornOutTire
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
haruki akimoto 1 Reputation point

2021-10-31T21:55:07.613+00:00

I find out forgetten comment out of last description. */
This cause problem in my program.
Please sign in to rate this answer.
Andritzky, Christian [ext] 0 Reputation points

2023-03-02T10:14:08.1633333+00:00

Same problem here with Visual Studio 2022 after upgrading from 17.4.5 to 17.5.1.

Problem only occurred after I opened the "Team Explorer" panel and tried to re-authenticate with my Azure DevOps account (which failed).
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.
Lucas Harskamp 20 Reputation points

2025-08-08T08:43:13.3133333+00:00
I've had the same issue, here's a bandaid to the issue: it happens whenever an exception occurs in your own source generator and Microsoft's tooling doesn't gracefully catch it. You may think your source generator (or IIncrementalGenerator if that's your fancy) works fine, but unexpected errors may occur when it's working on a singular class in your assembly after you've saved its .cs file. So the best thing I could advise one is to wrap your SourceGenerator methods in try-catch blocks. This way, you'll be alerted when an issue does occur, so you can fix it.

try { ... } catch (Exception ex) { Debugger.Launch(); context.ReportDiagnostic( Diagnostic.Create( new DiagnosticDescriptor("GEN0001", "Source generator error", ex.Message, "SourceGen", DiagnosticSeverity.Error, true), Location.None )); }

Dear Microsoft; please provide a patch to Visual Studio where you presume any and all Source Generators will fail in unexpected ways, and account for that without it breaking the internal tools of the IDE.
Please sign in to rate this answer.

0 comments No comments
Sign in to comment

Use comments to ask for clarification, additional information, or improvements to the question.

Share via

Could not start visual studio due to an error - StreamJsonRpc.ConnectionLostException

8 answers

Your answer