My builds keep failing with the following error
Project : error PRJ0002 : Error result 31 returned from 'C:\Program Files\Microsoft SDKs\Windows\v6.0A\bin\mt.exe'.
I find that i have to kill some process called mspdbsrv.exe description:"microsoft program database" Then rebuild the entire project. This is annoying. Is there a permanent solution to this problem or is it stuck with me for good?
PS
OS: windows 7 ultimate
msv studio 2008 + sp1 professional
The problem is that for some reason, your mspdbsrv.exe is staying alive after the build. This is what's used to generate your .pdb files as part of the build. The only reliable solution seems to be to kill that process.
What you can do is at least automate that, just add a post-build event and console kill it. I'd suggest using the SysInternals PSKill utility (free) like this in your post-build:
pskill mspdbsrv.exe
This issue came into effect on our Windows10 build slave over the holiday. It worked Thu and failed Fri without any code changes or anyone even in the office either day. We assume that there was an automated microsoft update that caused the issue.
Disabling Windows Defender solved the problem for us.
Microsoft Security Essentials appears to have caused my problem. I added mt.exe to the Excluded processes, and the problem stopped occurring.
I had the same problem. It was solved after VIPRE Anti virus disabling.
Related
I have the problem that I cannot update or install Visual Studio anymore on my system.
Today I saw that a newer Visual Studio 2017 version was released and I tried to start the VS installer for the update process. The start for the installer was just spinning but nothing happened. After that I tried to start the installer separately from VS but it didn't work either.
So I continued to make an even bigger mistake by assuming my installed version is bad and to completely reinstall Visual Studio by uninstalling and then trying to start the normal installation process.
Unfortunately it didn't work.
After downloading the webinstaller, it downloads the installer packages it needs but the vs_installer.exe itself will never run successfully afterwards (also if started manually).
There is no error shown directly. It just does not start. The EventViewer is also not showing any errors I would say have a connection to the problem.
Any ideas? Thanks!
After a bit of communication with the Visual Studio team they pointed me to the only thing they know could cause this issue.
Some time ago I added an environment variable to my system named NODE_OPTIONS. It was necessary because the builds of our Angular applications are so big that we had to adjust the available memory size.
Removing the environment variable enabled me to start vs_installer.exe and to reinstall Visual Studio again.
It's a bit obscure and not many people will have this problem. But I hope Microsoft will fix it anyway.
P.S. The silent crash is caused by the usage of Electron for the Visual Studio installer. The person from Microsoft, who helped me to workaround the problem, told me that they are working on a fix.
I have this C++ project I am trying to debug in Visual Studio (Community) 2015. The build is always successful, but after that debugging never starts. All that shows up is the Windows loading icon, which just never goes away. Any ideas about what might be wrong?
The problem was that Avast was interfering with my Visual Studio Projects. I used the instructions at https://forum.avast.com/index.php?topic=139935.0 to get it to work.
Basically you need to exclude your VS projects from Avast's scan.
... but simply turning off DeepScreen in Avast 2014 is not enough. I
make multiple apps in Visual STudio 2012, and I can tell you that even
with Deep Screen off, Avast will still pop right up and destroy the
compiling process by saying the .exe is a virus (the crazy "evo-gen
[susp]"). The only way I can get Avast to stop doing that is to
manually enter-in exclusion directories for every directory where I
create apps! ...or make an exclusion for some high-level folder.
Try resetting your settings by going here
Tools >> Import and Export Settings Wizard >> Reset all settings
I had similar problems for Visual Studio 2015 Update 1 on Windows 10.
For me, the only solution, which helped is to install this package:
https://www.microsoft.com/en-us/download/confirmation.aspx?id=49029
"FIX: Devenv.com process freezes after you execute devenv.com /build command in Visual Studio 2015 " https://support.microsoft.com/en-us/kb/3092422
I have a problem with debugging my program in Visual Studio 2012 -
when I try to debug the code by inserting some breakpoints, they seem not to work - when I hover on them a message pops up
The breakpoint will not currently be hit. Unexpected symbol reader error while processing <file.exe>
I tried searching for similar problems in the internet but I haven't found any solutions
I'd appreciate any help, thanks!
[VS 2012] Ok I got the answer that fixed this problem, so I'll post this here so that people have no such problem in the future.
A solution is to change
Debug -> (app) Properties-> Configuration Properties -> Debugging
from Auto to Mixed.
The breakpoints will automatically work.
[VS 2015] Closing all instances of VS 2015 and restarting fixes the problem for a while at least. The 2012 fix does not work.
For Visual Studio 2017, closing all open instances and restarting worked for me.
I might have gotten away with closing fewer, for example instances with unrelated solutions open, but I have not tested that.
I had a VS 2017 C++ DLL called from VS 2013 C# application. Upgrading the application to VS 2017 solved the problem.
Just a side note to the answer accepted, you should checkout /DEBUG:FULL in Linker->Debugging in Visual Studio 2017 upwards
Beginning in Visual Studio 2017, the build system in the IDE defaults to /DEBUG:FASTLINK.
This limited PDB can't be used for debugging when the required build products are not available, such as when the executable is deployed on another computer.
Source: https://learn.microsoft.com/en-us/cpp/build/reference/debug-generate-debug-info?view=vs-2019
In VS2017, I have to clean up and close the whole solution, then delete the .vs folder from the solution folder, then recompile to fix it.
I'm trying to start a performance profiling session in Visual Studio 2012 RTM on Windows 8 PRO 64-bit for a console program (ANALYZE / Start Performance Analysis).
I get a popup message informing me
Could not load file or assembly 'Microsoft.VisualStudio.PerformanceTools.CounterInfo.dll' or one of its dependencies. The Specified module could not be found.
Apparently this can happen under VS2010 after KB2645410 is installed. I carefully followed the procedure given for this issue with the same error message:
Visual Studio 2010 SP1, KB2645410 and Add-Ins
However, that does not resolve the issue.
I have tried running VS2012 as Administrator as well.
How can I get the profiler working?
UPDATE
I can actually attach to a running instance of the project from the command line using the steps here:
Walkthrough: Command-Line Profiling Using Sampling
However, Visual Studio does not open the resulting .vspx file (it just does nothing after I open it with File / Open File).
UPDATE 2
Fuslogvw reports two binding errors when I attempt to start the profiler:
VS 2012 Profiler Binding Errors - Pastebin
Adding the following to the system path resolved the issue for me permanently.
C:\Program Files (x86)\Microsoft Visual Studio 11.0\Team Tools\Performance Tools
Some other answers may be appropriate to other situations.
Note that you probably will need to run Visual Studio as Administrator for profiling to work correctly.
I also struggled with that issue.
I found a working solution for me:
I opende the XXX.sln file using notepad.
There i found several parts in the Project and Global Section looking something like this:
ProjectSection(SolutionItems) = preProject
Performance1.psess = Performance1.psess
EndProjectSection
I removed all of them and that made my Analyzer work again.
I delete the .suo file and everythings works correctly now.
The same question exists here:
http://social.msdn.microsoft.com/Forums/en-US/a6487155-980c-4bc8-82de-2fe588fdf37f/windows-update-kb2645410-and-performance-tools-error
The following are suggested workarounds:
Remove windows update KB2645410
Only run one instance of Visual Studio
If you are the administrator on your development PC you can add the permission to Everyone to read and execute all the content in the folder "C:\Program Files (x86)\Microsoft Visual Studio 10.0\Team Tools\Performance Tools" and subfolders/files.
"I backed everything up and did a complete repair of Visual Studio using the original disk from Microsoft. That allowed the computer to shut down normally. Then I tried the patch again. It hung again, but after a few reboots we got a message about deleting corrupt files and finally everything seems OK."
My issue was resolved when I realized that my user access control was set too high. Once that was turned off, I rebooted and it all worked great.
Once I uninstalled re-sharper my issue was resolved.
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?