Share via

Event ID 1001 — Remote Procedure Call Communication

  • Article

Applies To: Windows Server 2008 R2

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: 1001
Source: Microsoft-Windows-RemoteApp and Desktop Connection Management
Version: 6.1
Symbolic Name: TSCPUBSVR_FILTER_SID_CONVERT_ERROR
Message: Unable to filter RemoteApps for the requesting user. The user's string-format SID could not be converted to a binary-format SID.

User SID: %2

Error Code: %1

Resolve

Check security identifier format in 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 by using that user account's security identifier (SID). This error can occur in a non-Microsoft application if the SID is not properly formatted. For more information about the RemoteApp and Connection Management service API reference, see https://msdn.microsoft.com/en-us/library/dd401668(VS.85).aspx.

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.

Remote Procedure Call Communication

Remote Desktop Services