| Event Id | 3 |
| Source | Microsoft-Windows-RPC-Events |
| Description | Application (%1) (PID: %2) is using Windows functionality that is not present in this release of Windows. To obtain an updated version of the application, contact the application vendor. The technical information that needs to be conveyed to the application vendor is this: "An RPC method using synchronous pipes has been called on protocol sequence %3 interface with unique identifier %4. Usage and support of synchronous pipes has been deprecated for this release of Windows. |
| Event Information | According to Microsoft : Cause : This event is logged when application is using Windows functionality that is not present in this release of Windows. Resolution : Contact the application developer for an updated version of the application An error condition may have resulted from a deprecated feature of remote procedure call (RPC) that is used in the current version of the application. Look in the event message to find information about the details of the feature that caused the error. Contact the application developer for an updated version of the application. Provide the entire event message to the application developer, and let the developer know that the current version of the application uses a deprecated feature of RPC. The event message provides details about the deprecated feature. 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 this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority. To ensure that the Remote Procedure Call (RPC) service is started: 1.Click Start, and then click 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 to Remote Procedure Call (RPC). 4.Confirm that the status of the service is Started and that the service is running with no errors. |
| Reference Links | Event ID 3 from Source Microsoft-Windows-RPC-Events |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.