Why is my IIS 7 refusing to serve up css or js when I change 'Enable 32-Bit Applications' to False

跟風遠走 提交于 2019-12-05 07:46:24

It is very likely that on your IIS setup, a 32 bit only module is installed by you accidentally which prevents the whole web application from running in 64 bit module. That's a common cause of such 500 errors.

Failed request tracing should be able to show you more information on which module it is,

http://www.iis.net/learn/troubleshoot/using-failed-request-tracing/troubleshooting-failed-requests-using-tracing-in-iis

When I had this error there was a problem in system.webServer\staticContent in web.config.

Because of a difference between servers, an for a particular MIME type was required on one machine but caused this error on another.

The failsafe would be to include a for each that you have in web.config to avoid getting a 500 if the is not required.

Double check mime types are correctly assigned, it could be because you have double entry of mimetypes for local site web.config and server itself.

Having to put comment here as I dont have enough points to comment.

Have you tried checking the handler mapping on your website.

Under Handler Mappings: Check that the StaticFile Handler is still registered and that the path is assigned to *

Also check that it is enabled.

Just had this issue myself with windows security enabled and ananamous access turned off.

The solution in my case was to add the localhost site to my local intranet sites. Running Visual Studio in adminstrator mode can also clear the problem.

易学教程内所有资源均来自网络或用户发布的内容,如有违反法律规定的内容欢迎反馈
该文章没有解决你所遇到的问题?点击提问,说说你的问题,让更多的人一起探讨吧!