This gets weirder and weirder as we dig in deeper.
re:
I deleted the IUSR and IWAM accounts
Bad move. That wasn't necessary, and creates a host of problems.
Did you recreate the IWAM account ?
You'll need to, and you'll have to reassign IWAM_KILLER's
new credentials to the processes which use IWAM_KILLER.
You'll also need to recreate the IUSR_KILLER account.
re:
The IWAM account is the Built-in account for
Internet Information Services to start out of process applications.
If you deleted the IWAM account, it cannot run and can't start the IIS process.
The IWAM account is not created by IIS. It's created by your OS.
re:
'The server process could not be started because the configured identity
is incorrect. Check the username and password.
Again, the server process ( in this case ASP, not ASP.NET ), couldn't start
because the IWAM account doesn't exist, so the IIS process can't be started,
and the ASP process needs the IIS process to be able to run.
Resolution :
Recreate the IUSR_KILLER and IWAM_KILLER accounts.
Follow the instructions in this KB to assign "Logon as a batch job" rights :
http://support.microsoft.com/default.aspx?scid=kb;en-us;297519
That should get you up and running again
....and it may uncover new permission-related problems.
You might want, just in case, to read this KB article :
http://support.microsoft.com/kb/297989/EN-US/
In particular, read closely the "Method 1" and "Method 2" parts,
as well as the "Using Adsutil.vbs".
*Never* delete computer accounts unless you are very sure of whjat you're doing.
Juan T. Llibre
ASP.NET MVP
http://asp.net.do/foros/
Foros de ASP.NET en Español
Ven, y hablemos de ASP.NET...
======================