Event ID 9 — Remote Procedure Call (RPC) Service Endpoint Functionality

  • Article

Applies To: Windows Server 2008

Administrators can configure the Remote Procedure Call (RPC) service (RpcSs) to listen on a subset of the computer's network interfaces using RPC Firewall Filters. The administrator can use RPC Firewall Filters to block some interfaces from being accessed over a given network interface and while allowing other interfaces to be accessed over the same network interface. RPC Firewall Filters make it possible for an administrator to configure network interface access on a per-interface level of detail.

RPC Firewall Filters comprise a set of rules and conditions that the administrator specifies. The Ep_add Layer filter supports port addition to processes that host a given interface. By creating an Ep_add Layer filter, an administrator can force an interface to receive calls over the port that the administrator specifies when the administrator creates the filter. If the port that is specified in the RPC Firewall Filter is already in use, the system registers a port conflict error.

Event Details

Product: Windows Operating System
ID: 9
Source: Microsoft-Windows-RPC-Events
Version: 6.0
Symbolic Name: RPC_EVENTLOG_NDR_MCCP_FAILURE
Message: Application (%1) (PID: %2) has failed to complete a COM/RPC call because of an invalid message from the server. User Action: Try the operation again. If the problem persists, contact your system administrator.

Resolve

Report the error to the application developer

An error condition may have resulted from a problem in the application's code. The data item used to return data to the client is not large enough to hold the return data. Report the entire event message and related text to the application developer so that the developer can debug and fix the application.

Verify

You can verify that the Remote Procedure Call (RPC) service (RpcSs) is running by opening the Services administrative tool and ensuring that the status of the service is Started.

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

To open the Services administrative tool and verify that the Remote Procedure Call (RPC) service is running:

  1. Click Start, and then click Run.
  2. Type services.msc, and then click OK. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
  3. To locate the Remote Procedure Call (RPC) service in the list of services, scroll down to Remote Procedure Call (RPC).
  4. Verify that the status of the service is Started.

Using RPC Firewall Filters, an administrator can control the network interfaces that the RpcSs is allowed to listen on. The administrator can use RPC Firewall Filters to block some interfaces from being accessed over a given network interface while allowing other interfaces to be accessed over the same network interface. RPC Firewall Filters make it possible for the administrator to configure network interface access on a per-interface level of detail.

You can verify that the RPC filters running on the system are the filters that you expect.

To verify the RPC filters:

  1. Click Start, point to All Programs, click Accessories, right-click Command Prompt, and then click Run as administrator. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
  2. Type netsh rpc filter show filter, and then press ENTER.
  3. Confirm that any RPC filters in the list are the filters that you expect.

Remote Procedure Call (RPC) Service Endpoint Functionality

Application Server