My problem is basically that whenever I debug using Visual Studio (2015 Community edition on Windows 10 machine), and I try to hover over a variable or look at a variable in the locals or autos section of the debug view, I don’t see the actual data saved in the variable.
This is a problem I have seen with both strings and vectors. For strings, it will show npos=4294967295
and if you keep clicking the drop down arrows, you will eventually get to the actual string saved in that variable; only after digging into the internal structure of the variable, like std::_String_alloc and _Mypair and _Myval, etc. Same for vectors.
Has anyone ever experienced this problem or knows how to fix it?
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and
privacy statement. We’ll occasionally send you account related emails.
Already on GitHub?
Sign in
to your account
Closed
marcwmiller opened this issue
May 5, 2017
· 77 comments
Assignees
Comments
I’m getting the following error intermittently (approx 10-20% of CI build/tests) with the Visual Studio test runner (version 2.0.30):
Error: C:Program Files (x86)Microsoft Visual Studio2017EnterpriseCommon7IDEExtensionsTestPlatformvstest.console.exe failed with return code: 4294967295
My solution is VS2017 with .Net Core and Xunit test projects. I’m using the Hosted VS2017 agent.
Not only is it intermittent, but when it does fail, it is not in the same test project. Never are there failed tests.
What is return code 4294967295?
6_Test Assemblies .Tests.dll.txt
I also experience this lately, nothing to note with debug logging on, it just quits.
I also have it with some msbuild tasks (same idea, .net core in solution, xunit, hosted vs2017 agent).
Started happening since Tuesday
Same here. Just randomly started happening. It is a major blocker/annoyance for us.
Tagging @smadala . Can someone share the diagnostic log too please(with System.Debug «true»)?
@janpieterz, @daniefvh To run .net core unit tests choose vstest.console.exe from «C:Program Files (x86)Microsoft Visual Studio2017EnterpriseCommon7IDEExtensionsTestPlatformvstest.console.exe».
in vstest task (Execution options -> Specific location). In «Other console options» pass /diag:log.txt for diag information. please attach log.txt and log.*.host.txt.
@marcwmiller Please enable /diag:log.txt and attach log.txt and log.*.host.txt.
Seems for vstest to have something to do with code coverage. Where do I get those log.txt files from?
Also any thoughts about the msbuild one?
logs_639.zip
Seems for vstest to have something to do with code coverage.
/EnableCodeCoverage yet to support in .net core. Tracking here.
Pass /Framework:FrameworkCore10 arg in «Other console options» for running .net core tests.
log.txt is relative path from current working directory, you can pass absolute path too.
No vstest task or tests running in msbuild one. It was failing in Build solution, @acesiddhu Can you please tag Build solution task folks?
We are adding respective folks to investigate into this issue. Seems like both msbuild and vstest are failing with same error code.
@smadala — I have enabled /diag:log.txt as requested and will attach log files after next failure.
@marcwmiller
DefaultEngineInvoker: ParentProcess ‘1244’ Exited in log.host.17-05-08_12-08-07_38614_9.txt
Looks vstest.console.exe exiting abnormally, Can please share log.txt which will be in current directory of vs test task command runs.
vstest.console.exe full dump by following instructions here.
@smadala — I think I’ve correctly updated the Copy Files task to capture the log.txt file (we’ll have to wait for another failure).
But I’m not sure about your last request for logs — I’m using the Hosted VS2017 agent and cannot perform instructions provided in the link. Please advise.
This seems widespread, we have this error in approx. every 3rd build or so for several projects. Sometimes consecutive test runs have this, then it works for a couple of builds without any apparent change on our side. This happens only in VSO i haven’t been able to repro locally.
Solution is VS 2017 .Net 4.6, Nunit 3.7, Hosted VS2017 agent
@marcwmiller are you able to get log.txt file?
@nigurr Is there a way we can get dmp from Hosted server?
Just a note that we are not running .NET core. I will try getting logs for you.
@marcwmiller can you please send your VSTS account and build details to devops_tools at microsoft dot com
I will be investigating into this asap.
FYI, we have the same problem with .net 4.6, VS2017, 2017 host, MsTest v2. And it happens to the build step as well, about as frequent.
Hi,
We have created a Live Site Incident for the same and actively working on this.
@nigurr — I am unable to email the information requested. My email is returned with the following error:
The groups only accept messages from people in their organization or on their allowed senders list, and your email address isn’t on the lists
does everyone on this thread have .NET Core projects in their solution? Also can you all post your account URLs?
@chrisrpatterson — My solution contains .NET Core projects. I have shared account URL with @nigurr and can email to you if you’d like.
@marcwmiller can you simply ping your account and tell me what it resolves to.
Jup, contains .NET core, account url is intreba.visualstudio.com, one of affected projects Arke.
@nigurr has access to this already.
@chrisrpatterson tfsprodcus1.app.visualstudio.com [104.43.203.175]
Another question, what about TypeScript?
@janpieterz while I am working through debugging this issue I am going to temporarily increase the number of hosted agents in your account so I don’t block your normal work
@chrisrpatterson I see, interesting. I’ll wait for you to finish, only need to build correctly once for this security advisory.
@janpieterz you have 5 agents right now so you should be able to build.
Jup, I noticed when both ran at the same time. Cheers!
We don’t have any .NET Core / TypeScript stuff.
We went back to the non-2017 host and all is well. We can’t open it up for experimenting with builds since we have external dependencies (database for end2end tests).
Like I said in a previous post, we see builds failing on either the build step or the test step (not both).
@janpieterz thank you for your patience. We are working with the MSBuild team to figure out what additional diagnostics we can gather. It seems the failure rate is about 20% and the MSBuild failure happens at a different place in the project every time.
@chrisrpatterson no worries, happy to help! If you want to speed up your build test, you could disable webpack and npm, they shouldn’t bother the msbuild and test!
If you’d like me to add any other MS employee just send me an email or ping me here, besides that I’m enjoying the notifications for the builds in our Slack 😄
@chrisrpatterson Great to hear, just removed you. In case you need to get back in just let me know, otherwise good luck hinting, and cheers for that temp workaround!
What do I do with those agents btw?
@janpieterz the extra hosted agents should disappear. You can also delete the agent in the default pool.
we are also seeing about 50% of builds fail on running tests with error
Error: C:Program Files (x86)Microsoft Visual Studio2017EnterpriseCommon7IDECommonExtensionsMicrosoftTestWindowvstest.console.exe failed with return code: 4294967295
similar to @nvankesteren we are using the Hosted VS2017 agent, due to this we also needed to change the build to use the Version 2.* preview version of the Visual Studio Test step
The current situation is intolerable, but not sure what to do, is the error we are seeing the same issue? is this a known issue that is being fixed or do we back out and stop using the Hosted VS2017 agent? we started using the VS2017 agent because the default one started giving us c# compilation errors randomly due to new c# language features.
We are actively working very hard on it. We apologize for the inconvenience this is causing. What we know is the process does not crash — both msbuild and vstest simply exits with -1 or maxint. It only happens on the first run on a fresh OS (that is the hosted build scenario since every build is a new machine reimage). For example, you can put a second task of build or test in the same job with the first being continue on error and it will always succeed.
The workaround is to use a private agent (your own VM / machine).
A new image which fixes/mitigates the issue should be rolling across scale units throughout the day. Chime in throughout the weekend and early in the week if it’s addressed for you. We will be keeping an eye on it.
got another failure just now
Error: C:Program Files (x86)Microsoft Visual Studio2017EnterpriseCommon7IDECommonExtensionsMicrosoftTestWindowvstest.console.exe failed with return code: 4294967295
@cob999, can you please send your VSTS account and build details to devops_tools at microsoft dot com
and send your build log?
@nigurr I’ve sent that on, got a bounce message saying Couldn't deliver to the following groups: but i’m hoping the original email got to you
@nigurr — I’ve received the error twice today 
Error: C:Program Files (x86)Microsoft Visual Studio2017EnterpriseCommon7IDEExtensionsTestPlatformvstest.console.exe failed with return code: 4294967295
Vstest exited with return code: 1.
we’re copying a new image with gflags to figure out what’s wacking the process (it’s not crashing, it’s not exiting). the previous mitigation appears to reduce the likelyhood but still hapenning … we’re on it.
A new image is rolled out with additional logging enabled to determine more information. When msbuild.exe/vstest.console.exe exits, info will be written to the application event log with the exit code and if another process killed it, the name of the process that killed msbuild.exe/vstest.console.exe.
Please add the below inline powershell to grab the info from the application event log once. Please make sure you select «Always Run» in the task so that any previous errors in the build will still continue to execute this and dumps the logs.
Get-EventLog -LogName Application -After ([datetime]::now.addhours(-1)) -Source 'Process Exit Monitor' | % { "EventID: $($_.EventID)" ; "TimeGenerated: $($_.TimeGenerated)" ; "Message: $($_.Message)" ; "" }
Can MS repro this without outside projects? My team no longer has the resources to keep testing this and have stepped back a version. I’m watching this space to see if the issue is resolved.
We finally got a repro which captured the offending process from the event log line above. We know exactly what is killing msbuild/vstest now. We’re following up right now with an image update. It takes awhile to rollout but good news.
This one was especially tough because the size, length and volatility of our tool would protect it from repro’ing. Sorry for the inconvenience.
@bryanmacfarlane — when do you anticipate the roll out to be complete? I’m still receiving error:
Ran for 3.7 minutes (Hosted VS2017), completed at Fri 05/26/2017 05:43 PM
Request Summary
Request 309 Marc Miller Completed
Summary
| Build
2 error(s), 3 warning(s)
Build — 2 error(s), 3 warning(s)
Error: C:Program Files (x86)Microsoft Visual Studio2017EnterpriseCommon7IDEExtensionsTestPlatformvstest.console.exe failed with return code: 4294967295
Vstest exited with return code: 1.
@marcwmiller please send ersciple the name of your account (at microsoft com).
Updated June 2023: Stop error messages and fix your computer problem with this tool. Get it now at this link
- Download and install the software.
- It will scan your computer for problems.
- The tool will then fix the issues that were found.
Microsoft says it’s aware of a bug affecting some Windows 10 Insiders where the WSL (Windows Subsystem for Linux) doesn’t work properly. Microsoft says it’s working on a fix. In the meantime, here are three things you can do while you wait:
1. Use Bash on Ubuntu on Windows to access the command prompt.
2. Install Cygwin. You’ll still need to use Bash on Ubuntu on Windows, but you won’t have to worry about compatibility issues.
3. Try installing another version of WSL. If you don’t want to try out the latest build, you could always download one of the older versions.
The full list of fixes is available on GitHub.
Why Does the 4294967295 WSL Process Exit Code Occur?
The Windows Subsystem for Linux (WSL) process exits with code 4294967295 under certain conditions. This error code is returned when the WSL process cannot open a file handle for the specified path, and no other errors occur.
This article describes how to fix the error code.
Correction of WSL Process Exit Code 4294967295
This issue occurs due to a corrupt registry key. There are several possible reasons for this error. One of the most common issues is caused by malware infections. If you use Windows 10 Home edition, it is recommended to install Microsoft Security Essentials antivirus software. You can download it here.
If you don’t want to reinstall Windows, try repairing the registry. To do this, open the Registry Editor (regedit). Search for “Wsl”. Right-click on the entry named “Wsl”, select Properties, go to the tab called “Security”, check the box next to “Permissions”, and change the value to “Full Control”. Click OK twice, and restart your computer.
1] Reset Winsock
Winsock is a very useful program for developers who want to access the Internet. But it can cause problems because it contains different versions. One version works fine, while another causes errors. You might think that you just need to uninstall one version and install the other. But that won’t work. Here are some tips to help you solve this problem.
Step 1: Check whether Winsock is installed correctly
First, check whether Winsock is installed properly. Run the following command:
This command lists all programs running under Windows. If Winsock isn’t listed, then download it from Microsoft.
Step 2: Uninstall Winsock
If you don’t want to use the latest version of Winsock, you can uninstall it.
Updated: June 2023
We highly recommend that you use this tool for your error. Furthermore, this tool detects and removes common computer errors, protects you from loss of files, malware, and hardware failures, and optimizes your device for maximum performance. This software will help you fix your PC problems and prevent others from happening again:
- Step 1 : Install PC Repair & Optimizer Tool (Windows 10, 8, 7, XP, Vista).
- Step 2 : Click Start Scan to find out what issues are causing PC problems.
- Step 3 : Click on Repair All to correct all issues.
2] Stop or Restart Hyper-V Service
To start or stop Hyper-V service, you must use Windows PowerShell. You can do this by opening a command prompt window and typing “powershell”. If you are prompted to enter your password, press Enter. Type the following commands and press Enter:
# Start Hyper-V
Start-Service -Name MicrosoftHyperv
# Stop Hyper-V
Stop-Service -Name MicrosoftHyberv
# Restart Hyper-V
Restart-Service -Name MicrosoftHYperv
3] Uninstall DNSCrypt
If you are experiencing issues while trying to install DNSCrypt, there could be several reasons why. One of the most common problems is related to the DNS server settings. In some cases, the DNS servers might be set incorrectly or the wrong ones might be used. This can cause connection errors, such as the one mentioned above. To resolve this issue, we recommend that you check the DNS server settings and make sure that they are correct. If you still experience issues, try uninstalling DNSCrypt.
To do this, open Command Prompt and type the following command:
uninstall.exe /qdnscrypt
This will remove DNSCrypt completely. After completing the process, restart your computer.
4] Disable/Enable WSL & Virtual Machine Platform
Error Code 4294967295 occurs while accessing Windows Subsystem for Linux (WSL). This error can occur due many different reasons. In most cases, it is caused because you are trying to run a virtual machine on WSL. You must disable the virtual machine before you can use WSL again. To do this, follow the steps mentioned here.
If you are unable to access WSL, try disabling the virtual machine platform. If you still cannot access WSL, contact Microsoft support.
Reinstall Docker Desktop (if applicable)
The issue here isn’t really about Docker Desktop, it’s about Windows 10. If you’re having issues with Docker Desktop, try reinstalling it. This should resolve the issue.
If that doesn’t work, uninstall Docker Desktop. You’ll lose some data, but that’s better than losing everything.
A reboot might help too.
RECOMMENATION: Click here for help with Windows errors.
Frequently Asked Questions
How can I tell if WSL is set up?
Type WSL into the Windows Command Prompt to find out whether or nor you have WSL installed on your computer. If it says “Not Installed”, then you don’t have WSL installed. You’ll want to download and install WSL. Otherwise, skip ahead to step 2.
To switch between them, simply enter either “bash” or “sh” in the Run prompt. This will open up a bash terminal window where you can run commands like ls -la.
Is WSL enabled by default?
Microsoft has been pushing Windows Subsystem for Linux (WSL), a feature that allows you to run Linux apps within Windows 10, since 2016. But there’s still some confusion around how much control you actually have over WSL. Is it enabled by default? Does it require manual configuration? Can I turn it off? We’ve gathered up everything we know about WSL to help clear things up.
I have spent around two days to solve this but got no luck. My Vs Code is working fine but suddenly it starts showing the error The terminal process "C:WINDOWSSystem32cmd.exe /c (type "C:UsersDellAppDataLocalTempvscode-linux-multi-line-command-172.16.16.96-566984369.sh" | ssh -T -D 50126 172.16.16.96 bash) & exit /b 0" terminated with exit code: 4294967295. I don’t know what happen.
I am using VS Code on my Window 10 Machine and trying to connect to my office Mac Machine. Everything is working before last 2 days.
I am using VSCode-Insider and Remote SSh nightly extension.
Further stack trace is
[19:29:36.337] remote-ssh-nightly@2020.9.2340
[19:29:36.337] win32 x64
[19:29:36.344] SSH Resolver called for "ssh-remote+172.16.16.96", attempt 1
[19:29:36.345] SSH Resolver called for host: 172.16.16.96
[19:29:36.345] Setting up SSH remote "172.16.16.96"
[19:29:36.604] Using commit id "e790b931385d72cf5669fcefc51cdf65990efa5d" and quality "insider" for server
[19:29:36.614] Install and start server if needed
[19:29:39.671] Checking ssh with "ssh -V"
[19:29:40.070] > OpenSSH_for_Windows_7.7p1, LibreSSL 2.6.5
[19:29:40.108] Running script with connection command: ssh -T -D 50126 172.16.16.96 bash
[19:29:40.217] Terminal shell path: C:WINDOWSSystem32cmd.exe
[19:29:40.810] >
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> ]0;C:WINDOWSSystem32cmd.exe
[19:29:40.810] Got some output, clearing connection timeout
[19:29:40.940] >
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
>
[19:29:44.719] > Password:
[19:29:44.720] Showing password prompt
[19:29:45.861] "install" terminal command done
[19:29:45.862] Install terminal quit with output: Password:
[19:29:45.863] Received install output: Password:
[19:29:45.865] Stopped parsing output early. Remaining text: Password:
[19:29:45.865] Failed to parse remote port from server output
[19:29:45.879] Resolver error: Error:
at Function.Create (c:UsersDell.vscode-insidersextensionsms-vscode-remote.remote-ssh-nightly-2020.9.2340outextension.js:1:130564)
at Object.t.handleInstallOutput (c:UsersDell.vscode-insidersextensionsms-vscode-remote.remote-ssh-nightly-2020.9.2340outextension.js:1:127671)
at I (c:UsersDell.vscode-insidersextensionsms-vscode-remote.remote-ssh-nightly-2020.9.2340outextension.js:127:106775)
at processTicksAndRejections (internal/process/task_queues.js:94:5)
at async c:UsersDell.vscode-insidersextensionsms-vscode-remote.remote-ssh-nightly-2020.9.2340outextension.js:127:104774
at async Object.t.withShowDetailsEvent (c:UsersDell.vscode-insidersextensionsms-vscode-remote.remote-ssh-nightly-2020.9.2340outextension.js:127:109845)
at async Object.t.resolve (c:UsersDell.vscode-insidersextensionsms-vscode-remote.remote-ssh-nightly-2020.9.2340outextension.js:127:107960)
at async c:UsersDell.vscode-insidersextensionsms-vscode-remote.remote-ssh-nightly-2020.9.2340outextension.js:127:141955
[19:29:45.886] ------
[19:29:50.235] Password dialog canceled
[19:29:50.236] "install" terminal command canceled