I was just about to tell the customer to reinstall the OS, when he called me and told me he got a new computer and he was going to install it on the new computer instead of the old. When installing IIS on the new computer he did not run into any problems. Problem solved "That was easy!"

>I think I might have seen it once upon a time. It sounds familiar. I don't remember what my solution was. Just how I researched info on fixing it.
>
>>Perry,
>>Yes it seems like I (or should I say one of customers) has encountered the infamous-http-500-error-on-localhost.
>>Have you encountered this yourself? I should just tell my customer to call M$ tech support :)
>>
>>Thanks for the link
>>
>>
>>>Here's a couple places that might help:
>>>
>>>http://www.iisfaq.com/
>>>http://forums.aspfree.com/microsoft-iis-12/infamous-http-500-error-on-localhost-23593.html\
>>>
>>>
>>>>I didn't find a good category for my question but since ASP.NET apps mostly runs on the IIS server I figured this must be as good of a place as any.
>>>>A customer installed IIS (through adding windows components), but when he types localhost in the address bar of his browser he gets an error back. Computer has been restarted numerous times. I ran aspnet_regiis.exe. The error is a standard 500 internal error or something. I guess I could remove the friendly error message to show the real error message, but I've got a feeling that will not be too helpful either.
>>>>
>>>>So my question is: Does anyone know what could have gone wrong? What should I do next?
>>>>
>>>>I think reinstalling IIS might be the best plan. How do I uninstall IIS (do I just uncheck the checkbox in add or remove windows components?)
>>>>
>>>>Thanks,
>>>>Einar