Member Avatar for Venks

Hi all..

I have two dropdown list boxes in an aspx page to which i have to load items from the database..When i run the application i am getting the following error...

Auto- attach to process '[3236] aspnet_wp.exe' on 'machine 171' failed

Someone help in this regard..very urgent..

Regards,


Balaguru

  • 2 Contributors
  • 4 Replies
  • 105 Views
  • 1 Day Discussion Span
  • Latest Post Latest Post by hollystyles

Dani AI

Generated

— the thread already points to a debugger/runtime mismatch and is on the right track. Below are practical, non‑redundant checks and safe troubleshooting steps that complement the earlier suggestions without repeating the exact IIS setting already posted.

  • Try a manual attach instead of relying on auto‑attach: use Visual Studio Debug > Attach to Process, enable "Show processes from all users" and "Show processes in all sessions", pick the web server worker process, and ensure the Attach Type is set to managed code. See Microsoft's guide to attaching the debugger for details ().
  • If the web app is on another machine, verify the remote debugger matches your Visual Studio version, the remote debugging monitor is running, and any firewalls allow the debugger ports (Remote debugging).
  • Permission and process visibility: run Visual Studio elevated (administrative rights) so it can attach to system processes. If the worker process runs under a service account, confirm that account and your user have attach/debug rights.
  • Framework registration and IIS state: if script mappings or framework registration are inconsistent, re-register the framework handlers and recycle the application pool (or restart IIS) after changes. Check Event Viewer for related errors when attach fails.
  • If the app targets a newer CLR than your IDE supports, use an IDE version that matches the runtime, or host the app under a runtime your IDE can debug.

Caution: restarting IIS or changing app pool settings affects all sites on that server — do this in maintenance windows on production hosts.

Recommended Answers

All 4 Replies

Member Avatar for hollystyles

To me this looks like the debugger is trying to attach to the process. This can be caused if you have both framework 1.1 and 2.0 on your machine and an IIS virtual folder configured for framework 2.0, but you are trying to debug with VS 2003. Or some such mismatch of CLR's and debugger.

Member Avatar for Venks

Hi HollyStyles..

Thank u very much for the help.The problem is exactly which u had mentioned..i

Member Avatar for Venks

[Yes,I have both framework 1.1 and 2.0 on my machine and an IIS virtual folder configured for framework 2.0, but i am trying to debug with VS 2003.I couldn't do so..
Can u give me the solution to solve it ..i.e to debug with VS 2003..?

Member Avatar for hollystyles

In IIS right click the virtual folder for your project and select properties. Click the ASP.NET tab, In the ASP.NET Version drop down select 1.1.4322, click the apply button and click OK. That's it.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.