Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Debug Failure: No Managed Code in Process?!?

580 views
Skip to first unread message

Mikkel Rasmussen

unread,
Aug 5, 2003, 5:38:55 AM8/5/03
to
Hi

I recently installed a fresh 2003 server, xcopied an existing asp.net
application to the server.

when I try to debug the application I get this error:

"Error while trying to run project.: Unable to start debugging on the
webserver. There is no managed code running in the process. In order to
attach to a process with the .NET debugger, managed code must be running in
the process before attaching."..

...duh?!? the web-app is coded 100% in C#, and I've heard, this compiles to
managed code. Anybody out there with a solution?

checklist:
IIS 6.0, .Net framework 1.1, remote debugging, account is "Debugger User"
and "Administrators", has Full Control over application directory,
web.config specifies debug="true", authentication has been set to
"Integrated Windows", Solution was built and rebuilt several times and when
trying to attach to the process manually, I get the same error.

Monica Rosculet

unread,
Aug 15, 2003, 8:04:18 PM8/15/03
to
Hello,

Have you created a virtual directory for your application after you copied
it? To do this, go to IIS Manager and select your application's directory
under the Default Web Site. Right-0click on it, select Properties, go to
the Directory page and click the Create button.
Other thing to check:
In IIS manager, go to Server Extensions and make sure ASP.NET 1.1 is
allowed.

Hope this helps,
Monica

--------------------
>From: "Mikkel Rasmussen" <mik...@emikkel.dk>
>Subject: Debug Failure: No Managed Code in Process?!?
>Date: Tue, 5 Aug 2003 11:38:55 +0200
>Lines: 24
>X-Priority: 3
>X-MSMail-Priority: Normal
>X-Newsreader: Microsoft Outlook Express 6.00.2800.1158
>X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2800.1165
>Message-ID: <uB34kVzW...@TK2MSFTNGP11.phx.gbl>
>Newsgroups: microsoft.public.vsnet.debugging
>NNTP-Posting-Host: fw.int.webpartner.dk 213.150.34.98
>Path: cpmsftngxa06.phx.gbl!TK2MSFTNGP08.phx.gbl!TK2MSFTNGP11.phx.gbl
>Xref: cpmsftngxa06.phx.gbl microsoft.public.vsnet.debugging:2991
>X-Tomcat-NG: microsoft.public.vsnet.debugging

rohini-simha

unread,
Dec 29, 2010, 4:04:37 AM12/29/10
to
Mikkel Rasmussen wrote on 08/05/2003 05:38 ET :
> Hi
>
> I recently installed a fresh 2003 server, xcopied an existing asp.net
> application to the server.
>
> when I try to debug the application I get this error:
>
> &quot;Error while trying to run project.: Unable to start debugging on the

> webserver. There is no managed code running in the process. In order to
> attach to a process with the .NET debugger, managed code must be running in
> the process before attaching.&quot;..

>
> ...duh?!? the web-app is coded 100% in C#, and I've heard, this compiles to
> managed code. Anybody out there with a solution?
>
> checklist:
> IIS 6.0, .Net framework 1.1, remote debugging, account is &quot;Debugger
> User&quot;
> and &quot;Administrators&quot;, has Full Control over application directory,
> web.config specifies debug=&quot;true&quot;, authentication has been set to
> &quot;Integrated Windows&quot;, Solution was built and rebuilt several times

> and when
> trying to attach to the process manually, I get the same error.
>
CLOSE ALL IE WINDOWS and start Debug. There will not be any conflict and hence
the DEBUG WILL Happen on the only available IE window :)
0 new messages