| Event Id | 258 |
| Source | TermService |
| Description | STATUS_TIMEOUT Data: 0000: 00 00 00 00 00 00 00 00 ........ 0008: 00 00 00 00 00 00 00 00 ........ 0010: 00 00 00 00 00 00 00 00 ........ 0018: 00 00 00 00 00 00 00 00 ........ 0020: 00 00 00 00 00 00 00 00 ........ 0028: 00 00 00 00 00 00 00 00 ........ 0030: 00 00 00 00 00 00 00 00 ........ 0038: 00 00 00 00 00 00 00 00 ........ 0040: 00 00 |
| Event Information | When a Terminal Services client logs on or logs off (either in a session or on the console of the Terminal server), the Windows 2000-based Terminal server together with the connected Terminal Services client computers may stop responding or may pause for several seconds. Users may also experience one or more of the follow symptoms:
When a user types in a document, characters do not appear on the screen until this pause has ended.
Keyboard input and mouse input are queued, but they are not processed until this pause has ended.
Live performance monitoring (Perfmon) graphs have missing data points during this pause.
All running programs appear to stop responding, or "hang," during this pause.
When Spooler is under a load from a large number of users, a high CPU usage is displayed for it. CAUSE: This problem may occur if there is a contention among server resources. The contention causes a delay in processing that appears as a pause or as unresponsiveness. RESOLUTION: Hotfix Information A supported fix is now available from Microsoft. |
| Reference Links | Terminal Server and Connected Terminal Services Clients Pause When a Terminal Services Client Logs On or Logs Off |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.