简体   繁体   English

402.2.1260 IIS7 Windows Server 2008 R2 Web服务

[英]402.2.1260 IIS7 Windows Server 2008 R2 Web Service

I have a 3rd party webservice that runs by posting a soap message directly to a dll. 我有一个通过将肥皂消息直接发布到dll来运行的第三方Web服务。

It runs perfectly on my development machine, but when I try and deploy it to Windows 2008 R2 64-bit using IIS 7 it fails, indicating error 404 2 1260 in the IIS7 log. 它可以在我的开发计算机上完美运行,但是当我尝试使用IIS 7将其部署到64位Windows 2008 R2时,它会失败,并在IIS7日志中指示错误404 2 1260。

I have done all of the normal stuff, including: 我已经完成了所有正常的工作,包括:

  • Setting the ISAPI and CGI Restrictions, 设置ISAPI和CGI限制,
  • Adding the Handler Mappings and setting them to Execute, 添加处理程序映射并将其设置为Execute,
  • Setting Handler Mappings Feature Permissions to Execute 设置要执行的处理程序映射功能权限

but none of that helps. 但这无济于事。

When I enable Failed Request Logging, the lowest-level detail that I can get is: 启用失败请求日志记录后,我可以获得的最低级别的详细信息是:

  • Error Code 0x800704ec 错误代码0x800704ec
  • Error Code 2147943660 错误代码2147943660
  • Error message IsapiModule This program is blocked by group policy 错误消息IsapiModule该程序被组策略阻止

What is going on!? 到底是怎么回事!?

The DLL was a 32-bit DLL. 该DLL是32位DLL。

By default, IIS 7 running on Windows Server 2008 R2 64bit doesn't allow 32bit dlls to run. 默认情况下,在Windows Server 2008 R2 64位上运行的IIS 7不允许运行32位dll。

There's a little setting in the Application Pool Advanced Settings called Enable 32-Bit Applications . Application Pool Advanced Settings名为“ Enable 32-Bit Applications Application Pool Advanced Settings Set it to True in the application pool to which your web service belongs, and it should start working! 在您的Web服务所属的应用程序池中将其设置为True ,它将开始工作!

声明:本站的技术帖子网页,遵循CC BY-SA 4.0协议,如果您需要转载,请注明本站网址或者原文地址。任何问题请咨询:yoyou2525@163.com.

 
粤ICP备18138465号  © 2020-2024 STACKOOM.COM