November last year I posted a story with this title. It was a fix for the error messgae above. I wasn't the only one having this problem, over time many many comments and comments on the comments were added. It should be turned into a Wiki. In this post I will try to summarize the most usefull comments.
In the original post I suggested
- aspnet_regiis -i
to fix the problem. This can be done in a jiffy. In the course of the comments the most succesfull script has grown to
- uninstall IIS
- delete (rename) the inetpub directory
- Make sure the "Distributed Transaction Coordinator" service is running
- reinstall IIS
- regsvr32 aspnet_isapi.dll
- perform aspnet_regiis -i
which is quite a big job.
What shines through in a lot of the comments is that the problem is often a security setting. The many installations will set the permissions leading to an ASP.NET server working right. Correcting the permissions by hand might be a faster fix. So before you follow this script I suggest you check the ASPNET account. Does it have sufficient permissions in the wwwroot directory ? Might be a lot a faster.
<Update>Check this post for a detailed description of the security settings.</>
Peter