Microsoft-Windows-RPC-Events

19 events across 1 channel

Event	Title	Channel	Sample
2	Application (ApplicationName) (PID: ProcessId) is using Windows functionality …	Application	N
3	Application (ApplicationName) (PID: ProcessId) is using Windows functionality …	Application	N
4	Application (ApplicationName) (PID: ProcessId) is using Windows functionality …	Application	N
5	Application (ApplicationName) (PID: ProcessId) is using Windows functionality …	Application	N
6	Application (ApplicationName) (PID: ProcessId) is using Windows functionality …	Application	N
7	Application (ApplicationName) (PID: ProcessId) is using Windows functionality …	Application	N
8	Application (ApplicationName) (PID: ProcessId) has failed to add endpoint …	Application	N
9	Application (ApplicationName) (PID: ProcessId) has failed to complete a COM/RPC …	Application	N
10	Application (ApplicationName) (PID: ProcessId) has failed to complete a COM call …	Application	N
11	Possible Memory Leak.	Application	N
2147483657	Application ({param1}) (PID: {param2}) has failed to complete a COM/RPC call …	Application	N
3221225474	Application ({param1}) (PID: {param2}) is using Windows functionality that is …	Application	N
3221225475	Application ({param1}) (PID: {param2}) is using Windows functionality that is …	Application	N
3221225476	Application ({param1}) (PID: {param2}) is using Windows functionality that is …	Application	N
3221225477	Application ({param1}) (PID: {param2}) is using Windows functionality that is …	Application	N
3221225478	Application ({param1}) (PID: {param2}) is using Windows functionality that is …	Application	N
3221225479	Application ({param1}) (PID: {param2}) is using Windows functionality that is …	Application	N
3221225480	Application ({param1}) (PID: {param2}) has failed to add endpoint …	Application	N
3221225482	Application ({param1}) (PID: {param2}) has failed to complete a COM call because …	Application	N

Event ID 2: Application (ApplicationName) (PID: ProcessId) is using Windows functionality that is not present in this release of Windows.

Provider: Microsoft-Windows-RPC-Events
Channel: Application

Description

Application (ApplicationName) (PID: ProcessId) is using Windows functionality that is not present in this release of Windows. For obtaining an updated version of the application, please, 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 on protocol sequence RPCProtocolSequence interface with unique identifier InterfaceGUID. Usage and support of synchronous pipes on this protocol sequence has been deprecated for this release of Windows. For information on the deprecation process, please, see http://go.microsoft.com/fwlink/?LinkId=36415." User Action Contact the application vendor for updated version of the application.

Message #

Application (%1) (PID: %2) is using Windows functionality that is not present in this release of Windows. For obtaining an updated version of the application, please, 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 on protocol sequence %3 interface with unique identifier %4. Usage and support of synchronous pipes on this protocol sequence has been deprecated for this release of Windows. For information on the deprecation process, please, see http://go.microsoft.com/fwlink/?LinkId=36415."  User Action Contact the application vendor for updated version of the application.

Fields #

Name	Description
`ApplicationName` UnicodeString
`ProcessId` HexInt32
`RPCProtocolSequence` UnicodeString
`InterfaceGUID` GUID

Event ID 3: Application (ApplicationName) (PID: ProcessId) is using Windows functionality that is not present in this release of Windows.

Provider: Microsoft-Windows-RPC-Events
Channel: Application

Description

Application (ApplicationName) (PID: ProcessId) is using Windows functionality that is not present in this release of Windows. For obtaining an updated version of the application, please, 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 on protocol sequence RPCProtocolSequence interface with unique identifier InterfaceGUID. Usage and support of synchronous pipes has been deprecated for this release of Windows. For information on the deprecation process, please, see http://go.microsoft.com/fwlink/?LinkId=36415." User Action Contact the application vendor for updated version of the application.

Message #

Application (%1) (PID: %2) is using Windows functionality that is not present in this release of Windows. For obtaining an updated version of the application, please, 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 on protocol sequence %3 interface with unique identifier %4. Usage and support of synchronous pipes has been deprecated for this release of Windows. For information on the deprecation process, please, see http://go.microsoft.com/fwlink/?LinkId=36415."  User Action Contact the application vendor for updated version of the application.

Fields #

Name	Description
`ApplicationName` UnicodeString
`ProcessId` HexInt32
`RPCProtocolSequence` UnicodeString
`InterfaceGUID` GUID

Event ID 4: Application (ApplicationName) (PID: ProcessId) is using Windows functionality that is not present in this release of Windows.

Provider: Microsoft-Windows-RPC-Events
Channel: Application

Description

Application (ApplicationName) (PID: ProcessId) is using Windows functionality that is not present in this release of Windows. For obtaining an updated version of the application, please, contact the application vendor. The technical information that needs to be conveyed to the application vendor is this: "An RPC method using the name service has been called. Usage and support for the RPC name service has been deprecated for this release of Windows. For information on the deprecation process, please, see http://go.microsoft.com/fwlink/?LinkId=36415." User Action Contact the application vendor for updated version of the application.

Message #

Application (%1) (PID: %2) is using Windows functionality that is not present in this release of Windows. For obtaining an updated version of the application, please, contact the application vendor. The technical information that needs to be conveyed to the application vendor is this: "An RPC method using the name service has been called. Usage and support for the RPC name service has been deprecated for this release of Windows.  For information on the deprecation process, please, see http://go.microsoft.com/fwlink/?LinkId=36415."  User Action Contact the application vendor for updated version of the application.

Fields #

Name	Description
`ApplicationName` UnicodeString
`ProcessId` HexInt32

Event ID 5: Application (ApplicationName) (PID: ProcessId) is using Windows functionality that is not present in this release of Windows.

Provider: Microsoft-Windows-RPC-Events
Channel: Application

Description

Application (ApplicationName) (PID: ProcessId) is using Windows functionality that is not present in this release of Windows. For obtaining an updated version of the application, please, contact the application vendor. The technical information that needs to be conveyed to the application vendor is this: "An RPC method using pipes has been called on on protocol sequence RPCProtocolSequence interface with unique identifier InterfaceGUID. Usage and support of pipes on this protocol sequence has been deprecated for this release of Windows. For information on the deprecation process, please, see http://go.microsoft.com/fwlink/?LinkId=36415." User Action Contact the application vendor for updated version of the application.

Message #

Application (%1) (PID: %2) is using Windows functionality that is not present in this release of Windows. For obtaining an updated version of the application, please, contact the application vendor. The technical information that needs to be conveyed to the application vendor is this: "An RPC method using pipes has been called on on protocol sequence %3 interface with unique identifier %4. Usage and support of pipes on this protocol sequence has been deprecated for this release of Windows. For information on the deprecation process, please, see http://go.microsoft.com/fwlink/?LinkId=36415."  User Action Contact the application vendor for updated version of the application.

Fields #

Name	Description
`ApplicationName` UnicodeString
`ProcessId` HexInt32
`RPCProtocolSequence` UnicodeString
`InterfaceGUID` GUID

Event ID 6: Application (ApplicationName) (PID: ProcessId) is using Windows functionality that is not present in this release of Windows.

Provider: Microsoft-Windows-RPC-Events
Channel: Application

Description

Application (ApplicationName) (PID: ProcessId) is using Windows functionality that is not present in this release of Windows. For obtaining an updated version of the application, please, contact the application vendor. The technical information that needs to be conveyed to the application vendor is this: "An RPC method has been called on a connectionless protocol sequence RPCProtocolSequence. Usage and support of this protocol sequence has been deprecated for this release of Windows. For information on the deprecation process, please, see http://go.microsoft.com/fwlink/?LinkId=36415." User Action Contact the application vendor for updated version of the application.

Message #

Application (%1) (PID: %2) is using Windows functionality that is not present in this release of Windows. For obtaining an updated version of the application, please, contact the application vendor. The technical information that needs to be conveyed to the application vendor is this:  "An RPC method has been called on a connectionless protocol sequence %3. Usage and support of this protocol sequence has been deprecated for this release of Windows. For information on the deprecation process, please, see http://go.microsoft.com/fwlink/?LinkId=36415."  User Action Contact the application vendor for updated version of the application.

Fields #

Name	Description
`ApplicationName` UnicodeString
`ProcessId` HexInt32
`RPCProtocolSequence` UnicodeString

Event ID 7: Application (ApplicationName) (PID: ProcessId) is using Windows functionality that is not present in this release of Windows.

Provider: Microsoft-Windows-RPC-Events
Channel: Application

Description

Application (ApplicationName) (PID: ProcessId) is using Windows functionality that is not present in this release of Windows. For obtaining an updated version of the application, please, contact the application vendor. The technical information that needs to be conveyed to the application vendor is this: "An RPC method has been called on a connectionless protocol sequence RPCProtocolSequence and interface with unique identifier InterfaceGUID. Usage and support of this protocol sequence has been deprecated for this release of Windows. For information on the deprecation process, please, see http://go.microsoft.com/fwlink/?LinkId=36415." User Action Contact the application vendor for updated version of the application.

Message #

Application (%1) (PID: %2) is using Windows functionality that is not present in this release of Windows. For obtaining an updated version of the application, please, contact the application vendor. The technical information that needs to be conveyed to the application vendor is this:  "An RPC method has been called on a connectionless protocol sequence %3 and interface with unique identifier %4. Usage and support of this protocol sequence has been deprecated for this release of Windows. For information on the deprecation process, please, see http://go.microsoft.com/fwlink/?LinkId=36415."  User Action Contact the application vendor for updated version of the application.

Fields #

Name	Description
`ApplicationName` UnicodeString
`ProcessId` HexInt32
`RPCProtocolSequence` UnicodeString
`InterfaceGUID` GUID

Event ID 8: Application (ApplicationName) (PID: ProcessId) has failed to add endpoint RPCProtocolSequence:RPCEndpoint for interface with unique identifier InterfaceGUID with error RPCStatus.

Provider: Microsoft-Windows-RPC-Events
Channel: Application

Description

Application (ApplicationName) (PID: ProcessId) has failed to add endpoint RPCProtocolSequence:RPCEndpoint for interface with unique identifier InterfaceGUID with error RPCStatus. User Action Verify that the machine has sufficient memory. Verify that no other process is listening on the endpoint.

Message #

Application (%1) (PID: %2) has failed to add endpoint %3:%4 for interface with unique identifier %5 with error %6.  User Action Verify that the machine has sufficient memory.  Verify that no other process is listening on the endpoint.

Fields #

Name	Description
`ApplicationName` UnicodeString
`ProcessId` HexInt32
`RPCProtocolSequence` UnicodeString
`RPCEndpoint` UnicodeString
`InterfaceGUID` GUID
`RPCStatus` HexInt32

Event ID 9: Application (ApplicationName) (PID: ProcessId) has failed to complete a COM/RPC call because of an invalid message from server.

Provider: Microsoft-Windows-RPC-Events
Channel: Application

Description

Application () (PID: ) has failed to complete a COM/RPC call because of an invalid message from server. User Action Try the operation again. If the problem persists, contact your system administrator.

Message #

Application (%1) (PID: %2) has failed to complete a COM/RPC call because of an invalid message from server.  User Action Try the operation again. If the problem persists, contact your system administrator.

Fields #

Name	Description
`ApplicationName` UnicodeString
`ProcessId` UnicodeString

Event ID 10: Application (ApplicationName) (PID: ProcessId) has failed to complete a COM call because an incorrect interface ID was passed as a parameter.

Provider: Microsoft-Windows-RPC-Events
Channel: Application

Description

Application (ApplicationName) (PID: ProcessId) has failed to complete a COM call because an incorrect interface ID was passed as a parameter. The expected Interface ID was ExpectedInterfaceID, and the Interface ID returned was ReceivedInterfaceID. User Action Contact the application vendor for updated version of the application.

Message #

Application (%1) (PID: %2) has failed to complete a COM call because an incorrect interface ID was passed as a parameter.  The expected Interface ID was %3, and the Interface ID returned was %4.  User Action Contact the application vendor for updated version of the application.

Fields #

Name	Description
`ApplicationName` UnicodeString
`ProcessId` UnicodeString
`ExpectedInterfaceID` UnicodeString
`ReceivedInterfaceID` UnicodeString

Event ID 11: Possible Memory Leak.

Provider: Microsoft-Windows-RPC-Events
Channel: Application

Description

Possible Memory Leak. Application (ApplicationName) (PID: ProcessId) has passed a non-NULL pointer to RPC for an [out] parameter marked [allocate(all_nodes)]. [allocate(all_nodes)] parameters are always reallocated; if the original pointer contained the address of valid memory, that memory will be leaked. The call originated on the interface with UUID (InterfaceId), Method number (Method). User Action: Contact your application vendor for an updated version of the application.

Message #

Possible Memory Leak.  Application (%1) (PID: %2) has passed a non-NULL pointer to RPC for an [out] parameter marked [allocate(all_nodes)].  [allocate(all_nodes)] parameters are always reallocated; if the original pointer contained the address of valid memory, that memory will be leaked.  The call originated on the interface with UUID (%3), Method number (%4).  User Action: Contact your application vendor for an updated version of the application.

Fields #

Name	Description
`ApplicationName` UnicodeString
`ProcessId` UnicodeString
`InterfaceId` GUID
`Method` Int32

Event ID 2147483657: Application ({param1}) (PID: {param2}) has failed to complete a COM/RPC call because of an invalid message from server.

Provider: Microsoft-Windows-RPC-Events
Channel: Application

Message #

Application ({param1}) (PID: {param2}) has failed to complete a COM/RPC call because of an invalid message from server.  User Action Try the operation again. If the problem persists; contact your system administrator.

Fields #

Name	Description
`param1`
`param2`

Event ID 3221225474: Application ({param1}) (PID: {param2}) is using Windows functionality that is not present in this release of Windows.

Provider: Microsoft-Windows-RPC-Events
Channel: Application

Message #

Application ({param1}) (PID: {param2}) is using Windows functionality that is not present in this release of Windows. For obtaining an updated version of the application; please; 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 on protocol sequence {param3} interface with unique identifier {param4}. Usage and support of synchronous pipes on this protocol sequence has been deprecated for this release of Windows. For information on the deprecation process; please; see http://go.microsoft.com/fwlink/?LinkId=36415.'  User Action Contact the application vendor for updated version of the application.

Fields #

Name	Description
`param1`
`param2`
`param3`
`param4`

Event ID 3221225475: Application ({param1}) (PID: {param2}) is using Windows functionality that is not present in this release of Windows.

Provider: Microsoft-Windows-RPC-Events
Channel: Application

Message #

Application ({param1}) (PID: {param2}) is using Windows functionality that is not present in this release of Windows. For obtaining an updated version of the application; please; 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 on protocol sequence {param3} interface with unique identifier {param4}. Usage and support of synchronous pipes has been deprecated for this release of Windows. For information on the deprecation process; please; see http://go.microsoft.com/fwlink/?LinkId=36415.'  User Action Contact the application vendor for updated version of the application.

Fields #

Name	Description
`param1`
`param2`
`param3`
`param4`

Event ID 3221225476: Application ({param1}) (PID: {param2}) is using Windows functionality that is not present in this release of Windows.

Provider: Microsoft-Windows-RPC-Events
Channel: Application

Message #

Application ({param1}) (PID: {param2}) is using Windows functionality that is not present in this release of Windows. For obtaining an updated version of the application; please; contact the application vendor. The technical information that needs to be conveyed to the application vendor is this: 'An RPC method using the name service has been called. Usage and support for the RPC name service has been deprecated for this release of Windows.  For information on the deprecation process; please; see http://go.microsoft.com/fwlink/?LinkId=36415.'  User Action Contact the application vendor for updated version of the application.

Fields #

Name	Description
`param1`
`param2`

Event ID 3221225477: Application ({param1}) (PID: {param2}) is using Windows functionality that is not present in this release of Windows.

Provider: Microsoft-Windows-RPC-Events
Channel: Application

Message #

Application ({param1}) (PID: {param2}) is using Windows functionality that is not present in this release of Windows. For obtaining an updated version of the application; please; contact the application vendor. The technical information that needs to be conveyed to the application vendor is this: 'An RPC method using pipes has been called on on protocol sequence {param3} interface with unique identifier {param4}. Usage and support of pipes on this protocol sequence has been deprecated for this release of Windows. For information on the deprecation process; please; see http://go.microsoft.com/fwlink/?LinkId=36415.'  User Action Contact the application vendor for updated version of the application.

Fields #

Name	Description
`param1`
`param2`
`param3`
`param4`

Event ID 3221225478: Application ({param1}) (PID: {param2}) is using Windows functionality that is not present in this release of Windows.

Provider: Microsoft-Windows-RPC-Events
Channel: Application

Message #

Application ({param1}) (PID: {param2}) is using Windows functionality that is not present in this release of Windows. For obtaining an updated version of the application; please; contact the application vendor. The technical information that needs to be conveyed to the application vendor is this:  'An RPC method has been called on a connectionless protocol sequence {param3}. Usage and support of this protocol sequence has been deprecated for this release of Windows. For information on the deprecation process; please; see http://go.microsoft.com/fwlink/?LinkId=36415.'  User Action Contact the application vendor for updated version of the application.

Fields #

Name	Description
`param1`
`param2`
`param3`

Event ID 3221225479: Application ({param1}) (PID: {param2}) is using Windows functionality that is not present in this release of Windows.

Provider: Microsoft-Windows-RPC-Events
Channel: Application

Message #

Application ({param1}) (PID: {param2}) is using Windows functionality that is not present in this release of Windows. For obtaining an updated version of the application; please; contact the application vendor. The technical information that needs to be conveyed to the application vendor is this:  'An RPC method has been called on a connectionless protocol sequence {param3} and interface with unique identifier {param4}. Usage and support of this protocol sequence has been deprecated for this release of Windows. For information on the deprecation process; please; see http://go.microsoft.com/fwlink/?LinkId=36415.'  User Action Contact the application vendor for updated version of the application.

Fields #

Name	Description
`param1`
`param2`
`param3`
`param4`

Event ID 3221225480: Application ({param1}) (PID: {param2}) has failed to add endpoint {param3}:{param4} for interface with unique identifier {param5} with error {param6}.

Provider: Microsoft-Windows-RPC-Events
Channel: Application

Message #

Application ({param1}) (PID: {param2}) has failed to add endpoint {param3}:{param4} for interface with unique identifier {param5} with error {param6}.  User Action Verify that the machine has sufficient memory.  Verify that no other process is listening on the endpoint.

Fields #

Name	Description
`param1`
`param2`
`param3`
`param4`
`param5`
`param6`

Event ID 3221225482: Application ({param1}) (PID: {param2}) has failed to complete a COM call because an incorrect interface ID was passed as a parameter.

Provider: Microsoft-Windows-RPC-Events
Channel: Application

Message #

Application ({param1}) (PID: {param2}) has failed to complete a COM call because an incorrect interface ID was passed as a parameter.  The expected Interface ID was {param3}; and the Interface ID returned was {param4}.  User Action Contact the application vendor for updated version of the application.

Fields #

Name	Description
`param1`
`param2`
`param3`
`param4`

Provenance

Where this provider's schema came from, and which Windows build it was observed on. Windows can change a provider's event schema between builds, so use this to judge whether it matches the build you collect from.

ETW provider GUID f4aed7c7-a898-4627-b053-44a7caa12fcd

Defined in rpcrt4.dll, which carries the event manifest.

Observed on:

WS2022-20348.4893, schema read from the registered manifest, binary version 10.0.20348.2849, captured 2026-06-02
Win11-26200.6584, schema read from the registered manifest, binary version 10.0.26100.1, captured 2026-06-02

`j` / `k`	Scroll down / up
`d` / `u`	Half-page down / up
`gg` / `G`	Top / bottom
`h` / `l`	History back / forward
`f`	Follow link (`Shift` = new tab)
`/`	Focus search
`?`	Toggle this help
`↑` / `↓`	Navigate search results
`Enter`	Open highlighted result
`Esc`	Close results / dialog

`type:`	`events` / `rules` / `providers`
`vendor:`	`sigma` / `elastic` / `splunk` / `kusto` / `chronicle` (vendor name alone also works: `sigma:`, `kql:`, `secops:`…)
`tactic:`	TA-id, slug, or name: `credential_access`, `TA0006`
`technique:`	technique or sub-technique ID: `T1003`, `T1003.001` (alias `tech:`)
`severity:`	`critical` / `high` / `medium` / `low` / `informational` (alias `sev:`)
`risk_score`	Numeric comparison on the Elastic risk score (0 to 100): `risk_score>50`, `risk_score<=20`, `risk_score=99` (alias `risk`; Elastic rules only)
`stages:`	Rules with exactly N pipeline stages
`correlation:`	`single_event` / `sequence` / `alternatives` / `alternatives_cross_log` / `all_required` / `correlated`
`with:`	Co-occurrence event-id; stacks (`with:4624 with:4769`) to require all, while a comma list in one occurrence (`with:4624,4769`) is an either-or group. Implies multi-event
`like:`	Structural neighbors of a rule slug (equivalents + subsumption stricter / broader): `like:comsvcs_lsass_memory_dump-splunk-sysmon`
`groupby:`	Entity-grouping substring match against `group_by_keys`: `groupby:user`, `groupby:host`
`uses:`	Rules whose predicate tree touches the field (any kind, any value): `uses:CommandLine`
`excludes:`	Rules with top-level `not()` clauses on the field (FP whitelists): `excludes:ParentImage`
`field:` / `value:`	Predicate search; narrows rule cards to those with a matching leaf and drives the indicator tier. Unquoted = substring, wildcards allowed (`value:mimikatz`)
`indicator:`	Shorthand for `field:F value:V`: `indicator:Image=*\powershell.exe`
`kind:`	Filter by predicate kind. Narrows rule cards to those carrying a matching predicate leaf (`vendor:elastic kind:cidr_match`) and drives the indicator tier: `contains` / `starts_with` / `ends_with` / `regex` / `cidr` / `eq` / `in` … (operator aliases `op:`/`match:`)
`has:` / `no:`	`sample`, `field`, `notes`, `refs`, `trace`, `thirdparty`, `rule`, `pattern`, `timewindow`, `threshold`, `newterms`, `sigma`/`elastic`/`splunk`/`kusto`/`chronicle`
`-op:val`	Exclude matches; works on most operators but not `type:`/`like:`/`has:`/`no:` (use `no:<flag>` to exclude a rule flag): `tactic:execution -vendor:splunk`. Standalone `-kind:`/`-field:`/`-value:` drop every rule carrying a matching predicate leaf (`type:rules -kind:is_null`)
`field:"…"` / `value:"…"`	Quoted value = anchored exact match (also allows spaces): `value:"net user"`
`a,b`	Comma = OR inside one operator (`vendor:sigma,elastic`, `severity:high,critical`); repeating a facet merges the same way. `field:`/`value:` never split (literal commas)
`vendors:` / `stage:`	Singular and plural spellings fold to the canonical operator and value: `tactics:` = `tactic:`, `type:event` = `type:events`, `correlation:sequences` = `correlation:sequence`, `has:thresholds` = `has:threshold`
`"quoted phrase"`	Exact-match a multi-word phrase (free text)

Microsoft-Windows-RPC-Events

Event ID 2: Application (ApplicationName) (PID: ProcessId) is using Windows functionality that is not present in this release of Windows.

Description

Message #

Fields #

Event ID 3: Application (ApplicationName) (PID: ProcessId) is using Windows functionality that is not present in this release of Windows.

Description

Message #

Fields #

Event ID 4: Application (ApplicationName) (PID: ProcessId) is using Windows functionality that is not present in this release of Windows.

Description

Message #

Fields #

Event ID 5: Application (ApplicationName) (PID: ProcessId) is using Windows functionality that is not present in this release of Windows.

Description

Message #

Fields #

Event ID 6: Application (ApplicationName) (PID: ProcessId) is using Windows functionality that is not present in this release of Windows.

Description

Message #

Fields #

Event ID 7: Application (ApplicationName) (PID: ProcessId) is using Windows functionality that is not present in this release of Windows.

Description

Message #

Fields #

Event ID 8: Application (ApplicationName) (PID: ProcessId) has failed to add endpoint RPCProtocolSequence:RPCEndpoint for interface with unique identifier InterfaceGUID with error RPCStatus.

Description

Message #

Fields #

Event ID 9: Application (ApplicationName) (PID: ProcessId) has failed to complete a COM/RPC call because of an invalid message from server.

Description

Message #

Fields #

Event ID 10: Application (ApplicationName) (PID: ProcessId) has failed to complete a COM call because an incorrect interface ID was passed as a parameter.

Description

Message #

Fields #

Event ID 11: Possible Memory Leak.

Description

Message #

Fields #

Event ID 2147483657: Application ({param1}) (PID: {param2}) has failed to complete a COM/RPC call because of an invalid message from server.

Message #

Fields #

Event ID 3221225474: Application ({param1}) (PID: {param2}) is using Windows functionality that is not present in this release of Windows.

Message #

Fields #

Event ID 3221225475: Application ({param1}) (PID: {param2}) is using Windows functionality that is not present in this release of Windows.

Message #

Fields #

Event ID 3221225476: Application ({param1}) (PID: {param2}) is using Windows functionality that is not present in this release of Windows.

Message #

Fields #

Event ID 3221225477: Application ({param1}) (PID: {param2}) is using Windows functionality that is not present in this release of Windows.

Message #

Fields #

Event ID 3221225478: Application ({param1}) (PID: {param2}) is using Windows functionality that is not present in this release of Windows.

Message #

Fields #

Event ID 3221225479: Application ({param1}) (PID: {param2}) is using Windows functionality that is not present in this release of Windows.

Message #

Fields #

Event ID 3221225480: Application ({param1}) (PID: {param2}) has failed to add endpoint {param3}:{param4} for interface with unique identifier {param5} with error {param6}.

Message #

Fields #

Event ID 3221225482: Application ({param1}) (PID: {param2}) has failed to complete a COM call because an incorrect interface ID was passed as a parameter.

Message #

Fields #

Provenance

Downloads