The MSDTC transaction manager was unable to push the transaction to the destination transaction manager due to communication problems. Possible causes are: a firewall is present and it doesn't have an exception for the MSDTC process, the two machines cannot find each other by their NetBIOS names, or the support for network transactions is not enabled for one of the two transaction managers.
The MSDTC service cannot start because its contact identifiers are either missing, inaccessible, or corrupt. Running 'msdtc ...
The MSDTC service will be stopped and restarted. All dependent services will be stopped. Applications using MSDTC may need ...
The MSDTC TM could not determine if an incoming connection request is from a remote machine. For security reasons, it will ...
The MSDTC transaction manager was unable to pull the transaction from the source transaction manager due to communication ...
The MSDTC transaction manager was unable to push the transaction to the destination transaction manager due to communication ...
The Msft_WmiProvider_AccessCheck_Post event class represents an event generated immediately following completion of the provider's ...
The Msft_WmiProvider_AccessCheck_Pre event class represents an event generated immediately prior to calling the provider's ...
The Msft_WmiProvider_CancelQuery_Post event class represents an event generated immediately following completion of the provider's ...
The Msft_WmiProvider_CancelQuery_Pre event class represents an event generated immediately prior to calling the provider's ...