IIS Common Issues and solutions

Below are some common IIS issue in its solutions

1. "User is not recognized using Windows Authentication"

• Open Internet Information Service Manager
• Find the application pool for Pronestor (pronestor)
• Right click and choose advanced settings
• Ensure that "Identity" is set to Network Services
• Recycle application pool
   

2>     "HTTP 502 - Bad gateway"

• Open Internet Information Service Manager
• Find the application pool for Pronestor (pronestor)
• Right click and choose advanced settings
• Ensure that "Identity" is set to Network Services
• Recycle application pool
   

3>     "HTTP 500 internal server error" / "HTTP 500.19 internal server error" / "HTTP 500.21"

• Open a command prompt
• Go to the folder for the .NET Frame (C:\Windows\Microsoft.NET\Framework64\v4.0.30319)
• aspnet_regiis.exe –i

And

• Make sure .NET is enabled as a feature ("add/remove Programs" -> "Turn Windows features on or off")

And

• Make sure ASP.NET is enabled as a role("add/remove Programs" -> "Turn Windows features on or off")

And

• Ensure that "IIS_IUSRS" has full permissions on the PRONESTORDISPLAY folder

And (if "Handler" is showing MVCScriptMap64)

• Ensure the handler mapping for MvcScriptMap64 is set to use .NET 4.0 framework
• "PageHandlerFactory-Integrated" bad module "ManagedPipelineHandler in IIS7..."
• Open a command prompt
• Go to the folder for the .NET Frame (C:\Windows\Microsoft.NET\Framework64\v4.0.30319)
• aspnet_regiis.exe -i
   

4>     "Absolute physical path "C:\inetpub\custerr" is not allowed in....

• Please open the Event Viewer and look for Warning/Errors in the "Application" log.
• Choose an Warning/Error and look for stack trace in the "General tab"
   

5>     "HTTP 404 when call http://localhost/pronestor"

IIS 7/7.5 (Windows 2008 Server)

• " Open Internet Information Service Manager
• Find the application pool (pronestor)
• Right click and choose advance
• Ensure that "Load user profile" is set to "true

IIS 6 (Windows 2003 Server)

• Open Internet Information Service Manager
• Make sure ASPNET 4.0 is allows as a Web Service Extension 

6>     "HTTP 404 when calling http://localhost/pronestor/Booking.NET/Home.mvc"

• IIS 7/7.5 (Windows 2008 Server)
• Ensure that the Role "HTTP Redirection" is enable
   

1. "Can't install Pronestor Display due to missing ASP.NET Role"

• IIS 6 - the role is installed but the Pronestor Display still argues that ASP.NET isn't
• Check that ASP.NET role enabled (see article here from Microsoft)
• Run the installation from a command prompt using:
• "msiexec /i proNestor.Display.Setup.msi /l*v logfile.txt BYPASS_PREREQUISITES=1"
   

1. "PronestorWebAdmin.Models.PnbDataContext...ctor()"

• With notepad open the connectionstrings.config located in Configuration folder
• Ensure that the name of the connection string is equal to:
• <add name="dbConnectionString" connectionstring="......
   

1.  "Unable to generate a temporary class (Result=1)"

• It is due to a lack of permissions on the temporary folder which is used by the IIS.
  The easist way to fix it to do as follows:
• Right click the folder c:\windows\temp
• Choose permission
• Ensure that the "NTAUTHORITY\NETWORK SERVICE" has the following minimum permissions on the folder - ("List folder"/"Read Data"/"Write"/"Delete")
• Open the IIS
• Locate the Pronestor application pool and recycle the application pool
   

1.  "HTTP Error 400. The size of the request headers is too long"

• When a user is a member of a large number of active directory groups the Kerberos authentication token for the user increases in size.  If the HTTP header or packet size increases past the limits configured in IIS, IIS may reject the request and send this error as the response.
• There are two ways to solve this issue
• Decrease the number of Active Directory groups that the user is a member of.
• Try increasing the MaxRequestBytes and MaxFieldLength values as per note (you will need to restart http service (or reboot the machine) for it to take effect.)