Event Id | 1013 |
Source | Microsoft-Windows-TerminalServices-SessionBroker |
Description | The Terminal Services Session Broker service could not start because of a problem creating a security descriptor. The system may be low on resources. Error code: %1. |
Event Information | According to Microsoft : Cause : This event is logged when the Terminal Services Session Broker service could not start because of a problem creating a security descriptor. Resolution : Increase available memory To resolve this issue, increase the amount of available memory on the TS Session Broker server. One way to increase the amount of available memory is to determine if there are any programs or processes running on the TS Session Broker server that can be closed. Use Task Manager to determine which processes are using the most memory, and to end those processes. To perform this procedure, you must have membership in the local Administrators group, or you must have been delegated the appropriate authority.
Verify : To verify that the TS Session Broker server is available, ensure that the Terminal Services Session Broker service is running. To perform this procedure, you must have membership in the local Administrators group, or you must have been delegated the appropriate authority. To check the Terminal Services Session Broker service:
|
Reference Links | Event ID 1013 from Source Microsoft-Windows-TerminalServices-SessionBroker |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.