I've narrowed this down a bit. When I start up the Windows Task Manager and
then watch it while I navigate IE to an ASP.NET page on the local system, I
can see the "aspnet_wp.exe" process appear during the time it takes to
generate the page. Once the page is generated, the "aspnet_wp.exe" process
goes away.
So apparently, something isn't configured properly anymore in IIS?
I found that the "Enable ASP server-side debugging" box was not checked in
IIS configuration, the web site properties, "Home Directory" tab,
"Configuration", "Debugging" tab. I checked it, restarted IIS and still no
go.
[quoted text, click to view] "theyas@community.nospam" wrote:
> Windows XP SP2, VS 2003, IIS 5.1, IE 6.0, Symantec AV 9.0.0.xxx
>
> I've been changing things around (and have re-installed IIS and VS 2003) and
> am now at the point where I have things working--except that I cannot debug
> IIS Server processes of ASP.NET anymore. When, in VS 2003, I select "Debug"
> and then "Processes...." I get the list that appears to be the same as
> before, except that I don't see the "aspnet_wp" process. Also, when my
> application throws an exception and I get the dialog box for debugging, it
> will attach to an ASP script, but not delve into the .NET code that is called
> by the ASP script.
>
> And I've also brought up a data service page which before would always start
> up the aspnet_wp process if I had just restarted IIS. It sure seems to me
> like there's just some little setting somewhere that's missing.
>
> Any and all ideas welcome!
>
> Thanks,
>
Hi!
Do you see inetinfo.exe and if so, does attaching to that allow you to debug your web service correctly?
Thanks,
D.V.
--------------------
[quoted text, click to view] >Thread-Topic: Can't find aspnet_wp in list of processes.
>thread-index: AcThRzVMSffEgo0TRlSBhG7o2sYqBg==
>X-WBNR-Posting-Host: 128.165.156.80
>From: "=?Utf-8?B?dGhleWFzQGNvbW11bml0eS5ub3NwYW0=?=" <theyascommunitynospam@discussions.microsoft.com>
>References: <10D37222-9C7E-4122-9273-A8C70B90E840@microsoft.com>
>Subject: RE: Can't find aspnet_wp in list of processes.
>Date: Mon, 13 Dec 2004 11:09:02 -0800
>Lines: 35
>Message-ID: <2DB2C861-1E3C-4BCB-A612-FE804856F9D2@microsoft.com>
>MIME-Version: 1.0
>Content-Type: text/plain;
> charset="Utf-8"
>Content-Transfer-Encoding: 7bit
>X-Newsreader: Microsoft CDO for Windows 2000
>Content-Class: urn:content-classes:message
>Importance: normal
>Priority: normal
>X-MimeOLE: Produced By Microsoft MimeOLE V6.00.3790.0
>Newsgroups: microsoft.public.vsnet.debugging
>NNTP-Posting-Host: TK2MSFTNGXA03.phx.gbl 10.40.1.29
>Path: cpmsftngxa10.phx.gbl!TK2MSFTNGXA03.phx.gbl
>Xref: cpmsftngxa10.phx.gbl microsoft.public.vsnet.debugging:6775
>X-Tomcat-NG: microsoft.public.vsnet.debugging
>
>I've narrowed this down a bit. When I start up the Windows Task Manager and
>then watch it while I navigate IE to an ASP.NET page on the local system, I
>can see the "aspnet_wp.exe" process appear during the time it takes to
>generate the page. Once the page is generated, the "aspnet_wp.exe" process
>goes away.
>
>So apparently, something isn't configured properly anymore in IIS?
>
>I found that the "Enable ASP server-side debugging" box was not checked in
>IIS configuration, the web site properties, "Home Directory" tab,
>"Configuration", "Debugging" tab. I checked it, restarted IIS and still no
>go.
>
>"theyas@community.nospam" wrote:
>
>> Windows XP SP2, VS 2003, IIS 5.1, IE 6.0, Symantec AV 9.0.0.xxx
>>
>> I've been changing things around (and have re-installed IIS and VS 2003) and
>> am now at the point where I have things working--except that I cannot debug
>> IIS Server processes of ASP.NET anymore. When, in VS 2003, I select "Debug"
>> and then "Processes...." I get the list that appears to be the same as
>> before, except that I don't see the "aspnet_wp" process. Also, when my
>> application throws an exception and I get the dialog box for debugging, it
>> will attach to an ASP script, but not delve into the .NET code that is called
>> by the ASP script.
>>
>> And I've also brought up a data service page which before would always start
>> up the aspnet_wp process if I had just restarted IIS. It sure seems to me
>> like there's just some little setting somewhere that's missing.
>>
>> Any and all ideas welcome!
>>
>> Thanks,
>>
>> Lowell
>
--
This posting is provided "AS IS" with no warranties, and confers no rights. Use of included script samples are subject to the terms specified at
http://www.microsoft.com/info/cpyright.htm Note: For the benefit of the community-at-large, all responses to this message are best directed to the newsgroup/thread from which they originated.
