By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
439,978 Members | 1,362 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 439,978 IT Pros & Developers. It's quick & easy.

cannot attach to aspnet_wp.exe

P: n/a
i have a DLL which implements a HTTP handler, written in C#, and have
deployed it on IIS 5.0, on XP service pack 2.
six months ago, i was able to debug it by attaching CLR to the process
(aspnet_wp.exe).
now i can't attach to the process any more. when i select the process from
the list, and then select to attach the CLR, i just get a dialog box saying
"Cannot attach to process". there is no more info, nothing to direct me
further.
incidentally, i can still attach CLR to other processes and debug them
properly.

any help much appreciated.
Nov 19 '05 #1
Share this Question
Share on Google+
4 Replies


P: n/a
Are you sure the DLL created in the Debug configuration?

DalePres
MCAD, MCDBA, MCSE

"donall" <do****@discussions.microsoft.com> wrote in message
news:21**********************************@microsof t.com...
i have a DLL which implements a HTTP handler, written in C#, and have
deployed it on IIS 5.0, on XP service pack 2.
six months ago, i was able to debug it by attaching CLR to the process
(aspnet_wp.exe).
now i can't attach to the process any more. when i select the process from
the list, and then select to attach the CLR, i just get a dialog box
saying
"Cannot attach to process". there is no more info, nothing to direct me
further.
incidentally, i can still attach CLR to other processes and debug them
properly.

any help much appreciated.

Nov 19 '05 #2

P: n/a
Check your application directory for the presence of a .pdb file. You may
try rebuilding this pdb file because it may be corrupted or unusable.

--
Regards,
Alvin Bruney [MVP ASP.NET]

[Shameless Author plug]
The Microsoft Office Web Components Black Book with .NET
Now Available @ http://tinyurl.com/27cok
----------------------------------------------------------
"donall" <do****@discussions.microsoft.com> wrote in message
news:21**********************************@microsof t.com...
i have a DLL which implements a HTTP handler, written in C#, and have
deployed it on IIS 5.0, on XP service pack 2.
six months ago, i was able to debug it by attaching CLR to the process
(aspnet_wp.exe).
now i can't attach to the process any more. when i select the process from
the list, and then select to attach the CLR, i just get a dialog box
saying
"Cannot attach to process". there is no more info, nothing to direct me
further.
incidentally, i can still attach CLR to other processes and debug them
properly.

any help much appreciated.

Nov 19 '05 #3

P: n/a
there were pdb files in my debug directory. so i tried rebuilding the
solution from scratch, but to no avail. i reverted to old-fashioned debugging
through trace code to get me through this urgent problem, and i'll get around
to doing more investigation when i get more time.
thanks to Dale and Alvin for your suggeestions.

"Alvin Bruney [MVP]" wrote:
Check your application directory for the presence of a .pdb file. You may
try rebuilding this pdb file because it may be corrupted or unusable.

--
Regards,
Alvin Bruney [MVP ASP.NET]

[Shameless Author plug]
The Microsoft Office Web Components Black Book with .NET
Now Available @ http://tinyurl.com/27cok
----------------------------------------------------------
"donall" <do****@discussions.microsoft.com> wrote in message
news:21**********************************@microsof t.com...
i have a DLL which implements a HTTP handler, written in C#, and have
deployed it on IIS 5.0, on XP service pack 2.
six months ago, i was able to debug it by attaching CLR to the process
(aspnet_wp.exe).
now i can't attach to the process any more. when i select the process from
the list, and then select to attach the CLR, i just get a dialog box
saying
"Cannot attach to process". there is no more info, nothing to direct me
further.
incidentally, i can still attach CLR to other processes and debug them
properly.

any help much appreciated.


Nov 19 '05 #4

P: n/a
Another thing to try is deleting the VSWebCache folder at C:\Documents and
Settings\<%Your Login Name%>\VSWebCache

Sometimes it gets corrupted and can cause the symptoms you describe as well.

DalePres
"donall" <do****@discussions.microsoft.com> wrote in message
news:83**********************************@microsof t.com...
there were pdb files in my debug directory. so i tried rebuilding the
solution from scratch, but to no avail. i reverted to old-fashioned
debugging
through trace code to get me through this urgent problem, and i'll get
around
to doing more investigation when i get more time.
thanks to Dale and Alvin for your suggeestions.

"Alvin Bruney [MVP]" wrote:
Check your application directory for the presence of a .pdb file. You may
try rebuilding this pdb file because it may be corrupted or unusable.

--
Regards,
Alvin Bruney [MVP ASP.NET]

[Shameless Author plug]
The Microsoft Office Web Components Black Book with .NET
Now Available @ http://tinyurl.com/27cok
----------------------------------------------------------
"donall" <do****@discussions.microsoft.com> wrote in message
news:21**********************************@microsof t.com...
>i have a DLL which implements a HTTP handler, written in C#, and have
> deployed it on IIS 5.0, on XP service pack 2.
> six months ago, i was able to debug it by attaching CLR to the process
> (aspnet_wp.exe).
> now i can't attach to the process any more. when i select the process
> from
> the list, and then select to attach the CLR, i just get a dialog box
> saying
> "Cannot attach to process". there is no more info, nothing to direct me
> further.
> incidentally, i can still attach CLR to other processes and debug them
> properly.
>
> any help much appreciated.


Nov 19 '05 #5

This discussion thread is closed

Replies have been disabled for this discussion.