简体   繁体   English

Windows Server 2012上的IIS 8.5中的HTTP错误503

[英]http error 503 in IIS 8.5 on Windows Server 2012

We have 4 web applications installed on IIS 8.5 on Windows Server 2012. 3 websites and 1 webService. 我们在Windows Server 2012的IIS 8.5上安装了4个Web应用程序。3个网站和1个webService。 One website is functioning fine. 一个网站运行正常。 Hitting the urls for the other sites get "HTTP Error 503 Service Unavailable". 击中其他站点的URL将获得“ HTTP错误503服务不可用”。 The HttpErr log has ".http 1.1..Get websiteName 503 1 N//A websiteAppPoolName". HttpErr日志具有“ .http 1.1..get websiteName 503 1 N // websiteWebAppPoolName”。

I cannot find any error messages in any of the Event Logs: Application, System or Security. 我在以下任何事件日志中都找不到任何错误消息:应用程序,系统或安全性。 I also cannot find anything related to 503 dash 1 in any Microsoft documentation. 我也找不到任何Microsoft文档中与503破折号1相关的任何内容。 The same versions of these apps run fine on Windows 2008 Server. 这些应用程序的相同版本在Windows 2008 Server上运行良好。

I have read many posts about 503, and the application pool identity for all sites is valid, and unlike the typical 503 error caused by an expired credential for the app pool, when the 503 is recorded, the app pool is still started. 我已经阅读了很多有关503的帖子,并且所有站点的应用程序池标识都是有效的,并且与由应用程序池的凭据过期引起的典型503错误不同,当记录503时,应用程序池仍会启动。

Note that there is a mixture of 32-bit and 64-bit web apps. 请注意,混合使用32位和64位Web应用程序。 The functioning site is 64-bit. 正常运行的站点是64位。 The other 3 were 32-bit. 其他3位是32位。 Their app pools are set to enable 32-bit. 他们的应用程序池设置为启用32位。 Thinking this might be a part of the problem, I converted the webservice to 64-bit, changing the app pool accordingly, no difference, still get 503. 认为这可能是问题的一部分,因此我将Web服务转换为64位,相应地更改了应用程序池,没有区别,仍然得到503。

I found the solution in another Stack Overflow post about the 503 error, but I am not sure which one. 我在另一个有关503错误的Stack Overflow帖子中找到了解决方案,但是我不确定是哪个。 However, David McClendon provided the answer. 但是,大卫·麦克伦登(David McClendon)提供了答案。 Under /Advanced Settings for the website, under Enabled Protocols, there was this: http; 在网站的“ /高级设置”下的“启用的协议”下,有以下内容:http; https. https。 The colon should be a COMMA. 冒号应该是COMMA。 Once this was changed, sites were hunky dory. 一旦更改,站点就变成了笨拙的海ry。 Very frustrating that IIS logs no information about the cause of the error., 非常令人沮丧的是,IIS没有记录有关错误原因的任何信息。

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

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