Thanks to Michael Brian Lee in Autodesk QA for the following Revit Server information!
Some users with heavily loaded Revit Servers may experience periodic network disconnects and a lack of server availability. In the most severe cases Revit Server may become completely unresponsive and require a restart of the operating system itself. This issue is related to the underlying Windows Communication Foundation technology underpinning Revit Server, and generally manifests itself with one of the following symptoms:
- A message in the Windows Event Log with the following description:
An error occurred while dispatching a duplicated socket: this handle is now leaked in the process.
- Exceptions in the Revit Server logs that resemble the following:
System.ServiceModel.CommunicationException: There was an error reading from the pipe: The pipe has been ended. (109, 0x6d).
--->System.IO.PipeException: There was an error reading from the pipe: The pipe has been ended. (109, 0x6d).
at System.ServiceModel.Channels.PipeConnection.OnAsyncReadComplete(Boolean haveResult, Int32 error, Int32 numBytes)
--- End of inner exception stack trace ---
at System.ServiceModel.Channels.SessionConnectionReader.OnAsyncReadComplete(Object state)
Microsoft has issued a fix for this issue, and it can be downloaded here:
We recommend that all users with heavily loaded Revit Servers download and install these updates.