unable to debug:debugger is not properly installed.

[Kevin Goff]

I receive the following error when trying to debug an asp.net application:

Error while trying to run project: Unable to start debugging on the web
server. The debugger is not properly installed. Run setup to install or
repair the debugger. Would you like to disable future attempts to debug
ASP.NET pages for this project?

Here is my setup:
I am on a single domain trying to do remote debugging.
My client machine has vs7 installed (final) and the server has .net runtime
(final) downloaded from the asp.net website.

The server processes asp pages fine, just does not debug them. If I move
the files to the client machine I can debug fine so I think the problem is
with the server.

I am a member of the local admin and debugger users of the server machine.

The project is configured for debugging. The server machine.config is
configured for debugging.

When I go to debug:processes from VS on the client I can see all the
processes running on the server but when I try to attach to aspnet_wp i get
:
Unable to attach to the process. The debugger is not properly installed.
Run setup to install or repair the debugger.

Thanks in advance,
Kevin Goff
kevin_goff@myemaildomain
myemaildomain = gallup.com

[Min Kwan Park[MSFT]]

Please make sure that "mscordbi.dll" is registered properly. it sounds like
that the dll is not registered.

thanks
Min

--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Kevin Goff" <kevin...@hotmail.com> wrote in message
news:#Skq487wBHA.2556@tkmsftngp07...

[Kevin Goff]

I ran regsvr32 on this dll on the server and it registered successfully.
The problem still exists.

Kevin

"Min Kwan Park[MSFT]" <mkp...@microsoft.com> wrote in message
news:ODVZ#V8wBHA.2200@tkmsftngp07...

[Min Kwan Park[MSFT]]

Can you check these things?
- Can you attach to any other managed process on remote machine? I want to
know whether it is aspnet only issue or not.
- Run IE on server machine, and attach to the IE process in Script mode. and
Can you see whether you can attach it or not.
- When you fail to attach, Can you see "vs7jit.exe" process on the remote
server?
- You installed "Full remote debug setup" on remote server, right?

thanks
Min

--
This posting is provided "AS IS" with no warranties, and confers no rights.
"Kevin Goff" <kevin...@hotmail.com> wrote in message

news:uKgXCf#wBHA.2752@tkmsftngp04...

[Unknown]

I had the same problem and then followed these instructions and the problem was solved:

Remote Debugging with DCOM and the Machine Debug Manager
For remote debugging using DCOM, the Machine Debug Manager (MDM.exe) must be installed and running on the remote machine. MDM.exe runs as a service, which can be configured using the Services control panel.

There are three ways to set up DCOM remote debugging.

You can install a full, licensed version of Visual Studio .NET on the remote machine.
You can run the Visual Studio Setup CD-ROM on the remote machine and choose Remote Components Setup in the setup wizard. This will install only the remote debugging components. After selecting Remote Components Setup, you will have two options.
Native Remote Debugging installs components that enable a debugger to connect for debugging of native code only.

Full Remote Debugging installs components that enable a debugger to connect for debugging of native code, managed code running on the Common Language Runtime, and script (VBScript or Jscript). If SQL Server is installed on the machine, components for SQL remote debugging will be installed as well.

For more information, see Remote Components Setup.

You can manually install a minimal set of required components for native remote debugging. These files are:
msvcmon.exe
msvcr70.dll
natdbgtlnet.dllnatdbgdm.dll

psapi.dll (NT4 only)

For dump support (for more information, see Dumps), install this file as well:

dbghelp.dll (supports dumps)

You can copy all of these files to the same location on the remote server, or you can run them from a share on the local machine where you are running Visual Studio .NET. Using a share allows you to debug an application running on a remote machine where you cannot install files.

**********************************************************************
Sent via Fuzzy Software @ http://www.fuzzysoftware.com/
Comprehensive, categorised, searchable collection of links to ASP & ASP.NET resources...

[Kevin Goff]

Thanks for the help Michael and Min. The problem was that I had used the
downloaded version of the .net runtime and not a visual studio .net
installation that installs the full debugger.

If I have 3 developers and a central debugging machine do I need to have 3
licenses or 4?

"Michael Odekirk" <mi...@odekirks.org> wrote in message
news:#hBIe4#wBHA.2208@tkmsftngp05...