Jerry,

The 500 Server Error is a generic error message that indicates a problem in the application - of which default.aspx is a part of. To troubleshoot the problem, you can either 1. enable the full error message for all users, or 2. trap application errors in the global.asax class and write them to a file or the event log.

If you go with option 1, you will be eliciting the help of the users to troubleshoot the error. This may not really be an option for you.

To enable the raw error message for all users, make sure that you are using the Debugging mode for the project (in the Project Properties builder) and change customErrors mode= in the web.config to customErrors mode="Off". Now when an unhandled exception occurs, the user will see the complete error message and source code that caused the message.

The cleaner way to troubleshoot is to install an exception handler in the global.asax file. Put the error handling code in the Application_Error method. For more info, see ms-help://MS.VSCC.2003/MS.MSDNQTR.2005JAN.1033/vbcon/html/vbtskDisplayingSafeErrorMessages.htm in the 2003 help file. You will have to add code to write to the server's event log.

>We have a website that I developed using VFP and West-Wind. The website has been running for years. Recently, I changed the home page of the website to use a webform I created in ASP.Net with SQL Server as it's database.
>
>The form works great. However, two of our customer's have called saying that they are no longer able to get to our website. Whenever they attempt to go to our home page, which is a default.aspx page, they get a .Net Server Error message. These two customers are using IE6 on an XP OS with SP2. But they cannot view my default.aspx page.
>
>Luckily, I still have the default.htm page available. These two customers can get to our default.htm page and view the menu and use our website but they definately cannot view the default.aspx page.
>
>What would cause something like this to happen. So far only two customers have had this problem, but what if more start having this problem. Has anyone seen this happen before?
>
>Thanks,
>
>Jerry