Server Fault is a question and answer site for system and network administrators. It's 100% free, no registration required.

Sign up
Here's how it works:
  1. Anybody can ask a question
  2. Anybody can answer
  3. The best answers are voted up and rise to the top

I use mostly Apache and PHP, so I'm very unfamiliar with IIS and .aspx

I have a .aspx file (myFile.aspx) I'm debugging, and I would like to see - using localhost - what it will look like on the server (which is Windows 2003, I think) when looked at by a user. I'm using Windows 7 for debugging, but the project lives - and will continue to live - on a Windows 2003 server.

I have IIS up and running, so initially when I went to http://localhost/, I could see the IIS logo. I now have the Physical Path pointing to the directory with my ASP project.

The problem is that due to the server mismatches, when I go to the page (myFile.aspx) I get a server error because the related configuration data (web.config) for the page is invalid (HTTP Error 500.19 - Internal Server Error - The requested page cannot be accessed because the related configuration data for the page is invalid.).

How can I work around this? Are there any good tutorials that cover this matter? Any help appreciated.

share|improve this question
If your OS is Server 2003, you aren't running IIS 7 because IIS is tied to the OS and only became available on Server 2008 – GregD Oct 5 '11 at 23:57
@GregD - My OS is Windows 7 for my personal computer on which I want to debug the file. After I debug the file I want to upload it to a completely separate Windows 2003 Server which serves the file to the WWW. I want to test the file on my personal computer and not the live server. – Peter Ajtai Oct 6 '11 at 0:10
Your title says, "Windows 2003 server with IIS7"...that combo does not exist... – GregD Oct 6 '11 at 0:13
@GregD, the words before that phrase were important too, but I reworded the title to make it - hopefully - more clear. – Peter Ajtai Oct 6 '11 at 0:57

A simple Google or Bing search for this may have helped:

This has all of the potentially related error messages you are seeing and more importantly tells you exactly what to look at to get it fixed.

share|improve this answer

what important stuff is in your web.config? I would remove everything except the stuff you need. If your situation is complex, you might want to get your hands on a test server. You could get a virtual machine from godaddy for $30 for a month...

share|improve this answer
-1 He already has a Win7 and 2003 box, why would he need a test server? – Brent Pabst Aug 8 '12 at 23:24
Because he doesnt have a test machine with iis 6? The 2003 box is prod right? – trevdev Aug 9 '12 at 3:30
Just because it's prod doesn't mean you can't create another VD to test with... Plus if you can get it to run in IIS7 most likely it will run in IIS6 – Brent Pabst Aug 9 '12 at 10:50

Your Answer


By posting your answer, you agree to the privacy policy and terms of service.

Not the answer you're looking for? Browse other questions tagged or ask your own question.