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 #

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 #

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 #

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 #

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 #

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 #

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 #

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 #

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 #

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 #

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 #

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 #

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 #

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 #

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 #

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 #

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 #

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 #

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 #