Some .asp pages not working

Ok, I am putting into production a new web server, 2003 Server. I copied all of my web pages over to the new server, including my web site created in Dreamweaver. I copied all of my databases over to the server, everything is copied to the same path as was on the old server. I have gone into the ODBC panel and registered all of my databases, used the correct source name, etc. When I try to fire up most of my .asp pages (which pull content from a database) I get a 500 server error that the page cannot be viewed.

I'm at a loss here. Any ideas why this stuff is not working?

Who is Participating?
moduloConnect With a Mentor Commented:
PAQed with points refunded (500)

Community Support Moderator
Lee W, MVPTechnology and Business Process AdvisorCommented:
You've enabled ASP, right:
This Microsoft KB Article should explain how to enable ASP on IIS 6.0

If so, turn off the Friendly HTTP error messages and find out WHAT is causing the error.
Chris DentPowerShell DeveloperCommented:

500 is a very very generic error, it covers absolutely anything going wrong in ASP from simple page processing to a server-side application error.

If it's a page processing error you can check a combination of the server event log and web server log files - the log files will include the file name and (perhaps more importantly) the line number and error message.

As an example this is a line from an IIS 6.0 Log:

2005-03-22 15:56:00 GET /Index.asp |8|800a0401|Expected_end_of_statement <c-ip> HTTP/1.1 Mozilla/5.0+(Windows;+U;+Windows+NT+5.1;+en-GB;+rv:1.7.5)+Gecko/20041110+Firefox/1.0 <referrer> 500 636

The |8|800a0401|Expected_end_of_statement field represents the full details of the error. And indicates that I've done something silly in my ASP code on line 8 ;)

If it's a more generic error the cause is most likely to be permissions - this can include system policies and everything should be checked carefully.

A combination of RegMon and FileMon from can help a lot for discovering incorrectly set permissions.

Check the file level permissions are correct for both the Process Account and the Anonymous Access account (IWAM and IUSR respectively) - especially to any databases you use. If your ASP is .NET ensure that the ASPNET account has the correct permissions assigned.

Check the application pool the site is running under. To test the process account create a new local account (like IWAM_yoursitename), add it to the IIS_WPG group and assign that as the identity for the application pool it uses.

For .NET you can catch more detail of the error message by viewing the site on the server itself - by default a lot of the troubleshooting information is not sent to client browsers.

Post again if nothing in that helps at all :)

crbushAuthor Commented:
Thanks for your suggestions. I checked the logs and discovered with a little searching, that the issue was related to parent paths being disabled. Apparently, they are not enabled in II6. Once I enabled them, everything works perfect.
>Once I enabled them, everything works perfect.

They are disabled by default because they are unsafe, FYI.  I know you want your web site to *work* but you will need to eventually find the pages using ../ notation (say in server side includes or MapPath() calls) and replace the references with virtual paths or FQDNs.

All Courses

From novice to tech pro — start learning today.