|
|
|||||||||
|
|||||||||
|
|||||||||
| |
||
| ||||||||||||||||||||||||||
![]() |
|
|
«
Previous Thread
|
Next Thread
»
|
Thread Tools | Search this Thread | Rate Thread | Display Modes |
|
#1
|
|||
|
|||
|
Hi all,
Not sure if this is a VS issue or an IIS issue or an ASPNET process issue. BUT The machine used to work, then stopped. Applying a Microsoft security update was coincident with the problem. May be the cause, maybe not. The machine has VS.NET2003, IIS6, and both ASPNET 1.1 and 2.0 installed. When I run a web project in VS, it says Error: unable to start debugging on the web server, and in the development output pane, gives the message up there in the title. If I start the program without debugging, it starts okay, but will not attach. If I open IE and open the web page directly, it works, but then if I attach to the aspnet_wp.exe process, it fails. Curiously, when doing that attach manually, the "Attach to Process" dialog lists the process as v2.0 of aspnet. BUT in the IIS configuration for the default website, it says it will use ASPNET 1.1. If I change IIS to 2.0, it gives the same result. Anybody have a clue as to what is going on here? This has utterly screwed my work and I seem to be at a dead end. Thanks, Joe |
|
#2
|
|||
|
|||
|
This problem seems to be project related. One web project connects okay, but the other one doesn't. Any ideas as to where in the project configuration could cause this problem?
Thanks, Joe |
|
#3
|
|||
|
|||
|
Here's what google finds from that error code.
http://www.google.com/search?q=0x80...:en-US:official
__________________
====== Doug G ====== I didn't attend the funeral, but I sent a nice letter saying I approved of it. --Mark Twain |
|
#4
|
|||
|
|||
|
Hi Doug, thanks for the thought. I did do a google search before, though. The results seem to be on track, but incomplete for this issue.
I have two asp.net projects in VS2003. One runs and debugs and the other fails to attach. I have two aspnet_wp processes running, one apparently 1.1 and one 2.0. The 1.1 version will allow attaching, the 2.0 not. This machine used to work in this configuration, and failed coincident with installation of Microsoft security patches. So where in the individual project does it designate the version of aspnet_wp that VS will use? That seems to be the bearbodkin. Thanks, Joe |
|
#5
|
|||
|
|||
|
Well, going to the aspnet 2.0 folder and running regiis_aspnet -u seems to have resolved the trouble. For now. Until it comes back for no particular reason.
Thanks, Joe |
|
#6
|
|||
|
|||
|
Hi,
You can find the solution at here |
|
#7
|
|||
|
|||
|
solution to "Auto-attach to process ..."
I resolved by changing to the correct ASP.NET version in IIS (for vs2003 changed to 2.
|
|
#8
|
|||
|
|||
|
How about now? Is that problem still come back?
|
![]() |
| Viewing: ASP Free Forums > System Administration > Microsoft IIS > Auto-attach to process 'aspnet_wp.exe' Failed. Error code 0x8013134b. |
| Thread Tools | Search this Thread |
| Display Modes | Rate This Thread |
|
|
|
|
|