| Event Id | 16426 |
| Source | Live Communications Server |
| Description | Unable to start a process for C:\Program Files\Microsoft LC\Server\RTCSPL.EXE, error code is:0x80070102 (The wait operation timed out. ). |
| Event Information | According to Microsoft: CAUSE: The Rtcspl.exe process is a managed application that calls the WaitHandle.WaitAny method of the Microsoft .NET Framework. The WaitHandle.WaitAny method uses an infinite timeout value. However, this method incorrectly passes a timeout value of 0x7FFFFFFF to the NTDLL function NTWaitForMultipleObjects. The value 0x7FFFFFFF corresponds to about 28 days. The correct value for an infinite timeout is -1. Because the WaitHandle.WaitAny method passes a value of 0x7FFFFFFF to NTWaitForMultipleObjects, the WaitAny method incorrectly returns a value of 0 (zero). The Rtcspl.exe process interprets this returned zero value to mean that the Rtcsrv.exe process is quitting. Therefore, the Rtcspl.exe process also quits. When this behavior occurs, the Rtcsrv.exe process is still running. When the Rtcsrv.exe process detects that the Rtcspl.exe process has quit, the Rtcsrv.exe process restarts the Rtcspl.exe process. After the Rtcsrv.exe process has restarted the Rtcspl.exe process 10 times, the Rtcsrv.exe process determines that a problem exists in the Rtcspl.exe process. Therefore, the Rtcsrv.exe process quits. RESOLUTION: A supported hotfix is now available from Microsoft, but it is only intended to correct the problem. Only apply it to systems that are experiencing this specific problem.You do not have to restart the computer after you install this hotfix. |
| Reference Links | The Rtcspl.exe process unexpectedly quits approximately one time every 28 days, and event IDs 13, 16426, and 16427 are logged in Live Communications Server 2003 |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.