Did you try any of the suggestions given to you yesterday to get a more descriptive error message from an appropriate source (IIS, http.sys or Windows Event Log)?
Making random configuration changes in the hope that it fixes the problem usually isn't a productive way to solve problems in my experience. You may get lucky, or you may not. Usually better to get an error message/reason, then work on things that might correct that particular issue. Cheers Ken From: [email protected] [mailto:[email protected]] On Behalf Of Greg Keogh Sent: Wednesday, 5 January 2011 2:03 PM To: 'ozDotNet' Subject: RE: 500 - Internal server error I have created a "hello world" ASP.NET web site in Framework 2.0 and 4.0, and a similar simple service in Framework 4.0. They both work on my Win2003 server, but all give 500 errors when the same files are copied to the Win2008 server with identical app properties. This indicates that it's not just a web service problem, or just a Framework version problem. Something is therefore completely cactus for all .NET web apps on the new server. But what is it? Greg
