Test Connection. Invalid Application Path – IIS

When you test a connection from an IIS application (website), you get this error: Test Connection Invalid application path To fix the Invalid application path error, try the following: Change the Connect As to an administrator account Ignore the error Delete the bindings for the application, recreate them and try again Check that the credentials are set […]
Continue reading…

 

The Current Identity Does Not Have Write Access To Temporary ASP.NET Files

An IIS website may give the following error when trying to browse an ASP.NET website: Server Error in ‘/website’ Application The current identity (username) does not have write access to ‘C:\Windows\Microsoft.NET\Framework64\v4.0…\Temporary ASP.NET Files’. This is because the user listed in the error doesn’t have write permission to the specified direectory. You can fix this by […]
Continue reading…

 

IIS Website Only Works Locally On The Localhost Of The Server

Here’s a common IIS problem: You create a website, which works locally on the server, but not remotely from another computer. If an IIS website only works on the localhost, it’s likely that port 80 (or whichever port you are using to host the website on the local server) is blocked by the Windows Firewall. […]
Continue reading…

 

Could Not Find Part Of The Path – IIS 7

In IIS 7 Web Server, when selecting an application in a virtual directory under a website, clicking on Content View can give this error: Internet Information Services (IIS Manager) Could not find a part of the path ‘C:\inetpub\wwwroot\virtualdirectory’. This is because the account used to run it doesn’t have permission to the directory or the […]
Continue reading…

 

One Or More Intermediate Certificates In The Certificate Chain Are Missing – IIS

When trying to add a site binding to a website in IIS, you may get the following error when specifying to bind the connection with an SSL certificate over HTTPS: Add Site Binding One or more intermediate certificates in the certificate chain are missing. To resolve this issue, make sure that all of the intermediate […]
Continue reading…

 

404.2: The page you are requesting cannot be served because of the ISAPI and CGI Restriction list settings on the Web server

By default, IIS doesn’t allow ISAPI and CGI through .NET. You get the above 404.2 error message because these are set to disallow in IIS. To fix this, in IIS, under the web server, click on ISAPI and CGI Restrictions. From here you can then allow the .NET version you are using in your webpage.
Continue reading…