This section should help you troubleshoot common issues with installting and operating BugNET.

1. Troubleshooting ASP.NET and IIS issues

The most common issues with installing BugNET on IIS

Here are the steps to discover if IIS is serving ASP.NET pages properly.

1. Read the installation documenation.
2. See if the default installer page is working. Try opening the following URL on your server:
   http://yourserver.com/bugnetvirtualfolder/install/install.aspx
3. See if any aspx pages work.
   http://yourserver.com/bugnetvirtualfolder/default.aspx
4. Check that you created a Virtual Directory in IIS and you pointed it at the location where you have installed BugNet.
5. Check the Virtual Directory in IIS is configured to run ASP.NET 2.0. Also it should be bound to an IIS "Application Pool". 
6. Check that you are allowing default.aspx to be in the list of default documents.
7. Check the Application Pool to see if all is configured ok. Find out what user the Application Pool that BugNET is configured to run as. (Tyically "Network Service" or "ASPNET" users on the local machine).
8. Check that the Application Pool user on the local machine has permissions to the curent BugNET folder. Check that "Network Service" (or user SQL 2005 or SQL express) can read and modify the database location (found in APP_DATA in the BugNET folder).
9. Check your Event Log for any error messages pertaining to "IIS", "ASP.NET 2.0" or "SQL Server".
10. De-register ASP.NET with IIS by running the following command:
    c:\windows\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis -u
    
11. Register ASP.NET with IIS by running the following command:
    c:\windows\Microsoft.NET\Framework\v2.0.50727\aspnet_regiis -i

Back to User Guide Table of Contents