A request on persistent/resilient handle failed because the handle was invalid or it exceeded the timeout. Status: %7 Type: ...

A request on persistent/resilient handle failed because the handle was invalid or it exceeded the timeout.

Status: %7

Type: %1
Path: %4%6
Restart count: %2

Guidance:
After retrying a request on a Continuously Available (Persistent) handle or a Resilient handle, the client was unable to reconnect the handle. This event is the result of a handle recovery failure. Review other events for more details.

A request for a callback on a MTA thread failed. This should happen only if the system is in an extremely unstable state. ... A request for assistance with an error could not be sent because the email address of the recipient is blank. Details: Error: ... A request for assistance with an error was sent. Details: Error: %1 Email sent to: %2 Email subject: %3 User: %4\%5 File ... A request message from another BranchCache client was dropped because it was not valid. Remote client address: %1 Error: ... A request on persistent/resilient handle failed because the handle was invalid or it exceeded the timeout. Status: %7 Type: ... A request timed out because there was no response from the server. Server name: %6 Session ID:%3 Tree ID:%4 Message ID:%2 ... A request to allocate an ephemeral port number from the global TCP port space has failed due to all such ports being in use. ... A request to allocate an ephemeral port number from the global UDP port space has failed due to all such ports being in use. ... A request to send or receive data was disallowed because the socket had already been shut down in that direction with a previous ...