Event ID 896 — Connection Request Management

  • Article

Applies To: Windows Server 2008 R2

Connection requests in RD Connection Broker include user connection requests and redirection connection requests.

Event Details

Product: Windows Operating System
ID: 896
Source: Microsoft-Windows-TerminalServices-SessionBroker
Version: 6.1
Symbolic Name: EVENT_PROBLEM_DELETING_LOGS
Message: RD Connection Broker failed to delete all the log files in the "%SystemRoot%\System32\tssesdir\" directory. The error code was %1.

Resolve

Close RD Connection Broker log files or remove read-only attribute

To resolve this issue, do one or both of the following:

  • Close any RD Connection Broker log files that are open.
  • Ensure that the RD Connection Broker log files are not set to read-only.

To perform these tasks, refer to the following sections.

The RD Connection Broker log files are located in the %windir%\system32\tssesdir folder (where %windir% is the folder in which the operating system is installed, which is, by default, c:\windows).

Close any RD Connection Broker log files that are open

If you have any log files open, close the files and then start the Remote Desktop Connection Broker service. To start the Remote Desktop Connection Broker service, see the section titled "Start the Remote Desktop Connection Broker service."

Ensure that the RD Connection Broker log files are not set to read-only

If the log files are not open, or if the problem still occurs after you close the files, ensure that the log files are not set to read-only, and then start the Remote Desktop Connection Broker service.

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 read-only attribute for the log files:

  1. On the RD Connection Broker server, click Start, click Run, type %windir%\system32\tssesdir and then click OK.
  2. For each file, do the following:
    1. Right-click the file, and then click Properties.
    2. On the General tab, ensure that the Read-only check box is cleared, and then click OK.

After you check the read-only attribute of each log file, start the Remote Desktop Connection Broker service.

Start the Remote Desktop Connection Broker service

To perform this procedure, you must have membership in the local Administrators group, or you must have been delegated the appropriate authority.

To start the Remote Desktop Connection Broker service:

  1. On the RD Connection Broker server, open the Services console. To open the Services console, 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 Yes.
  3. In the Services pane, right-click Remote Desktop Connection Broker, and then click Start.
  4. Confirm that the Status column for the Remote Desktop Connection Broker service displays Started.

Verify

To verify that the RD Connection Broker server is managing connection requests successfully, examine Event Viewer logs and search for the following event message. This event message indicates that the RD Connection Broker server is managing connection requests successfully.

To perform this procedure, you do not need to have membership in the local Administrators group. Therefore, as a security best practice, consider performing this task as a user without administrative credentials.

To verify that the RD Connection Broker server is successfully managing connection requests:

  1. On the RD Connection Broker server, click Start, point to Administrative Tools, and then click Event Viewer.
  2. In the Event Viewer console tree, navigate to Application and Services Logs\Microsoft\Windows\TerminalServices-SessionBroker, and then search for the following events:
    • Event ID 801, Source TerminalServices-SessionBroker: This event indicates that the RD Connection Broker successfully managed a connection request.

Connection Request Management

Remote Desktop Services