I recently updated my system from Windows 7 to Windows 10. Before I did this, my Visual Studio C++ compiler (2013) and debugger was working fine but when I ran the debugger, I would occasionally get the following message:
The Visual Studio 2015 Remote Debugger (MSVMON.EXE) does not appear to be running on the remove computer. This may be because a firewall is preventing communication to the remove computer. Please see Help for assistance on configuring remote debugging.
When I got the message, I would restart the debugger and the message would go away. After upgrading to Windows 10, every time I run the debugger, I get this message. Then the debugger does not run. So, I upgraded to Visual Studio C++ 2015 hoping it would fix the problem. It does not. I also use ZoneAlarm as my firewall. I thought that might be the problem. So I turned off ZoneAlarm but that did not help.
What am I doing wrong?
Related
VS2017 remote debugger had been working well until some developer replaced it with VS2019 version.
I know them can both work on the same computers since they use different ports (4022 and 4024).
On this computer I already shut down the remote debugger 2019, and ran debugger 2017. It prompts such message:
Unable to configure this computer to allow remote debugging. The
system cann't find the path specified.
I don't know why.
Just turning-off the firewall solved the problem.
I'm using Visual Studio 2017 with a ClearCase dynamic view connected to a mapped drive.
Starting a debugger session fails with:
Unable to start program filename.exe.
Operation is not supported.
Unknown error: 0x80070057.
Using a ClearCase snapshot view, the debugging session works as expected, without error message.
Visual Studio 2013 works perfectly fine with a snapshot or dynamic view.
Any help would be appreciated.
It depends on your exact ClearCase version, as seen in this PI45450 (project issue, similar but not identical to your case)
PI45450: RUNNING AN .NET EXECUTABLE IN A DYNAMIC VIEW FAILS WITH RUNTIME ERROR SYSTEM.ARGUMENTEXCEPTION 0X80070057 (E_INVALIDARG)
Recommendation:
Running the executable by specifying its fully qualified UNC
pathname may work, such as
\\view\viewtag\vobtag\<application>.exe
In your case, with Windows:
m:\viewtag\vobtag\<application>.exe
See if the full path (M:\...\<application>.exe) works better with Visual Studio 2017.
Or try and upgrade ClearCase if possible (8.0.1.10+).
There is a new ClearCase APAR for this behavior, because it was initially reported only if the CC VS 2017 integration was installed. It actually doesn't need the integration, at least not on Windows 10 with UAC on. The APAR is PI86014, but it may not be visible yet as it's really new.
The issue is specific to Visual Studio 2017, Visual Studio 2015 will open and start the debug session fine, and the debug executables load just fine from a dynamic view.
The integration released in the technote seems to be a little buggy. Perhaps the one in 9.0.0.5 and 9.0.1.1 will behave better.
I'm trying to build and run a simple project in Visual Studio 2017 (C++) in x64 using the Local Windows Debugger. However every time I try to run it using the debugger I get this error.
This error doesn't show up when I change it from x64 to x86, but I need it to compile to x64. This has happened on both computers that I've tried it on, and seems to happen in every one of my projects. I've tried reinstalling Visual Studio already and nothing's changed. I've tried adding 'devenv.exe' as an exception to the Windows Firewall but no changes there either, even when I disabled the firewall completely. My antivirus isn't affecting it at all either: still happens when I disable it.
The application runs fine when I find it in the explorer and run it manually but then I don't have any debugging tools.
What am I doing wrong here, how do I make it build and run my project as x64?
I get this error every time I have an active VPN connection. If you use a VPN, try disconnect and see if the error disappears.
If you want to use a VPN, the solution (assuming you have Visual Studio 2017 Version 15.7 or later) is as follows:
Go to the Windows Start Menu and launch the “Developer Command Prompt for VS 2017 Preview”
Run: "%DevEnvDir%vsregedit.exe" set "%VSINSTALLDIR:~0,-1%" HKCU Debugger UseAnonymousPipes dword 1
Restart VS if it is already running
That solution is from this link to Microsoft.
I'm using Microsoft Visual Studio 2010. It was going fine until this morning when I try to build my code. It gave me this weird error:
C:\Program Files
(x86)\MSBuild\Microsoft.Cpp\v4.0\Platforms
\Win32\Microsoft.Cpp.Win32.Targets(147,5)
:error` MSB6006: "CL.exe" exited with code 1073741855.
I have no idea why this error is occuring. I need help please.
I am using Window 7.
1073741855 is 0x0x4000001f, and 0x1f is decimal 31, and 31 is ERROR_GEN_FAILURE. In other words, something is hosed and VS isn't going to tell you what it is.
Go to Control Panel/Programs and Features, right click, Uninstall/Change, Repair/Reinstall. If that doesn't fix the problem, I would uninstall VS completely and reinstall.
For those of you looking to avoid the (timely) process of uninstalling and reinstalling Visual Studio, a simple restart worked for me. I have noticed this happens more often when I have multiple Visual Studio windows open.
I am running Visual Studio 2005 on Windows XP. It crashes without any error, log or trace when I try to load the solution for our product that contains 362 projects. I don't think the size of solution (362) is a problem, because it works on my colleagues computers. There is no entry of this in Event Viewer.
Any help to locate root cause of the problem or any solution if known would be greatly appreciated.
Thanks,
Shashibhushan
Thanks Luke for your suggestion. When I debugged using windbg.exe, it became evident that the exception was being generated at the time of loading dll related to "VMDebugger - Visual Studio Integrated Virtual Machine Debugger". I disabled it from the Add-in Manager and now the solution is being loaded successfully and working fine. Thanks for all your suggestions.
Thanks,
Shashi
Just some general thougts:
Uninstall SP1 - i had several difficulties with it. I.e. i was unable to create a working x64 DLL using SP1
Try again on a different machine that so far does not have Visual Studio on it. So you know wheteher its a problem of the Machine, or maybe a general Problem of Visual Studio
Uninstall and reinstall Visual Studio.
EDIT:
If you started seeing these problems yesterday i would even more strongly suggest, to uninstall and reinstall VisualStudio as well as SP1.
Did you install any new software recently?