Logging of DCOM errors

PI log errors

OSIsoft products log DCOM security errors in the OPC client node’s local PI message log file. Errors might also appear in the Windows System log. You can use these errors to troubleshoot common DCOM errors. Connection errors (CoCreateInstanceEx) indicate problems instantiating the OPC server, usually because the OPC server cannot authenticate the account used by the client or because that account does not have permission to use the server. Advise errors indicate the reverse: the OPC client cannot authenticate the account that is associated with the OPC server, or the account does not have the permissions required to use the interface node.

DCOM failure logging

To configure Windows logging of DCOM failures, use REGEDIT to define the following registry values in the HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Ole entry and set them to 1:

You must restart OPC servers and client instances before these settings take effect. After you enable logging, DCOM security errors appear in the Windows System event log.