使用IIS7.5的64位窗口上运行X86 ASP.NET应用程序的问题

StackOverflow https://stackoverflow.com/questions/1679610

题

目前，我正在准备一台新服务器来运行我们的ASP.NET平台。我第一次在64位Windows（2008 R2）和IIS7.5（在此之前始终7.0之前）进行安装。我们的网站构建在X86中，因此我启用了应用程序池使用32位应用程序。

我遇到以下错误，当我浏览网站时遇到的错误：

Server Error in '/' Application.



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)

Source Error:

An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.


Stack Trace:



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

   System.Reflection.Assembly._nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, Assembly locationHint, StackCrawlMark& stackMark, Boolean throwOnFileNotFound, Boolean forIntrospection) +0

   System.Reflection.Assembly.nLoad(AssemblyName fileName, String codeBase, Evidence assemblySecurity, Assembly locationHint, StackCrawlMark& stackMark, Boolean throwOnFileNotFound, Boolean forIntrospection) +43

   System.Reflection.Assembly.InternalLoad(AssemblyName assemblyRef, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection) +127

   System.Reflection.Assembly.InternalLoad(String assemblyString, Evidence assemblySecurity, StackCrawlMark& stackMark, Boolean forIntrospection) +142

   System.Reflection.Assembly.Load(String assemblyString) +28

   System.Web.Configuration.CompilationSection.LoadAssemblyHelper(String assemblyName, Boolean starDirective) +46



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

   System.Web.Configuration.CompilationSection.LoadAssemblyHelper(String assemblyName, Boolean starDirective) +613

   System.Web.Configuration.CompilationSection.LoadAllAssembliesFromAppDomainBinDirectory() +203

   System.Web.Configuration.CompilationSection.LoadAssembly(AssemblyInfo ai) +105

   System.Web.Compilation.BuildManager.GetReferencedAssemblies(CompilationSection compConfig) +178

   System.Web.Compilation.BuildProvidersCompiler..ctor(VirtualPath configPath, Boolean supportLocalization, String outputAssemblyName) +54

   System.Web.Compilation.CodeDirectoryCompiler.GetCodeDirectoryAssembly(VirtualPath virtualDir, CodeDirectoryType dirType, String assemblyName, StringSet excludedSubdirectories, Boolean isDirectoryAllowed) +600

   System.Web.Compilation.BuildManager.CompileCodeDirectory(VirtualPath virtualDir, CodeDirectoryType dirType, String assemblyName, StringSet excludedSubdirectories) +125

   System.Web.Compilation.BuildManager.EnsureFirstTimeDirectoryInit(VirtualPath virtualDir) +8803959

   System.Web.Compilation.BuildManager.GetBuildResultFromCacheInternal(String cacheKey, Boolean keyFromVPP, VirtualPath virtualPath, Int64 hashCode) +219

   System.Web.Compilation.BuildManager.GetVPathBuildResultFromCacheInternal(VirtualPath virtualPath) +43

   System.Web.Compilation.BuildManager.GetVPathBuildResultInternal(VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) +59

   System.Web.Compilation.BuildManager.GetVPathBuildResultWithNoAssert(HttpContext context, VirtualPath virtualPath, Boolean noBuild, Boolean allowCrossApp, Boolean allowBuildInPrecompile) +101

   System.Web.Compilation.BuildManager.GetVirtualPathObjectFactory(VirtualPath virtualPath, HttpContext context, Boolean allowCrossApp, Boolean noAssert) +126

   System.Web.Compilation.BuildManager.CreateInstanceFromVirtualPath(VirtualPath virtualPath, Type requiredBaseType, HttpContext context, Boolean allowCrossApp, Boolean noAssert) +62

   System.Web.UI.PageHandlerFactory.GetHandlerHelper(HttpContext context, String requestType, VirtualPath virtualPath, String physicalPath) +33

   System.Web.UI.PageHandlerFactory.GetHandler(HttpContext context, String requestType, String virtualPath, String path) +37

   System.Web.MaterializeHandlerExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute() +307

   System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously) +155

我已经使用FusLogVW来跟踪任何.NET绑定错误：出现了4个组件，但是第一次浏览站点时，我在常规服务器上获得了相同的4个组件。这些组件是cppcodeprovider，vjsharpcodeprovider和我们的两个.Resources文件。我已经调查了这些，我认为它们不是造成这个问题的原因，当然，在发现工作环境中的fuslogvw中没有相同的组件之后。

接下来，我使用依赖性沃克（Walker）研究网站的主要DLL。似乎没有任何东西缺少，但是我收到以下消息：

* Error: Modules with different CPU types were found.

我认为这也不是一个问题，因为我的.NET组件是X86，所有其他依赖性都是X64。

因此，我真的很想知道缺少的“模块” ASP.NET抱怨。

有帮助吗？

解决方案

这解决了我的问题：我必须将msvcr71.dll放入c： windows system32和c： windows syswow64中。

其他提示

我通过设置解决了问题 启用32位程序 至 真的 在应用程序池的高级设置选项卡下。

启用32位程序http://zizhujy.com/blog/image.axd?picture= enable32bit.png

此博客文章中的详细信息

最近在R2上将4.0 Beta 1应用程序放置时，我遇到了类似的问题，结果相似。我花了很长时间才发现问题是该项目中引用的核心.NET组件之一（来自GAC）已被标记为脊柱属的真实。我不知道是怎么回事 - 我当然没有故意这样做，没有其他人对此做出了努力。一旦我设置了回去（并且，我认为我必须删除本地副本）一切都很好。

我在这里找到了我在cppcodeprovider的问题上的答案：http://www.experts-exchange.com/programming/languages/.net/.net_framework_2.0/q_24367712.html（需要登录）

关闭“定义跟踪常数”，否则请在计算机上安装.NET SDK。

许可以下： CC-BY-SA 和 归因
不隶属于 StackOverflow
scroll top