Event ID 1298 — Connection Request Management

Published: January 8, 2010

Applies To: Windows Server 2008 R2

red

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

Event Details

Product: Windows Operating System
ID: 1298
Source: Microsoft-Windows-TerminalServices-SessionBroker
Version: 6.1
Symbolic Name: EVENT_ERR_FILTER_CREATEENV
Message: VM Manager webservice failed to create the environment for the VM. Error code: %1 , Description: %2

Resolve

Fix virtual machine issues with Virtual Machine Manager

To resolve this issue, do the following:

  • Start the Virtual Machine Manager Remote Desktop Server service.
  • Allow TCP port 8101 through the Windows Firewall.
  • Ensure that the virtual machine appears in Virtual Machine Manager.
  • Ensure that the virtual machine is in an acceptable state.
  • Ensure that the virtual machine can be started.
  • Add the RD Connection Broker computer account to the Administrator User Role.
  • Ensure that the RD Connection Broker computer account is a delegated administrator to the host group.

To perform these procedures, you must be a member of the Administrators group, or you must have been delegated the appropriate authority.

Start the Virtual Machine Manager Remote Desktop Server service

The Virtual Machine Manager Remote Desktop Server service must be started for Virtual Machine Manager to interact with the RD Connection Broker.

To start the Virtual Machine Manager Remote Desktop Server service:

  1. On the Virtual Machine Manager server, open the Services console. To open the Services console, click Start, point to Administrative Tools, and then click Services.
  2. If the Status column for the Virtual Machine Manager Remote Desktop Server service does not say Started, right-click Virtual Machine Manager Remote Desktop Server, point to All Tasks, and then click Start.
  3. If the issue is still not resolved, use the procedure in the section named "Allow TCP 8101 through the Windows Firewall."

Allow TCP port 8101 through the Windows Firewall

Virtual Machine Manager uses TCP port 8101 to communicate with the RD Connection Broker.

To allow TCP 8101 through the Windows Firewall:

  1. On the Virtual Machine Manager server, open Windows Firewall. To open Windows Firewall, click Start, and then click Control Panel.
  2. Click System and Security, and then click Windows Firewall.
  3. Click Allow a program or feature through Windows Firewall.
  4. Ensure that VMM RDV Server is listed. If VMM RDV Server is not listed, run the following command at an elevated command prompt: netsh advfirewall firewall add rule name ="VMM RDV Server" dir=in action=allow protocol=TCP localport=8101 profile=any and then press ENTER.
  5. If the issue is still not resolved, use the procedure in the section named "Ensure that the virtual machine appears in Virtual Machine Manager."

Ensure that the virtual machine appears in Virtual Machine Manager

The virtual machine must appear in Virtual Machine Manager before it can be used with the RD Connection Broker server.

To ensure that the virtual machine appears in Virtual Machine Manager:

  1. On the Virtual Machine Manager server, open the Virtual Machine Manager Administrator Console. To open the Virtual Machine Manager Administrator Console, click Start, point to All Programs, point to Microsoft System Center, point to Virtual Machine Manager 2008 R2, and then click Virtual Machine Manager Administrator Console.
  2. Click Virtual Machines.
  3. Ensure that the virtual machine appears in the list.
  4. If this issue is still not resolved, use the procedure in the section named "Ensure that the vitual machine is in an acceptable state."

Ensure that the virtual machine is in an acceptable state

Each virtual machine must be in an acceptable state so that the RD Connection Broker can communicate with it. The acceptable states are Running, Saved, Stopped, or Stored.

To ensure that the virtual machine is in an acceptable state:

  1. On the Virtual Machine Manager server, open the Virtual Machine Manager Administrator Console. To open the Virtual Machine Manager Administrator Console, click Start, point to All Programs, point to Microsoft System Center, point to Virtual Machine Manager 2008 R2, and then click Virtual Machine Manager Administrator Console.
  2. Click Virtual Machines.
  3. Locate the appropriate virtual machine.
  4. Ensure that Running, Saved, Stopped, or Stored is displayed in the Status column.
  5. If this issue is still not resolved, use the procedure in the section named "Ensure that the virtual machine can be started."

Ensure that the virtual machine can be started

In a non-clustered Remote Desktop Services environment, the virtual machine must be able to start.

To ensure that the virtual machine can be started:

  1. On the Virtual Machine Manager server, open the Virtual Machine Manager Administrator Console. To open the Virtual Machine Manager Administrator Console, click Start, point to All Programs, point to Microsoft System Center, point to Virtual Machine Manager 2008 R2, and then click Virtual Machine Manager Administrator Console.
  2. Click Virtual Machines.
  3. Right-click the appropriate virtual machine, and then click Start.
  4. If this issue is still not resolved, use the procedure in the section named "Add the RD Connection Broker computer account to the Administrator User Role."

Add the RD Connection Broker computer account to the Administrator User Role

The RD Connection Broker computer account is added to the Administrator User role by using the Virtual Machine Manager Administrator console.

To add the RD Connection Broker computer account to the Administrator User Role:

  1. On the Virtual Machine Manager server, open the Virtual Machine Manager Administrator Console. To open the Virtual Machine Manager Administrator Console, click Start, point to All Programs, point to Microsoft System Center, point to Virtual Machine Manager 2008 R2, and then click Virtual Machine Manager Administrator Console.
  2. Click Administration, and then click User Roles.
  3. Right-click the Administrator User Role, and then click Properties.
  4. Click the Members tab, and then click Add.
  5. In the Select Users, Computers, or Groups dialog box, in the Enter the object names to select box, type the name of the RD Connection Broker server, and then click OK.
  6. Click OK to close the User Role Properties for Administrator dialog box.
  7. If this issue is still not resolved, use the procedure in the section named "Ensure that the RD Connection Broker computer account is a delegated administrator to the host group."

Ensure that the RD Connection Broker computer account is a delegated administrator to the host group

The RD Connection Broker computer account must be a delegated administrator to the host group. This is done by using Virtual Machine Manager Administrator Console.

To ensure that the RD Connection Broker computer account is a delegated administrator to the host group:

  1. On the Virtual Machine Manager server, open the Virtual Machine Manager Administrator Console. To open the Virtual Machine Manager Administrator Console, click Start, point to All Programs, point to Microsoft System Center, point to Virtual Machine Manager 2008 R2, and then click Virtual Machine Manager Administrator Console.
  2. Click Administration, and then click Users Roles.
  3. Ensure that the proper user role exists. If the user role does not exist, use the procedure named "Create a new user role" in this section.

You can create a new user role by using the Virtual Machine Manager Administrator Console.

To create a new user role:

  1. On the Virtual Machine Manager server, open the Virtual Machine Manager Administrator Console. To open the Virtual Machine Manager Administrator Console, click Start, point to All Programs, point to Microsoft System Center, point to Virtual Machine Manager 2008 R2, and then click Virtual Machine Manager Administrator Console.
  2. Click Administration, and then click User Roles.
  3. Click New user role.
  4. In the User role name box, type a name for the user role.
  5. In the User role profile box, click Delegated Administrator.
  6. Click Next.
  7. Under User role members, click Add to add a new user account.
  8. In the Select Users, Computers, and Groups dialog box, in the Enter the object names to select box, type the user account, and then click OK.
  9. Click Next.
  10. Click the check box next to the appropriate host group, and then click Next.
  11. Click Create.

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.

Related Management Information

Connection Request Management

Remote Desktop Services

Community Additions

ADD
Show: