[thelist] IIS Nightmare

[Jeff Howden]

Ken,

><><><><><><><><><><><><><><><><><><><><><><><><><><><><><
> From: Ken Schaefer
>
> If indeed the metabase is corrupt, then one solution
> maybe to uninstall IIS, delete the metabase.bin file
> (which is where the metabase resides), and then
> reinstall IIS. You'd need to recreate your settings
> etc however.
><><><><><><><><><><><><><><><><><><><><><><><><><><><><><

Indeed, the metabase *was* corrupt and a reinstall, check that it's working,
restore of previously backed-up settings, and check to see that it crashes
proved to me that it was the metabase.  So, another uninstall, reinstall,
and recreation of settings by hand had me back in business.  *Now*, if I
could just identify what is corrupting the metabase, life would be much
better.

><><><><><><><><><><><><><><><><><><><><><><><><><><><><><
> Another possible troubleshooting step might be to use
> the IISState tool from:
> http://www.iisfaq.com/default.aspx?view=P197
> which you'd need to attach to the inetinfo.exe process
> to see what's causing W3WSC service to crash.
><><><><><><><><><><><><><><><><><><><><><><><><><><><><><

The catch-22 with this tool is inetinfo.exe has to be running long enough to
get the PID from Task Manager, run IISStat from the command-line with that
PID, crash, and then read the debug output.  Unfortunately IIS was crashing
when trying to start the service so it never was resident in memory long
enough to accomplish and, of course, the PID changes every time you try to
start it.

Thanks,

Jeff

——————————————————————————————————————————————————————
Jeff Howden - Web Application Specialist
Résumé - http://jeffhowden.com/about/resume/
Code Library - http://evolt.jeffhowden.com/jeff/code/