Event ID 1013 — TS Session Broker Server Availability

Updated: January 5, 2012

Applies To: Windows Server 2008

red

The Terminal Services Session Broker (TS Session Broker) server relies on the Terminal Services Session Broker service to be running in order to perform session load balancing between terminal servers in a farm, and to reconnect a user to an existing session in a load-balanced terminal server farm.

Note:  TS Session Broker was formerly called Terminal Services Session Directory.

Event Details

Product: Windows Operating System
ID: 1013
Source: Microsoft-Windows-TerminalServices-SessionBroker
Version: 6.0
Symbolic Name: EVENT_COULDNOTSECUREDIR
Message: 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.

Resolve

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.

  1. On the TS Session Broker server, right-click an empty area of the taskbar, and then click Task Manager.
  2. Click the Processes tab.
  3. Make sure that the User Name and Memory (Private Working Set) columns appear. If they do not appear, on the View menu, click Select Columns, select the User Name and the Memory (Private Working Set) check boxes, and then click OK.
  4. At the bottom of the tab, select the Show processes from all users check box.
  5. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
  6. To sort the processes by memory usage, click the Memory (Private Working Set) column header.
  7. Determine if you can end any of the memory-intensive processes.
  8. To end a process, click the process name, and then click End Process.
  9. Click End Process to confirm that you want to end the process.

If you cannot free memory by using Task Manager, or if this issue still occurs after you try to free up memory, restart the TS Session Broker server.

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:

  1. On the TS Session Broker server, open the Services snap-in. To open the Services snap-in, click Start, point to Administrative Tools, and then click Services.
  2. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
  3. In the Services pane, locate Terminal Services Session Broker.
  4. Confirm that the Status column for the Terminal Services Session Broker service displays Started.

Related Management Information

TS Session Broker Server Availability

Terminal Services

Community Additions

ADD
Show: