R
RD Holland
Guest
Yesterday afternoon while working on one of my projects I started getting a message box titled "Microsoft (R) Visual C++ Package Server" with the message "Microsoft Visual C++ Package Server has stopped working. A problem caused the program to stop working correctly. Please close the program."
I choose "close the program" and the dialog goes away. And then in less than a minute it comes right back up. I had two VS 2010s running. I shut both down and restarted one. As soon as I open a project the box shows up again. I rebooted. Still the dialog keeps showing up. So I picked "debug the program". The JIT debugging window shows up and tells me an "unhandled win32 exception" has occurred in vcpkgsrv.exe and the only debugger listed is "VS .NET 2003". If I pick that debugger, I am presented with a dialog box telling me the program has known problems on Win7. I choose to use it anyway. I pick native debugging and can do nothing. So I picked each check box the next time the dialog showed up. The debugger starts up and if I hit the pause button (quickly), the debugger locks up. If I don't hit pause, the call stack window and other debugging windows show up very briefly and then all go away. Nothing in the call stack window when that happens.
Besided 2003, I have 2005, 2008 and 2010 and VS 6 on the machine. None of them can be reached via the JIT debugging window.
What is this program trying to do? I see in task manager that it is constantly running when I start 2010 up.
I am on Win7 64 bit OS.
R.D. Holland
Continue reading...
I choose "close the program" and the dialog goes away. And then in less than a minute it comes right back up. I had two VS 2010s running. I shut both down and restarted one. As soon as I open a project the box shows up again. I rebooted. Still the dialog keeps showing up. So I picked "debug the program". The JIT debugging window shows up and tells me an "unhandled win32 exception" has occurred in vcpkgsrv.exe and the only debugger listed is "VS .NET 2003". If I pick that debugger, I am presented with a dialog box telling me the program has known problems on Win7. I choose to use it anyway. I pick native debugging and can do nothing. So I picked each check box the next time the dialog showed up. The debugger starts up and if I hit the pause button (quickly), the debugger locks up. If I don't hit pause, the call stack window and other debugging windows show up very briefly and then all go away. Nothing in the call stack window when that happens.
Besided 2003, I have 2005, 2008 and 2010 and VS 6 on the machine. None of them can be reached via the JIT debugging window.
What is this program trying to do? I see in task manager that it is constantly running when I start 2010 up.
I am on Win7 64 bit OS.
R.D. Holland
Continue reading...