Event ID 1003 — Remote Procedure Call Communication

Published: January 8, 2010

Applies To: Windows Server 2008 R2

yellow

The RemoteApp and Desktop Connection Management service must be able to communicate by using remote procedure call (RPC) to query RD Session Host and RD Virtualization Host servers for RemoteApp program, session-based desktop, and virtual desktop information on your network.

Event Details

Product: Windows Operating System
ID: 1003
Source: Microsoft-Windows-RemoteApp and Desktop Connection Management
Version: 6.1
Symbolic Name: TSCPUBSVR_FILTER_SERVER_CONTEXT_ERROR
Message: Unable to filter RemoteApps for user %2. There was an error initializing the server context from the user's SID. Check that the Remote App and Desktop Management machine is in the domain's Windows Authorization Access Group, or is on a compatibility-mode domain.

Error Code: %1

Resolve

Ensure that the credentials are valid

To resolve this issue, ensure that the credentials are valid on the RD Web Access Web site by doing the following:

  • Ensure that you can log on to the RD Web Access server by using domain credentials.
  • Ensure that the domain credentials are formatted correctly in a non-Microsoft application.
  • Add the RD Connection Broker computer account to the Windows Authorization Access Group.

To perform these tasks, refer to the following sections.

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

Ensure that you can log on to the RD Web Access server by using domain credentials

The RD Web Access server that is configured to use the RD Connection Broker server must be available to communicate with the RD Connection Broker server.

To log on to the RD Web Access server that is configured to use the RD Connection Broker server:

  1. On the RD Web Access server, open Remote Desktop Web Access Configuration. To open Remote Desktop Web Access Configuration, click Start, point to Administrative Tools, point to Remote Desktop Services, and then click Remote Desktop Web Access Configuration.
  2. In the Domain\user name box, type a valid domain and user account name.
  3. In the Password box, type the password for the user account.
  4. Verify that you can successfully log on to the RD Web Access server by using Remote Desktop Web Access Configuration.

Ensure that the domain credentials are formatted correctly in a non-Microsoft application

The RemoteApp and Connection Management service queries RemoteApp programs, session-based desktops, and virtual desktops that are available to a specific user. This error can occur in a non-Microsoft application if the domain credentials are not properly formatted. For more information about the RemoteApp and Connection Management service API reference, see http://msdn.microsoft.com/en-us/library/dd401668(VS.85).aspx.

Add the RD Connection Broker computer account to the Windows Authorization Access Group

The Windows Authorization Access Group is a security group included in the Active Directory Domain Services domain.

To add the RD Connection Broker computer account to the Windows Authorization Access Group:

  1. On the domain controller, open Active Directory Users and Computers. To open Active Directory Users and Computer, click Start, point to Administrative Tools, and then click Active Directory Users and Computers.
  2. Click Builtin, and then double-click Windows Authorization Access Group.
  3. Click the Members tab, and then click Add.
  4. In the Enter the object names to select box, type the name of the RD Connection Broker computer account, and then click OK.
  5. Click OK to close the Windows Authorization Access Group dialog box.

Verify

To verify that RemoteApp and Desktop Connection Management can communicate with the RD Session Host servers and the RD Virtualization Host servers, do the following:

  • Verify that the RemoteApp and Desktop Connection Management service is started.
  • Log on to the RD Web Access server that is configured to use the RD Connection Broker server.

Verify that the RemoteApp and Desktop Connection Management service is started

The RemoteApp and Desktop Connection Management service is used to communicate with the RD Session Host and RD Virtualization Host servers on your network.

To verify that the RemoteApp and Desktop Connection Management service is started:

  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. Locate the service named RemoteApp and Desktop Connection Management.
  3. Verify that the Status column for this service displays Started.
  4. After you have verified that the RemoteApp and Desktop Connection Management service is started, you should log on to the RD Web Access server as outlined in the section "Log on to the RD Web Access server that is configured to use the RD Connection Broker server."

Log on to the RD Web Access server that is configured to use the RD Connection Broker server

The RD Web Access server that is configured to use the RD Connection Broker server must be available to communicate with the RD Connection Broker server.

To log on to the RD Web Access server that is configured to use the RD Connection Broker server:

  1. On the RD Web Access server, open Remote Desktop Web Access Configuration. To open Remote Desktop Web Access Configuration, click Start, point to Administrative Tools, point to Remote Desktop Services, and then click Remote Desktop Web Access Configuration.
  2. In the Domain\user name box, type a valid domain and user account name.
  3. In the Password box, type the password for the user account.
  4. Verify that you can successfully log on to the RD Web Access server by using Remote Desktop Web Access Configuration.

Related Management Information

Remote Procedure Call Communication

Remote Desktop Services

Community Additions

ADD
Show: