Diagnosing "The specified module could not be found" on IIS7 with ASP.Net


I am migrating some web apps from a windows 2003 server with IIS6 server to a Windows server 2008 R2 server with IIS7.

One of the apps, which runs on asp.net v2.0 using forms authentication will not load.

It gives me the following error...

The specified module could not be found. (Exception from HRESULT: 0x8007007E)

Description: An unhandled exception occurred during the execution of the current web request. Please review the stack trace for more information about the error and where it originated in the code.

Exception Details: System.IO.FileNotFoundException: The specified module could not be found. (Exception from HRESULT: 0x8007007E)

Now i fully understand that the app cannot load some kind of resource due to a FileNotFoundException, but i am struggling to diagnose exactly where in the application this is happening, as it does not tell me what the module is, nor what file it is looking for.

I have enabled failed request tracing and i get back a complete request trace, yet i cannot find anything that gives me detail on this specific error, or the module involved.

Here is a log (and the xsl sheet) from a failed request...

XML Log File

XSL Stylesheet for log file

Download both to your machine and open the xml file.

Any advice on diagnosing the root cause of the issue would be greatly appreciated.

asked on Server Fault Mar 31, 2012 by Baldy • edited Mar 31, 2012 by Baldy

1 Answer


I've seen this occur before where a referenced managed assembly is present on the previous machine (such as in the GAC or registered in another location), but is not present on the new machine.

If you can identify the missing managed assembly(s), one approach may be to configure them to "copy local" so that they are "bin-deployed" to the application bin folder.

You may want to try running SysInternals' Process Monitor to identify the missing assembly.

There have also been a few occurrences where native assemblies were missing from the %systemroot%\system32 folder, such as msvcr71.dll.



answered on Server Fault Mar 31, 2012 by Greg Askew • edited May 23, 2017 by Community

User contributions licensed under CC BY-SA 3.0