Re: aspnet_wp.exe could not be started

the issue you are dealing with is that domain controllers do not have local accounts and for security, iis, aspnet and sqlserver have been converted to local limited priv accounts in their installation.

you have to go thru each and convert to a domain account with the correct permissions. it sounds like you've got sqlserver (its pretty simple because it will setup the account privs).

next you should do iis, then asp.net. iis should have been a domain account (you can check the identity under services).

you should probably uninstall iis and asp.net then reinstall them. it sounds like your iis install is bad. i'd delete the iis metabase file after the uninstall.

-- bruce (sqlwork.com)


Rbrt wrote:
This whole thing has already been discussed in this thread: http://msdn.microsoft.com/newsgroups/default.aspx?query=aspnet_wp.exe+could+not+be+started&dg=microsoft.public.dotnet.framework.aspnet&cat=en-us-msdn-dotnet-frmwrk&lang=en&cr=US&pt=de7bb609-3fd0-4b0f-865d-5ed2463ad5d0&catlist=DEA2432D-EA76-4E5B-AF80-E56902048BAD%2C774F24A2-F71F-425F-AC2B-DC48AB0DA5C9&dglist=&ptlist=&exp=&sloc=en-us

I have exactly the same scenario as the guy who started this thread - IIS on a domain controller. Before you start lecturing me on my setup, I am a professional developer and the reason I have IIS running on a domain controller is that I have a small development network with a server (domain controller/web server/SQL Server) and a couple of workstations. The server also serves as a test deployment server for applications I build for my customers. This should not be unusual given the population of MSDN members (of which I am one). I have talked to a handful of them at Microsoft events who do the same thing.

My server is Win 2003 Server standard, which I upgraded from Win 2000 Server. This in itself was a nightmare and I had to burn one of my 4 support incidents to get it done. Took two days altogether. I couldn't believe how badly it went. All of my software comes from my MSDN subscription.

Now I am trying to deploy an ASP.NET 2.0 app to the server from the development workstation to testbed it.

I have all the same symptoms as discussed in the thread above - no application pools showing up (they were there when I installed ASP.NET 2.0 on the Win 2000 server before I upgraded, and now have disappeared), same error messages in the app log. I did all of the things specified in the KB articles as well as the stuff recommended in the thread... re-registering asp.net, setting up special account, setting permissions, ....

The big difference for me is that I put the user account and password in the machine.config file and it still does not work.

Please do not lecture me about not running IIS on a domain controller. This is a development environment and it is very tightly secured behind a firewall. And please, no lame comments from the Linux crowd, OK? We've heard it all before. When my customers switch to Linux, then maybe I will too. Until then, I work with what they've got.

Any advice from anybody else out there who has gone through this nightmare would be greatly appreciated.

Thanks

Robert

.

Relevant Pages

  • RE: SOME Users cannot access OWA others do, error HTTP 500
    ... I understand that some account access OWA ... IIS 6.0 compression corruption causes access violations ... compressed copy of the affected files on the SBS server: ...
    (microsoft.public.windows.server.sbs)
  • Re: Virtual Directory - Permission Denied with fso CopyFile
    ... TestUser (normal user account with same credentials on all machines). ... I logged into the IIS server as vdirUser and simply typed ... open and I had read and write permissions to the share. ... I logged off and back into the IIS server as the administrator and deleted ...
    (microsoft.public.inetserver.iis)
  • Re: I hate IIS - "Server Application Unavailable" error message
    ... this is on a Win2003 Server. ... complaints or warnings installing IIS for me. ... as the SYSTEM account on a domain controller, although I would encrypt the section. ...
    (microsoft.public.dotnet.framework.aspnet)
  • Re: IISlockdown doesnt allow asp !!!
    ... You IIS server is a DC right? ... > It's bcos i can't access the "Domain Controller Security Policy", ... go to your Domain Controller Security policy. ...
    (microsoft.public.inetserver.iis.security)
  • Re: Unable To Add DC
    ... I have reloaded it with 2003 server again and given ... I have gone into active directory users and computers then ... it still had the old domain controller in there, ... account SERVERNAME$ to a domain controller ...
    (microsoft.public.windows.server.active_directory)