I have a native unit testing project in Visual Studio 2013 that has been testing the development of a C++ library for many months. Out of seemingly nowhere, Visual Studio has started popping the following message box whenever a test asserts:
vstest.executionengine.x86.exe - No Disk:
There is no disk in the drive. Please insert a disk into drive F:.
There are a few tests that access the filesystem, but I commented them out. I tried remaking the entire test project from scratch but it still is happening. Even a simple assert like this will cause the message box to appear:
Assert::IsTrue(false);
What is causing this behavior?
I'd try running VS setup in repair mode - maybe some of the vstest executables have disappeared and vs tries to find them on installer disk F
Definitely not an installation repair issue in my case. It just started to happen after I attached a new USB disk drive while tests were running.
Restarting the machine solved the problem.
Related
VS2019 was working fine.
Then I ran Visual Installer and added "Mobile development with .NET".
After than, visual Installer "update" button was showing, so I did the update.
But now when I stop my VS2019 project at a breakpoint, single stepping is very slow, taking many seconds per step.
Tried restarting VS2019, and restarting my Windows 10 Pro, but got same slowness.
Opened same project with VS2017, it is debugging is OK, no slowness.
The resolution I found was that the culprit is not Internet, RAM, or CPU.
It is the Disk Usage. Check for your disk usage under the Performance tab in Task Manager. Try and find out which process (Anti-Malware/ anti-virus/ant other process) is eating up your resources.
Kill the culprit and it works smooth. For me, it was Disk Scan Service and Windows Search Service (which is fairly useless).
Check this link to kill the Windows search service.
Comprehensive deletion of all contents of %TEMP% worked for me -
https://developercommunity.visualstudio.com/content/problem/516141/very-hight-cpu-usage-by-visual-studio-2019.html
I can't believe is 2020 and MS can't stop spaffing crap into a temp directory which causes their software to slow to a snails pace with some kind of infinite processing issue. Jeez.
For me it was NVidia NSight for visual studio. Uninstalling it from the windows application list was the only option as it wasn't showing up in the VS2019 Extensions manager.
For me it turned out to be a problem with the installation. I had old versions of Visual Studio and .NET libraries still on my machine. I did a full uninstall of Visual Studio, .NET Core SDK, .NET Framework, etc. and then re-installed Visual Studio 2019 and just the .NET libraries that I needed. After that VS 2019 debugging is speedy.
I was experiencing the same issue stepping over one line of code took me 1400 ms on my VM and 6 ms on my coworker's VM. (Earlier this week he had copied my VM so essentially we were on the same machine).
Took me some time but then I remembered a change I did to my visual studio.
Earlier that week I needed to step into one of our DLLs. To do this I changed my debug settings under Project Properties --> Debug --> Debugger engines. I Checked "Enable native code debugging". This was wonderful to allow me to debug into our DLL and see what was happening on the other side, although it dramatically slowed down my debugging (233x slower to be exact!!!!).
The performance change will different per your solution and how much you are inheriting, but unchecking this did the fix for me!
Delete .vs folder where locate in your project root directory after backup.
i am facing error message when i publish visual studio project it gave me the following message
"problem generating manifest insufficient memory to continue the execution of the program"enter image description here
computer processor core i5
ram 4 GB
and i switch off all unused services program from misconfig
also i clean windows boot
but invain it gave me the same message
For the exception thrown by visual studio, please try the following steps to solve this issue:
1) You can first try resetting the Visual Studio setting, check out How to: Reset Your Settings.
2) Have you applied the latest service pack? If not, I suggest you apply the service pack.
3) If you reboot the operating system to safe mode, do you have the problem? This can help to isolate whether any other applications are interfering with Visual Studio. In addition to safe mode, you can also try “clean boot”.
If none of these solutions works,
This looks like faulty Visual Studio installation. So, try repairing it or remove and install the fresh one.
I get this error: fatal error LNK1201: error writing to program database every time I edit my code and build again in visual studio 2003.
The issue is resolved if I restart VS2003 but I need to do this every time i build the project.
I have been googling and stackoverflowing ;) for a few hours and have tried the following proposed solution:
Change the Debug Information Format from Zi to Z7. (Property -> C/C++ -> General -> Debug Information Format)
This did not work
Change Visual Studio Compatibility Mode to Windows XP SP3
This did not work
Add the following in the Pre-Build Event : net stop "Machine Debug Manager"
net start "Machine Debug Manager"
This produced the following error: System Error 5 has occurred. Access is denied. This could be because I do not have Admin Access on this machine.
I have not tried this one because I am not allowed to download untrusted code at my work. Run FreePDB.cmd posted by Tony76 here
Changed the Symbol Path as seen here:
This did not work
What I know:
This error could occur if the pdb file exceeds 1GB but mine is only 10MB.
My limitations:
I do not have Admin Access on this computer
Cannot run untrusted software (Work Computer)
I came across the same problem when I was moving my VS project from old disk to new PC. Deleting all debug files eliminated the issue, maybe Clean-Build would solve it as well, but that is not what I have tried.
I use a program called LockHunter to unlock the PDB file. This works, though from time-to-time if stops successfully unlocking (or recognizing that the PDB file is locked) and I have to restart my PC
Had similar problem on Windows 10. This answer provides a solution using a tool called FreePDB. Worked for VS2003.NET, but apparently this solution works for multiple versions of Visual Studio.
Had similar issues when the solution was open in both VS2017 and VS2013. Fixed this issue by closing both the visual studio instances and re-opened the solution file.
Quick fix for some cases, close all msbuilds and running instances, some prior run may crashed and holding the some files/pdb
I had this issue in VS2017. Deleting the PDB mentionned in the error solved it for me.
For some reason, my ability to attach a debugger to ANYTHING has just stopped. It has persisted after a computer reboot, and it's really making things difficult.
This is the error I get:
---------------------------
Microsoft Visual Studio
---------------------------
Unable to attach to the process. Operation not supported. Unknown error: 0x80072ee6.
---------------------------
OK
---------------------------
I mean, what the hell? It stopped working whilst VS2010 was running: worked for one debug, I stopped it, and then the next one didn't work.
Any help? Thanks in advance.
EDIT:
I have tried:
a) rebooting the computer
b) regsvr32 MSXML3.dll
c) repairing MS VS2010
d) attaching the debugger manually, and by using the debug button
I had this exact problem and found that it only affected one of the projects I was working on. If I opened Visual Studio with other .sln files, they were able to attach to any process without problems. Deleting the .suo file for the affected solution didn't help, however moving the whole project to a different directory fixed the problem.
I think that Visual Studio keeps additional data for each solution file in a common location(maybe in %AppData%\Microsoft\VisualStudio somewhere) and somehow that data got corrupted for that specific path to a solution file...
EDIT: I found it! Deleting the cache in %LOCALAPPDATA%\Microsoft\WebsiteCache fixed the problem without me having to move the project files.
I got it working again, but I'm not going to mark this as a answer.
Here's what I did:
Started debugging a WP7 project - success!
Stopped debugging the WP7 project.
Started debugging the ASP.Net project (runs on a remote machine) that was in the same solution as my silverlight project I was attempting to debug - success!
Started debugging the silverlight project I was having problems with - success!
Stopped debugging both
Started debugging just the silverlight project - success!
Apparently it works now, but as I said, but I'm not marking this as the answer.
For those of you whose problem wasn't solved by deleting cache, check your Project URL in:
Debug > [project name] Debug Properties > Web (tab) > Servers (section).
I had the same error as the OP, and after adding a URL into that field it cleared the issue.
After my laptop fell on the floor and its screen was a little damaged, I was able to continue working with it, but failed to build a project of mine. At some point, the system froze, and I was forced to restart the laptop. Ever since, I’m not able to start Visual Studio 2008 or 2010. Moreover, when I do try to start one of the versions, I see no splash screen, and at some point, all running applications stop responding, and I’m forced to restart the laptop.
When I started Visual Studio 2008 with the /SafeMode flag it started OK and worked perfectly, but when I tried it with Visual Studio 2010, I did see a splash screen and the application main window was opened, but then the system got stuck again and forced me to restart.
I use Windows XP SP3, and the addins I recall I have are Visual Assist, IncrediBuild, and Productivity Power Tools for VS 2010 (how can I check what other addins are installed without having Visual Studio running?)
I tried using the /Log flag to find out what’s happening, but there was nothing that seemed related in the generated log.
At the time of the hang, the CPU and memory of the system was low.
The problem happens whether I open Visual Studio with no solution, or with an existing solution.
Do you have any idea why this might happen, or how it can be solved?
Edit:
I run chkdsk /R /V and it is stuck on "1 percent
completed." for hours now. Is there anything I can do?
I'll try to re-install Visual Studio 2010 next week, when I'm in the office. I hope that will help.
Thanks a lot,
splintor
Your drive is torched. Buy a new drive, and salvage whatever you can from the existing drive, then swap them out. If you're lucky you can salvage enough of the existing drive to not need to do a full OS reinstall, but it's likely you're going to need to do some reinstallation.
Looks like the cause if the fall of your laptop. Though what changes happened is unknown it is more likely to be a hardware issue.
Did you reinstall the softwares and check how they work.
If I was diagnosing this issue, I would start from the ground up.
Start of with a basic CheckDisc - CheckDisk Instructions for XP
Progress from that to try re-installing over your existing VS install.
I can't see it being a software problem, so I reckon the checkdisk will discover/fix something, or a reinstall should resolve it.
Dave
You've probably damaged your hard disk in an area which is touched by VS. Windows often grinds completely to a halt when it's struggling to read a damaged area of disk.
Check the Windows event log for errors to do with disk drives.