How do I prevent this IIS error that required a manual restart of the app pool from occurring again?
0
My website hosted in IIS became inaccessible. In the event log on the server, I saw this error:
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:inetpubwwwrootMyWebsite
Machine name: MyWebServer
Process information:
Process ID: 3388
Process name: w3wp.exe
Account name: NT AUTHORITYSYSTEM
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 AUTHORITYSYSTEM
Thread information:
Thread ID: 112
Thread account name: NT AUTHORITYSYSTEM
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:
Restarting only the website caused the error to be logged again, but with a different code (0x800704CD instead of 0x80070057). The website was still inaccessible. Restarting the app pool resolved the issue.
What is this error, and how can I stop it from happening again?
Googling both error codes yields results from people who were encountering the error intermittently (post1, post2). The difference is that their websites don't appear to be brought down by this error, and they are seeing the error intermittently. I saw it twice, and had to manually intervene just to get the website running again.
iis
asked Nov 14 '18 at 20:44
RainboltRainbolt
2,6911235
|
show 5 more comments
0
My website hosted in IIS became inaccessible. In the event log on the server, I saw this error:
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:inetpubwwwrootMyWebsite
Machine name: MyWebServer
Process information:
Process ID: 3388
Process name: w3wp.exe
Account name: NT AUTHORITYSYSTEM
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 AUTHORITYSYSTEM
Thread information:
Thread ID: 112
Thread account name: NT AUTHORITYSYSTEM
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:
Restarting only the website caused the error to be logged again, but with a different code (0x800704CD instead of 0x80070057). The website was still inaccessible. Restarting the app pool resolved the issue.
What is this error, and how can I stop it from happening again?
Googling both error codes yields results from people who were encountering the error intermittently (post1, post2). The difference is that their websites don't appear to be brought down by this error, and they are seeing the error intermittently. I saw it twice, and had to manually intervene just to get the website running again.
iis
asked Nov 14 '18 at 20:44
RainboltRainbolt
2,6911235
There are some tools to monitor the IIS. Process Monitor tool is very helpful. It collects the IIS logs and narrow down which specific dll is causing the issue. We need to know, which specific class (or) project is throwing this exception error.
– goofyui
Nov 14 '18 at 20:47
@goofyui There's a stack trace in the error. Does that help?
– Rainbolt
Nov 14 '18 at 20:52
Whatever you shared is from Event Viewer Log (or) from IIS Log stored in the IIS log folder path ? Please also download the Process Monitor Tool provided by Microsoft. Our objective is to find which class (or) project layer is throwing this exception
– goofyui
Nov 14 '18 at 20:56
The call stack shows "WebSocket". Do you use your own WebSocket code or SignalR?
– Lex Li
Nov 14 '18 at 20:57
1
The issue has been well discussed github.com/SignalR/SignalR/issues/1790 and workaround (handling the exceptions) is mentioned. The posts you linked above are completely irrelevant, and no doubt they don't help. Use Google smartly and serve it with SignalR keyword, and that's the right way to find the relevant information.
– Lex Li
Nov 14 '18 at 22:32
|
show 5 more comments
0
0
0
My website hosted in IIS became inaccessible. In the event log on the server, I saw this error:
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:inetpubwwwrootMyWebsite
Machine name: MyWebServer
Process information:
Process ID: 3388
Process name: w3wp.exe
Account name: NT AUTHORITYSYSTEM
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 AUTHORITYSYSTEM
Thread information:
Thread ID: 112
Thread account name: NT AUTHORITYSYSTEM
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:
Restarting only the website caused the error to be logged again, but with a different code (0x800704CD instead of 0x80070057). The website was still inaccessible. Restarting the app pool resolved the issue.
What is this error, and how can I stop it from happening again?
Googling both error codes yields results from people who were encountering the error intermittently (post1, post2). The difference is that their websites don't appear to be brought down by this error, and they are seeing the error intermittently. I saw it twice, and had to manually intervene just to get the website running again.
iis
asked Nov 14 '18 at 20:44
RainboltRainbolt
2,6911235
My website hosted in IIS became inaccessible. In the event log on the server, I saw this error:
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:inetpubwwwrootMyWebsite
Machine name: MyWebServer
Process information:
Process ID: 3388
Process name: w3wp.exe
Account name: NT AUTHORITYSYSTEM
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 AUTHORITYSYSTEM
Thread information:
Thread ID: 112
Thread account name: NT AUTHORITYSYSTEM
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:
Restarting only the website caused the error to be logged again, but with a different code (0x800704CD instead of 0x80070057). The website was still inaccessible. Restarting the app pool resolved the issue.
What is this error, and how can I stop it from happening again?
Googling both error codes yields results from people who were encountering the error intermittently (post1, post2). The difference is that their websites don't appear to be brought down by this error, and they are seeing the error intermittently. I saw it twice, and had to manually intervene just to get the website running again.
iis
iis
asked Nov 14 '18 at 20:44
RainboltRainbolt
2,6911235
asked Nov 14 '18 at 20:44
RainboltRainbolt
2,6911235
asked Nov 14 '18 at 20:44
RainboltRainbolt
2,6911235
asked Nov 14 '18 at 20:44
RainboltRainbolt
2,6911235
asked Nov 14 '18 at 20:44
RainboltRainbolt
2,6911235
2,6911235
There are some tools to monitor the IIS. Process Monitor tool is very helpful. It collects the IIS logs and narrow down which specific dll is causing the issue. We need to know, which specific class (or) project is throwing this exception error.
– goofyui
Nov 14 '18 at 20:47
@goofyui There's a stack trace in the error. Does that help?
– Rainbolt
Nov 14 '18 at 20:52
Whatever you shared is from Event Viewer Log (or) from IIS Log stored in the IIS log folder path ? Please also download the Process Monitor Tool provided by Microsoft. Our objective is to find which class (or) project layer is throwing this exception
– goofyui
Nov 14 '18 at 20:56
The call stack shows "WebSocket". Do you use your own WebSocket code or SignalR?
– Lex Li
Nov 14 '18 at 20:57
1
The issue has been well discussed github.com/SignalR/SignalR/issues/1790 and workaround (handling the exceptions) is mentioned. The posts you linked above are completely irrelevant, and no doubt they don't help. Use Google smartly and serve it with SignalR keyword, and that's the right way to find the relevant information.
– Lex Li
Nov 14 '18 at 22:32
|
show 5 more comments
There are some tools to monitor the IIS. Process Monitor tool is very helpful. It collects the IIS logs and narrow down which specific dll is causing the issue. We need to know, which specific class (or) project is throwing this exception error.
– goofyui
Nov 14 '18 at 20:47
@goofyui There's a stack trace in the error. Does that help?
– Rainbolt
Nov 14 '18 at 20:52
Whatever you shared is from Event Viewer Log (or) from IIS Log stored in the IIS log folder path ? Please also download the Process Monitor Tool provided by Microsoft. Our objective is to find which class (or) project layer is throwing this exception
– goofyui
Nov 14 '18 at 20:56
The call stack shows "WebSocket". Do you use your own WebSocket code or SignalR?
– Lex Li
Nov 14 '18 at 20:57
1
The issue has been well discussed github.com/SignalR/SignalR/issues/1790 and workaround (handling the exceptions) is mentioned. The posts you linked above are completely irrelevant, and no doubt they don't help. Use Google smartly and serve it with SignalR keyword, and that's the right way to find the relevant information.
– Lex Li
Nov 14 '18 at 22:32
There are some tools to monitor the IIS. Process Monitor tool is very helpful. It collects the IIS logs and narrow down which specific dll is causing the issue. We need to know, which specific class (or) project is throwing this exception error.
– goofyui
Nov 14 '18 at 20:47
There are some tools to monitor the IIS. Process Monitor tool is very helpful. It collects the IIS logs and narrow down which specific dll is causing the issue. We need to know, which specific class (or) project is throwing this exception error.
– goofyui
Nov 14 '18 at 20:47
@goofyui There's a stack trace in the error. Does that help?
– Rainbolt
Nov 14 '18 at 20:52
@goofyui There's a stack trace in the error. Does that help?
– Rainbolt
Nov 14 '18 at 20:52
Whatever you shared is from Event Viewer Log (or) from IIS Log stored in the IIS log folder path ? Please also download the Process Monitor Tool provided by Microsoft. Our objective is to find which class (or) project layer is throwing this exception
– goofyui
Nov 14 '18 at 20:56
Whatever you shared is from Event Viewer Log (or) from IIS Log stored in the IIS log folder path ? Please also download the Process Monitor Tool provided by Microsoft. Our objective is to find which class (or) project layer is throwing this exception
– goofyui
Nov 14 '18 at 20:56
The call stack shows "WebSocket". Do you use your own WebSocket code or SignalR?
– Lex Li
Nov 14 '18 at 20:57
The call stack shows "WebSocket". Do you use your own WebSocket code or SignalR?
– Lex Li
Nov 14 '18 at 20:57
1
1
The issue has been well discussed github.com/SignalR/SignalR/issues/1790 and workaround (handling the exceptions) is mentioned. The posts you linked above are completely irrelevant, and no doubt they don't help. Use Google smartly and serve it with SignalR keyword, and that's the right way to find the relevant information.
– Lex Li
Nov 14 '18 at 22:32
The issue has been well discussed github.com/SignalR/SignalR/issues/1790 and workaround (handling the exceptions) is mentioned. The posts you linked above are completely irrelevant, and no doubt they don't help. Use Google smartly and serve it with SignalR keyword, and that's the right way to find the relevant information.
– Lex Li
Nov 14 '18 at 22:32
|
show 5 more comments
0
active
oldest
votes
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53308439%2fhow-do-i-prevent-this-iis-error-that-required-a-manual-restart-of-the-app-pool-f%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
0
active
oldest
votes
0
active
oldest
votes
active
oldest
votes
active
oldest
votes
draft saved
draft discarded
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
draft saved
draft discarded
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f53308439%2fhow-do-i-prevent-this-iis-error-that-required-a-manual-restart-of-the-app-pool-f%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
There are some tools to monitor the IIS. Process Monitor tool is very helpful. It collects the IIS logs and narrow down which specific dll is causing the issue. We need to know, which specific class (or) project is throwing this exception error.
– goofyui
Nov 14 '18 at 20:47
@goofyui There's a stack trace in the error. Does that help?
– Rainbolt
Nov 14 '18 at 20:52
Whatever you shared is from Event Viewer Log (or) from IIS Log stored in the IIS log folder path ? Please also download the Process Monitor Tool provided by Microsoft. Our objective is to find which class (or) project layer is throwing this exception
– goofyui
Nov 14 '18 at 20:56
The call stack shows "WebSocket". Do you use your own WebSocket code or SignalR?
– Lex Li
Nov 14 '18 at 20:57
1
The issue has been well discussed github.com/SignalR/SignalR/issues/1790 and workaround (handling the exceptions) is mentioned. The posts you linked above are completely irrelevant, and no doubt they don't help. Use Google smartly and serve it with SignalR keyword, and that's the right way to find the relevant information.
– Lex Li
Nov 14 '18 at 22:32