Live-share: vsls-agent.exe - System Error, VS 2017 Enterprise Startup

[joshuapetryk]

Product and Version [VS/VSCode]: VS 2017 Enterprise Version 15.6.6
OS Version [macOS/Windows]: Windows Server 2012 R2 Standard
Live Share Extension Version: 0.3.98.2686
Target Platform or Language [e.g. Node.js]: n/a

Steps to Reproduce / Scenario:

1. Install the Microsoft.VisualStudio.LiveShare.vsix plugin
2. Open Visual Studio 2017
3. Notice an error message modal popup with the following error message:

vsls-agent.exe - System Error
Exception Processing Message 0xc0000005 Parameters
0x00007FFBCF8C6550 0x00007FFBCF8C6550
0x00007FFBCF8C6550 0x00007FFBCF8C6550

How can I troubleshoot this error message or find logs? This appears to be the generic "access violation" message.

[Chuxel]

@joshuapetryk Oddly enough, #366 was raised at about the same time on the same OS version. Was this related to your issue or just coincidence?

We have not validated Windows Server 2012, so it's possible there is an issue here. I assume you've uninstalled and reinstalled to try to resolve the issue?

You can find the Live Share logs at %TEMP%\VSFeedbackVSRTCLogs

[joshuapetryk]

@Chuxel Jason is part of my team, working on an Azure VM. I am using a corporate on-prem VM. So you're thinking this is a Windows Server 2012 problem? I can try a Windows Server 2016 VM to see if that makes a difference.

Edit: Yes - tried uninstalling and reinstalling the vsix, no change.

Here's the log file:

[2018-05-14 21:23:42.861 VSIX I] vsls-agent.exe <143:014ee84f>
[2018-05-14 21:23:43.949 VSIX I] Extension, IDE, Protocol, OS: VSLS/0.3.114.65050 VisualStudio/15.0.27428.2037 VSLS/2.2 Windows 6.3.9600.0
[2018-05-14 21:23:57.937 VSIX E] Timed out waiting for agent process to respond.
[2018-05-14 21:23:57.943 VSIX E] Failed to initialize the client context: System.TimeoutException: The operation has timed out.
at Microsoft.VisualStudio.Threading.TplExtensions.d__5.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.VisualStudio.Threading.TplExtensions.d__6`1.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.VisualStudio.Cascade.AgentProcess.d__19.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.VisualStudio.Cascade.ClientFactory.d__0.MoveNext()
--- End of stack trace from previous location where exception was thrown ---
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
at Microsoft.VisualStudio.Cascade.VsCascadeClientService.d__37.MoveNext()

[Chuxel]

Merging #366 from @JasonRaby

---

Steps to Reproduce / Scenario:

1. Install extension
2. Launch VS

When launching debug the exception message reads:
Unhandled exception at 0x5FC8A786 (coreclr.dll) in vsls-agent.exe: 0xC0000005: Access violation reading location 0x00000000. occurred

[Chuxel]

@joshuapetryk Yeah Windows Server in general is not currently on our test matrix, so it's possible there is something odd going on. Win Server 2016 might work but we have not validated that either. Win 7, 8.1, 10, have been tested.

That said, this does appear to be .NET Core crash on the surface. Could you send us the crash logs? Can you go to event viewer -> Windows Logs -> Application and search for the log for the agent crash.. The Source field should have ".Net Runtime" so you can sort the logs based on Source column and retrieve the appropriate crash log.

@Priya91 - FYI

Also - Just so I understand from a scenario perspective, is there a particular reason to run in a VM?

[joshuapetryk]

we are developing a full blown asp.net mvc app (using Sitecore) with a local sql server instance. I thought developing on a vm is a pretty common thing

[Chuxel]

@joshuapetryk Oh yes, did not mean to imply I was questioning that. There's just lots of variability in how people do it and why - which is why I'm interested in the scenario. For example, a variation is running Windows 10 in Hyper-V locally if you are doing things that can alter the OS so you can use checkpoints. The thing I am most interested in understanding is the use of Windows Server verses other editions of Windows given Server is more locked down and patched differently. For example, you can create Windows Client 10 Pro VM in Azure as well. There are definitely good reasons to do it - I'm just not aware of your use case, which is why I asked.

Regardless, it would still be good to get the crash information so we can see what might be going on. As I mentioned, to get them, go to event viewer -> Windows Logs -> Application and search for the log for the agent crash (vsls-agent.exe).. The Source field should have ".Net Runtime" so you can sort the logs based on Source column and retrieve the appropriate crash log.

[joshuapetryk]

Sure no problem. I see now that me and Jason are getting the same error. I didn't have WER enabled and he does so that's why the error popup looks different.

Let me know if you need more info.
Here is the event:

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="Application Error" /> 
<EventID Qualifiers="0">1000</EventID> 
<Level>2</Level> 
<Task>100</Task> 
<Keywords>0x80000000000000</Keywords> 
<TimeCreated SystemTime="2018-05-15T01:42:14.000000000Z" /> 
<EventRecordID>147705</EventRecordID> 
<Channel>Application</Channel> 
<Computer>REDACTED</Computer> 
<Security /> 
</System>
<EventData>
<Data>vsls-agent.exe</Data> 
<Data>0.0.0.0</Data> 
<Data>5a3b0289</Data> 
<Data>coreclr.dll</Data> 
<Data>4.6.26020.3</Data> 
<Data>5a3ae975</Data> 
<Data>c0000005</Data> 
<Data>000ba786</Data> 
<Data>1694</Data> 
<Data>01d3ebedf2f88a52</Data> 
<Data>C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\Common7\IDE\Extensions\oprpfoeu.n32\Agent\vsls-agent.exe</Data> 
<Data>C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\Common7\IDE\Extensions\oprpfoeu.n32\Agent\coreclr.dll</Data> 
<Data>30dde988-57e1-11e8-814a-005056ac79d1</Data> 
<Data /> 
<Data /> 
</EventData>
</Event>

[Chuxel]

@joshuapetryk Let's try running the agent manually to see if that gives us any more information. Here's how:

1. Find the "Extensions" folder in your VS installation location: C:\Program Files (x86)\ Microsoft Visual Studio\Enterprise\Common7\IDE\Extensions
2. Run a search for vsls-agent.exe. It will be in a folder like "Microsoft Visual Studio\Enterprise\Common7\IDE\Extensions\lglqixit.qx3\Agent"
3. Run this from the command line

This should spin up the agent and start listening. It likely will crash for you, but hopefully we get a better stack trace.

[joshuapetryk]

Works fine from cmd:

C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\Common7\IDE\Exten
sions\oprpfoeu.n32\Agent>vsls-agent.exe
[Agent I] (1002) Trace log: D:\temp\3\VSFeedbackVSRTCLogs\20180515_161254_Agent.
log
[Agent I] vsls-agent v0.3.114.65050 (pid: 6600)
[Agent I] Reminder: You may only use this software with Visual Studio and Visual
Studio Code, as described in the license (https://go.microsoft.com/fwlink/?link
id=872556).
[Agent I] Start time: 2018-05-15 16:12:53.876
[Agent I] Using VSLS service: https://insiders.liveshare.vsengsaas.visualstudio.
com/
[Agent I] VSLSAgent/0.3.114.65050 VSLS/2.2 PlatformName/Microsoft Windows 6.3.96
00 PlatformVersion/6.2.9200.0
[Agent I]
[Agent I] Proxy settings from env variable: http_proxy was null and https_proxy
was null
[Agent I] (1001) Listening on pipe "VSLS"

[Chuxel]

Interesting, this is similar to #380 though in that case it was a full crash on Win 10. Could use the "Report a Problem..." feature in Visual Studio to report this? This will give us more data to go on.

[Priya91]

@joshuapetryk This is not related to your issue, but you mentioned you are behind a corporate proxy? But your http_proxy and https_proxy variables are null from your logs.

Also it looks like only when VS is trying to connect to the agent, the agent hits some codepath that causes AV. I'll try to repro this locally with similar environment to yours..

[joshuapetryk]

@Priya91 no - there is not a corporate proxy at play here. We are able to repro the issue on a Windows Server 2012 R2 Azure VM

[joshuapetryk]

@Chuxel just tried submitting via "Report a problem" twice now and am met with

Sorry, we couldn't send your report. Please retry now or sign out, sign in, and try again
Still can’t report your issue?Let us know
Error message: 'Request failed with status code 500'

the Let us know link open a browser window that doesn't go anywhere.
Also on the Visual Studio Feedback screen where it shows "Items I Follow" and "Problems" it says: Error loading your items: 'Request failed with status code 500'

How can I get this information to you?

[joshuapetryk]

I updated to VS 2017 15.7.1, no difference, still crashes at startup.

[joshuapetryk]

Okay I successfully submitted a "Report a problem" report under my name.

[Priya91]

@joshuapetryk Can you try this as well?

https://github.com/MicrosoftDocs/live-share/issues/380#issuecomment-389283555

[joshuapetryk]

@Priya91 the PipeClient.zip you posted is a VS solution. I did not find an .exe. I tried building and running it but VS 2017 can't seem to compile or debug it:

System.ExecutionEngineException
HResult=0x80131506
Source=
StackTrace:

[Priya91]

It's a .netcore project, i thought you would be comfortable looking at the source and building it yourself, I'll get you the binaries..

[joshuapetryk]

Like I said, VS can't seem to run it, getting the above error. Any idea what I am missing?

[Priya91]

publishedApp.zip

This has the whole app published, you can run pipeclient.exe <pipename>

[Priya91]

This is a .netcore app, are you able to create .NET Console apps from your VS and run them? Not sure why VS is not building it, maybe you don't have the .NET Core profile installed.

[joshuapetryk]

@Priya91 @Chuxel
Solved it!

Found the issue: https://developercommunity.visualstudio.com/content/problem/119259/can-not-run-net-core-20-application-from-vs-2017.html

We are using JustMock for unit test mocking. Looks like the JustMock profiler was hooking into .net and causing problems with dotnet core. vsls-agent.exe loads up just fine after disabling it. This was also preventing me from running @Priya91 's PipeClient.zip

[Chuxel]

@joshuapetryk That is fantastic news!! So glad you were unblocked. Really interesting to know that is the issue.