如何防止再次发生需要手动重新启动应用程序池的IIS错误?

时间:2018-11-14 20:44:00

标签: iis

我在IIS中托管的网站无法访问。在服务器上的事件日志中,我看到此错误:

Event code: 3005 
Event message: An unhandled exception has occurred. 
Event time: 01/01/2018 00:00:00 AM 
Event time (UTC): 01/02/2018 6:00:00 AM 
Event ID: 64b4d6533abd4e71b3ba30b9008d7d86 
Event sequence: 1921230 
Event occurrence: 1 
Event detail code: 0 

Application information: 
    Application domain: /LM/W3SVC/2/ROOT-1-131865989552967444 
    Trust level: Full 
    Application Virtual Path: / 
    Application Path: C:\inetpub\wwwroot\MyWebsite\ 
    Machine name: MyWebServer

Process information: 
    Process ID: 3388 
    Process name: w3wp.exe 
    Account name: NT AUTHORITY\SYSTEM 

Exception information: 
    Exception type: HttpException 
    Exception message: The remote host closed the connection. The error code is 0x80070057.
   at System.Web.Hosting.IIS7WorkerRequest.RaiseCommunicationError(Int32 result, Boolean throwOnDisconnect)
   at System.Web.Hosting.IIS7WorkerRequest.ExplicitFlush()
   at System.Web.WebSocketPipeline.DoFlush()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Web.WebSocketPipeline.<ProcessRequestImplAsync>d__9.MoveNext()



Request information: 
    Request URL:  
    Request path:  
    User host address:  
    User:  
    Is authenticated: False 
    Authentication Type:  
    Thread account name: NT AUTHORITY\SYSTEM 

Thread information: 
    Thread ID: 112 
    Thread account name: NT AUTHORITY\SYSTEM 
    Is impersonating: False 
    Stack trace:    at System.Web.Hosting.IIS7WorkerRequest.RaiseCommunicationError(Int32 result, Boolean throwOnDisconnect)
   at System.Web.Hosting.IIS7WorkerRequest.ExplicitFlush()
   at System.Web.WebSocketPipeline.DoFlush()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.ExceptionServices.ExceptionDispatchInfo.Throw()
   at System.Web.WebSocketPipeline.<ProcessRequestImplAsync>d__9.MoveNext()


Custom event details: 

仅重新启动网站会导致再次记录该错误,但使用不同的代码(0x800704CD而不是0x80070057)。该网站仍然无法访问。重新启动应用程序池解决了该问题。

这是什么错误,我该如何阻止它再次发生?

对两个错误代码进行搜索都会产生间歇性遇到错误的人(post1post2)的结果。区别在于他们的网站似乎并未因该错误而被关闭,并且他们间歇性地看到该错误。我看了两次,不得不手动干预才使网站重新运行。

0 个答案:

没有答案