Glad to see the issue was GoDaddy. I've steered clear of their hosting offerings as all I hear is trouble.
From: [email protected] [mailto:[email protected]] On Behalf Of Greg Keogh Sent: Thursday, 6 January 2011 12:48 PM To: [email protected]; 'ozDotNet' Subject: RE: 500 - Internal server error Glen, Ken, Folks After a couple of hours, thanks for procmon telling which accounts were getting ACCESS DENIED I managed to get a plain web site working, then as simple ASPX page and a simple SVC displaying in a browser. I had to enable Basic, Windows and Anonymous authentication, then assign the Classic ASP.NET 4 pool to NETWORK SERVICE, then give IUSR read permissions to all web site folders and ASP.NET app virtual folders, then give NETWORK SERVICE modify permission to ASP.NET virtual folders. What worries me is: why did I need to set permissions? I've never done it before and it seems wrong. So wrong that I suspect I must have some fundamental IIS setting wrong elsewhere. The GoDaddy domain is now totally screwed to hell and I'm trying to delete and recreate it, but even that hasn't worked. it's disabled the domain and there is no obvious way to delete and recreate it with defaults back again. Somehow I destroyed the aspx handler in the domain and nothing will get it working again. I'm getting MIME errors and it thinks ASPX files are script files and won't serve them. So now we're making a ticket with GoDaddy support asking how to delete and recreate a domain. Now I have proof that my vanilla Win2008 box and serve htm, aspx and svc files after careful tweaking, this indicates that my problems on the GoDaddy Win2008 box are specific to it. A warning to anyone about GoDaddy ---> Their virtual server's are over-engineered with an administrative tool called PLESK. It's a comprehensive and clever web front-end management tool for almost everything in the Win2008 OS. The trouble is that it puts its sticky fingers into almost everything in the OS and makes traditional management tasks nearly impossible, as you seem to be fighting it all the way. It has put non-standard handlers into all of the web sites, and I removed and destroyed one of them. I'm not confident that a dedicated IIS forum would be of much help either. All of the advice so far in here has made perfect sense, but the GoDaddy box resists all efforts to configure it. Greg
