Error while trying to run project : Unable to start debugging.

  • Thread starter Thread starter Ravi Shankar
  • Start date Start date
R

Ravi Shankar

Hi,

I get the below error while I press F5 from Microsoft Visual Studio .NET
Enterprise Architect IDE. This doesn't allow me to debug the application.
But I am able to launch any other C# application when CTRL+F5 is pressed.

"Error while trying to run project : Unable to start debugging."
Unable to start program 'PROGRAM_NAME'

Can anyone suggest some work around?

Regards,

Ravi Shankar
 
Hi Ravi,

Thanks for your post. You may experience the problem as described in the
following KB article:

PRB: Error Message: Unable to Start Debugging. Unable to Start Program
<application name.exe>
http://support.microsoft.com/?id=303067

If the problem persists, please tell me the version of Visual Studio .NET
(2002 or 2003), what the type of your project is (Console, Windows Forms,
Web Application, etc), and check if you can reproduce the problem against a
new wizard-generated only project.

Hope this helps.

Have a nice day! :-)

Regards,

HuangTM
Microsoft Online Partner Support
MCSE/MCSD

Get Secure! -- www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
 
Hi Huang,

Thanks for the reply. I did as it was adviced in the url mentioned. But
the problem still persist. Now I get an additional information stating
"The debugger is not properly installed. Run setup to install or repair
the debugger."

I run the Microsoft Development Environment 2002 Version 7.0.9466 and
Microsoft .NET Framework Version 1.0.3705. My OS is Microsoft Windows XP
Professional Version 2002 Service Pack 1. The type of application is
Windows Forms.

I reproduced the same problem by creating a new wizard-generated only
project.

NOTE: I tried to reply to your mail address (online.microsoft.com) but
got an undeliverable message

Regards,

Ravi Shankar
 
Hello Ravi,

Thanks for your information. According to the error message, the VS .NET
debugger is not properly installed. I'd like you perform the following
steps to manually repair the debugger:

1. Replace the following files with their equivalents from the Visual
Studio .NET installation media:

Program Files\Common Files\Microsoft Shared\VS7Debug\coloader.dll
Program Files\Common Files\Microsoft Shared\VS7Debug\csm.dll
Program Files\Common Files\Microsoft Shared\VS7Debug\msdbg2.dll
Program Files\Common Files\Microsoft Shared\VS7Debug\pdm.dll
Program Files\Common Files\Microsoft Shared\VS7Debug\vs7jit.exe
Program Files\Common Files\Microsoft Shared\VS7Debug\mdm.exe

2. Register each DLL above with regsvr32.EXE, e.g:

regsvr32 "ProgramFiles\Common Files\Microsoft Shared\VS7Debug\coloader.dll"
...

3. Re-register each executable, e.g:

"Program Files\Common Files\Microsoft Shared\VS7Debug\vs7jit" /regserver
"Program Files\Common Files\Microsoft Shared\VS7Debug\mdm.exe" /regserver

If all else fails, please rename Program Files\Common Files\Microsoft
Shared\VS7Debug and then reinstall visual studio.

Please let me know the result.

Have a nice day! :)

Regards,

HuangTM
Microsoft Online Partner Support
MCSE/MCSD

Get Secure! -- www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
 
Hi Huang,

Thanks for the reply. I tried with all your suggestions including
uninstallation and then reinstallation of the Visual Studio .NET but the
problem still persist. Can I upgrade my system to .NET 2003? Will that
suffice?

Any more luck?

Regards,

Ravi Shankar S
 
Hi Ravi,

Thanks for your response.

Does it prompt the same error message? Please go to "Control Panel" ->
"Administrative Tools" -> "Services", and make sure that the "Machine Debug
Manager" is started.
Generally speaking, both VS .NET 2002 and 2003 should debug programs
properly as they do on my system. I am afraid that the problem may be
caused by malfunctioned third-party application or services. I suggest you
to close/stop all other unnecessary application/service (say, anti-virus
application) to check whether or not the problem still exists. You can also
remove VS .NET 2002 cleanly with the steps described in the following MSDN
article:

HOW TO: Manually Remove Visual Studio .NET 2002 Components
http://support.microsoft.com/?id=320114

I look forward to your result.

Have a nice day!

Regards,

HuangTM
Microsoft Online Partner Support
MCSE/MCSD

Get Secure! -- www.microsoft.com/security
This posting is provided "as is" with no warranties and confers no rights.
 
Back
Top