If you are receiving an IIS ASP.NET error message after installing the application the first step is to make sure that you can view the error details.
To enable this, you must edit the web.config files custom errors tag; <customErrors
mode="RemoteOnly" />
should be changed to; <customErrors
mode="Off" />
This will allow you to view the ASP.NET error message and therefor be able to rectify the problem. Note: You may want to change this back once you have application running as you don't usually want to have any error message details displayed to your end users in the unlikely event of an application error.
Common Problems
Message:
Server error in 'appname'/ Could not load type... Possible Cause:
Missing or inaccessible application (bin\application.bin) file.
Message:
There can be only one 'page' directive...
Possible Cause:
There is more than one '<%@ Page LANGUAGE="c#" %>' declaration in a file usually becuase Visual Studio added a second one on creation of a project to a file which has an .ASPX extension and a protect include. Remove one!
Message:
Server error in '/' application ... Possible Cause:
Folder containing application is not set as an application.
For self hosted sites, use IIS to set the folder as an application;
For ISP hosted sites, use provided wizard in ISPs control panel or adhere to a preset application folder.
Message:
Application Generated: Login System Error... Possible Cause:
Check database is correctly named and visible+writable to the ASP.NET user.
For self hosted sites makes sure the ASP.NET user account has access to the database file, example;
For ISP hosted sites, use provided wizard in ISPs control panel to set file permissions or use special 'db' folder if provided.
