Share via

Event ID 1281 — 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: 1281
Source: Microsoft-Windows-TerminalServices-SessionBroker
Version: 6.1
Symbolic Name: EVENT_ERR_FIND_FARM_VM
Message: RD Connection Broker failed to find any available VM in the farm %1.
User name = %2. Hr=%3

Resolve

Identify and fix connection issues

To determine how to fix this error condition, examine the error code report in the event message text.

The event message can report the following error codes:

  • E_SB_SERVICE_STOPPING (0x88130019)
  • E_SB_TSV_URL_NOT_PRESENT (0x8813001F)
  • E_SB_WRONG_TSV_URL_FORMAT (0x8813001C)
  • E_SB_UNIDENTIFIED_TARGET_TYPE (0x8813001D)
  • E_SB_UNKNOWN_RESOURCE_PLUGIN (0x88130020)
  • E_SB_FARM_NOT_FOUND (0x88130018)
  • E_SB_NULL_CP_PLUGIN (0x88130022)
  • E_SB_UNKNOWN_CP_PLUGIN (0x88130021)
  • E_SB_WRONG_USER_DATA_FROM_PUB_SERVICE (0x8813001E)
  • E_SB_NO_RESOURCE_PLUGIN (0x88130012)
  • E_SB_TARGET_IN_DIFFERENT_FARM (0x8813001A)
  • E_SB_VM_WAKE_FAILED (0x88130016)
  • E_SB_VM_BOOT_FAILED (0x88130017)
  • E_SB_NO_TARGET_IP_ADDRESS (0x88130014)
  • ERROR_NOT_FOUND (EVENT_ERR_FIND_ENVIRONMENT)

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

E_SB_SERVICE_STOPPING (0x88130019)

This error code indicates that the Remote Desktop Connection Broker service is stopping. If you requested that the Remote Desktop Connection Broker service stop, no user action is required. If the Remote Desktop Connection Broker service is stopped for an unknown reason, you must start the Remote Desktop Connection Broker service.

To start the Remote Desktop Connection Broker service:

  1. On the RD Connection Broker server, open the Services snap-in. To open the Services snap-in, click Start, point to Administrative Tools, and then click Services.
  2. Right-click Remote Desktop Connection Broker, point to All Tasks, and then click Start.

E_SB_TSV_URL_NOT_PRESENT (0x8813001F)

This error code indicates that the LoadBalanceInfo value in the RDP file is not correct.

The LoadBalanceInfo value in the RDP file contains the provider name, endpoint type, and an endpoint. The format of the LoadBalanceInfo value is in the form of LoadBalanceInfo:s:tsv://<provider>.<endpoint type>.<endpoint> where the the following is true:

  • Provider - The name of the provider. By default, this is vmresource.
  • Endpoint type - This must be either 1 or 2, where 1 indicates that this is a farm and 2 indicates that it is being used for a personal virtual desktop.
  • Endpoint - This is only valid for farms and is the name of the farm.

Some examples of properly formatted LoadBalanceInfo values are as follows:

  • LoadBalanceInfo:s:tsv://vmresource.1.VMFarm
  • LoadBalanceInfo:s:tsv://vmresource.2

E_SB_WRONG_TSV_URL_FORMAT (0x8813001C)

This error code indicates that the LoadBalanceInfo value in the RDP file is not correct.

The LoadBalanceInfo value in the RDP file contains the provider name, endpoint type, and an endpoint. The format of the LoadBalanceInfo value is in the form of LoadBalanceInfo:s:tsv://<provider>.<endpoint type>.<endpoint> where the the following is true:

Provider - The name of the provider. By default, this is vmresource.

  • Endpoint type - This must be either 1 or 2, where 1 indicates that this is a farm and 2 indicates that it is being used for a personal virtual desktop.
  • Endpoint - This is only valid for farms and is the name of the farm.

Some examples of properly formatted LoadBalanceInfo values are as follows:

  • LoadBalanceInfo:s:tsv://vmresource.1.VMFarm
  • LoadBalanceInfo:s:tsv://vmresource.2

E_SB_UNIDENTIFIED_TARGET_TYPE (0x8813001D)

This error code indicates that the endpoint type in the LoadBalanceInfo value contained in the RDP file is not correct. The endpoint type must be either 1 or 2.

The LoadBalanceInfo value in the RDP file contains the provider name, endpoint type, and an endpoint. The format of the LoadBalanceInfo value is in the form of LoadBalanceInfo:s:tsv://<provider>.<endpoint type>.<endpoint> where the the following is true:

  • Provider - The name of the provider. By default, this is vmresource.
  • Endpoint type - This must be either 1 or 2, where 1 indicates that this is a farm and 2 indicates that it is being used for a personal virtual desktop.
  • Endpoint - This is only valid for farms and is the name of the farm.

Some examples of properly formatted LoadBalanceInfo values are as follows:

  • LoadBalanceInfo:s:tsv://vmresource.1.VMFarm
  • LoadBalanceInfo:s:tsv://vmresource.2

E_SB_UNKNOWN_RESOURCE_PLUGIN (0x88130020)

This error code indicates that the resource plug-in specified in the LoadBalanceInfo value contained in the RDP file is not correct. The resource plug-in is entered as the endpoint and must correspond to a resource plug-in that is registered on the RD Connection Broker server. The plug-in is registered in the following registry path: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Tssdis\Parameters\Plugins\Resource.

The LoadBalanceInfo value in the RDP file contains the provider name, endpoint type, and an endpoint. The format of the LoadBalanceInfo value is in the form of LoadBalanceInfo:s:tsv://<provider>.<endpoint type>.<endpoint> where the the following is true:

  • Provider - The name of the provider. By default, this is vmresource.
  • Endpoint type - This must be either 1 or 2, where 1 indicates that this is a farm and 2 indicates that it is being used for a personal virtual desktop.
  • Endpoint - This is only valid for farms and is the name of the farm.

Some examples of properly formatted LoadBalanceInfo values are as follows:

  • LoadBalanceInfo:s:tsv://vmresource.1.VMFarm
  • LoadBalanceInfo:s:tsv://vmresource.2

E_SB_FARM_NOT_FOUND (0x88130018)

This error code indicates that the farm name specified in the LoadBalanceInfo value contained in the RDP file is not correct. The farm name is entered as the endpoint and must correspond to a farm name that exists within your organization.

The LoadBalanceInfo value in the RDP file contains the provider name, endpoint type, and an endpoint. The format of the LoadBalanceInfo value is in the form of LoadBalanceInfo:s:tsv://<provider>.<endpoint type>.<endpoint> where the the following is true:

  • Provider - The name of the provider. By default, this is vmresource.
  • Endpoint type - This must be either 1 or 2, where 1 indicates that this is a farm and 2 indicates that it is being used for a personal virtual desktop.
  • Endpoint - This is only valid for farms and is the name of the farm.

Some examples of properly formatted LoadBalanceInfo values are as follows:

  • LoadBalanceInfo:s:tsv://vmresource.1.VMFarm
  • LoadBalanceInfo:s:tsv://vmresource.2

E_SB_NULL_CP_PLUGIN (0x88130022)

This error code indicates that the resource plug-in specified in the LoadBalanceInfo value contained in the RDP file is not correct. The resource plug-in is entered as the endpoint and must correspond to a resource plug-in that is registered on the RD Connection Broker server. The plug-in is registered in the following registry path: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Tssdis\Parameters\Plugins\Resource.

The LoadBalanceInfo value in the RDP file contains the provider name, endpoint type, and an endpoint. The format of the LoadBalanceInfo value is in the form of LoadBalanceInfo:s:tsv://<provider>.<endpoint type>.<endpoint> where the the following is true:

  • Provider - The name of the provider. By default, this is vmresource.
  • Endpoint type - This must be either 1 or 2, where 1 indicates that this is a farm and 2 indicates that it is being used for a personal virtual desktop.
  • Endpoint - This is only valid for farms and is the name of the farm.

Some examples of properly formatted LoadBalanceInfo values are as follows:

  • LoadBalanceInfo:s:tsv://vmresource.1.VMFarm
  • LoadBalanceInfo:s:tsv://vmresource.2

E_SB_UNKNOWN_CP_PLUGIN (0x88130021)

This error code indicates that the resource or filter plug-in is not enabled. You must enable the plug-in by using Registry Editor.

To enable a resource or filter plug-in by using Registry Editor:

  1. On the RD Connection Broker server, open Registry Editor. To open Registry Editor, click Start, and then click Run.
  2. Type regedit.exe and then press ENTER.
  3. Navigate to HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Tssdis\Parameters\Plugins
  4. If you need to enable a resource plug-in:
    1. Click Resource, and then click the plug-in to be enabled.
    2. Double-click IsEnabled.
    3. In the Value data box, type 1 and then click OK.
  5. If you need to enable a filter plug-in:
    1. Click Filter, and then click the plug-in to be enabled.
    2. Double-click IsEnabled.
    3. In the Value data box, type 1 and then click OK.

E_SB_WRONG_USER_DATA_FROM_PUB_SERVICE (0x8813001E)

This error code indicates that the personal virtual desktop could not be located. You must ensure that the personal virtual desktop is assigned correctly by using Active Directory Users and Computers.

Note: This procedure assumes that your Active Directory Domain Services functional level is set to Windows Server 2008 R2. This functional level is required to see the Personal Virtual Desktop tab in Active Directory Users and Computers.

To ensure that the personal virtual desktop is assigned correctly:

  1. On the domain controller, open Active Directory Users and Computers. To open Active Directory Users and Computers, click Start, point to Administrative Tools, and then click Active Directory Users and Computers.
  2. Navigate to the user account object where the personal virtual desktop is assigned.
  3. Right-click the user account object, and then click Properties.
  4. Click the Personal Virtual Desktop tab.
  5. Ensure that the Assign a personal virtual desktop to this user check box is selected.
  6. In the Computer Name box, ensure that the computer name is pointing to the correct personal virtual desktop.
  7. If the personal virtual desktop is configured correctly, you should ensure that the virtual machine is not part of a farm.

E_SB_NO_RESOURCE_PLUGIN (0x88130012)

This error code indicates that the resource plug-in specified in the LoadBalanceInfo value contained in the RDP file is not correct. The resource plug-in is entered as the endpoint and must correspond to a resource plug-in that is registered on the RD Connection Broker server. The plug-in is registered in the following registry path: HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Tssdis\Parameters\Plugins\Resource.

The LoadBalanceInfo value in the RDP file contains the provider name, endpoint type, and an endpoint. The format of the LoadBalanceInfo value is in the form of LoadBalanceInfo:s:tsv://<provider>.<endpoint type>.<endpoint> where the the following is true:

  • Provider - The name of the provider. By default, this is vmresource.
  • Endpoint type - This must be either 1 or 2, where 1 indicates that this is a farm and 2 indicates that it is being used for a personal virtual desktop.
  • Endpoint - This is only valid for farms and is the name of the farm.

Some examples of properly formatted LoadBalanceInfo values are as follows:

  • LoadBalanceInfo:s:tsv://vmresource.1.VMFarm
  • LoadBalanceInfo:s:tsv://vmresource.2

E_SB_TARGET_IN_DIFFERENT_FARM (0x8813001A)

This error code indicates that the farm name specified in the LoadBalanceInfo value contained in the RDP file does not match the farm in which the server is joined. The farm name is entered as the endpoint and must correspond to a farm name that exists within your organization.

The LoadBalanceInfo value in the RDP file contains the provider name, endpoint type, and an endpoint. The format of the LoadBalanceInfo value is in the form of LoadBalanceInfo:s:tsv://<provider>.<endpoint type>.<endpoint> where the the following is true:

  • Provider - The name of the provider. By default, this is vmresource.
  • Endpoint type - This must be either 1 or 2, where 1 indicates that this is a farm and 2 indicates that it is being used for a personal virtual desktop.
  • Endpoint - This is only valid for farms and is the name of the farm.

Some examples of properly formatted LoadBalanceInfo values are as follows:

  • LoadBalanceInfo:s:tsv://vmresource.1.VMFarm
  • LoadBalanceInfo:s:tsv://vmresource.2

E_SB_VM_WAKE_FAILED (0x88130016)

This error code indicates that the RD Connection Broker server could not wake the virtual machine. For more information about this error code, you should examine Event Viewer logs and search for the following event messages.

To open Event Viewer:

  1. On the RD Virtualization Host 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\Microsoft-Windows-TerminalServices-TSV-VmHostAgent, and then search for the following events:
    • Event ID 4869, Source Microsoft-Windows-TerminalServices-TSV-VmHostAgent

E_SB_VM_BOOT_FAILED (0x88130017)

This error code indicates that the RD Connection Broker server could not start the virtual machine. For more information about this error code, you should examine Event Viewer logs and search for the following event messages.

To open Event Viewer:

  1. On the RD Virtualization Host 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\Microsoft-Windows-TerminalServices-TSV-VmHostAgent, and then search for the following events:
    • Event ID 12801, Source Microsoft-Windows-TerminalServices-TSV-VmHostAgent

E_SB_NO_TARGET_IP_ADDRESS (0x88130014)

This error code indicates that a non-Microsoft resource plug-in did not return a valid IP address when the virtual machine was being orchestrated. For further troubleshooting, you should contact the manufacturer of the non-Microsoft resource plug-in.

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