IIS 8.0 Detailed 500.0 Internal Server Error - IsapiModule Not Found

1
votes

I am working on a project that was originally built on a previous version on Visual Studio (pre-2013) and I am running into an error. I have searched and searched on google and stackoverflow including these resources:

The second and third links are even from Microsoft's error article!

Anyways, I have checked out a repository and opened the project in my Visual Studio 2013 that runs IIS 8.0 express. When I try and navigate to a page that is hosted on the production instance, it loads just fine. When I load it from the local instance, I get a HTTP Error 500.0 - Internal Server Error.

Here is the request summary of the error: enter image description here

And here is the error page itself: enter image description here

As you can see, it throws a 500.0 - Internal Server Error claiming that The specified module could not be found. The module it is referring to is the IsapiModule. I have read that I need to ensure the location of the Isapi.dll, but I do not know how to go about this. I have ensured that the pages I've requested are in the correct project directory. This internal server error happens when I try and navigate to most of the site's links, both locally and on the production server.

I am running with .NET 4.0 framework.

Please let me know if additional information is required. I have tried to be as transparent as possible.

Thanks.

1
asp.netvisual-studio-2013.net-4.0iis-express
Click Request Details in the first screen shot, and then check what is the module. – Lex Li
This provides the exact same information as the first screen shot – Tanner Hallman
Request Details shows much more things than the first screen shot, as it reveals all activities on the IIS processing pipeline for this request. However, you are supposed to analyze all such on your own, or with Microsoft support team via a support case at support.microsoft.com. Such tracing log can contain confidential information about your firm or home, and should not be published publicly in most cases. – Lex Li
Okay, I am fairly new to ASP so this should be interesting. Thanks for your help. – Tanner Hallman

1 Answers

0
votes

The resolution to my errors were as follows:

  • My project directory was listed on a network drive instead of the local C drive.

  • The .asp handler was mapped to a 32-bit .dll (C:\Windows\Sys32\inetsrv\asp.dll) instead of the 64-bit .dll (C:\Windows\SysWOW64\inetsrv\asp.dll)

After moving the project and adjusting where the handler pointed, I am now able to continue threading through all the other bugs of my source code. :)

Sometimes its the simple things.