Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Fields

Message

Unable to translate the MS DTC error code to the appropriate MS DTC error message. The MS DTC error code was: %1.

Fields

Message

You do not have permissions to manage the MS DTC on this system. MS DTC administrative functionality will be disabled.

Fields

Message

String message: %1.

Fields

Message

During the MS DTC installation, the attempt to delete the dtclog directory failed. This was done since the location of the log directory has been changed to msdtc. This can happen if the dtclog directory is not empty. Internal Information : %1.

Fields

Message

The MSDTC TM could not determine if an incoming connection request is from a remote machine. For security reasons, it will treat this connection request as a remote connection request. If the NetworkClients security option is not enabled, this can cause it to reject this connection attempt. This can cause applications to report that the TM is not available. Error Specifics: %1

Fields

Message

During MS DTC installation, the attempt to preserve the old log file failed. The MS DTC installation will continue, however any information present in the old log file will get lost. Internal Information : %1.

Fields

Message

The connection manager in a MS DTC component has received an invalid message. Event specific Information: %1.

Fields

Message

The local MS DTC detected that the MS DTC on %1 has the same unique identity as the local MS DTC. This means that the two MS DTC will not be able to communicate with each other. This problem typically occurs if one of the systems were cloned using unsupported cloning tools. MS DTC requires that the systems be cloned using supported cloning tools such as SYSPREP. Running 'msdtc -uninstall' and then 'msdtc -install' from the command prompt will fix the problem. Note: Running 'msdtc -uninstall' will result in the system losing all MS DTC configuration information.

Fields

Message

MS DTC log path not found.

Fields

Message

Could not force transaction outcome.

Fields

Message

Transaction not found.

Fields

Message

The transaction is not a child transaction.

Fields

Message

The transaction cannot be forced to abort or commit because the transaction's state is not "In Doubt".

Fields

Message

Either the transaction is not committed or there are resource managers or subordinate MS DTC Transaction Managers still connected.

Fields

Message

Could not resolve the transaction due to an unknown error.

Fields

Message

MS DTC encountered an internal error and is terminating.

Fields

Message

A critical error occurred in an MS DTC component therefore the process is terminating. The category field identifies the component that encountered the error. Please contact Microsoft Product Support. Error Specifics: %1

Fields

Message

Failed to convert the caller provided TIP Transaction URL into a valid MS DTC Transaction Id. This error is unexpected because the TIP Transaction URL indicates that the transaction originated on this system. Error Specifics: %1

Fields

Message

Unable to get the file name for the OLE Transactions Proxy DLL. Error Specifics: %1

Fields

Message

Failed to dynamically load the OLE Transactions Proxy DLL. Error Specifics: %1

Fields

Message

The "DllGetTransactionManagerCore" function is missing from the OLE Transactions Proxy DLL. Error Specifics: %1

Fields

Message

Failed to connection to the registry on the remote MS DTC Transaction Manager's system. Error Specifics: %1

Fields

Message

Failed to open the registry key containing the list of transaction managers. Error Specifics: %1

Fields

Message

Failed to read the name of the default transaction manager from the registry. Error Specifics: %1

Fields

Message

Failed to open the registry key containing the name of the OLE Transactions Proxy DLL. Error Specifics: %1

Fields

Message

Failed to read the name of the OLE Transactions Proxy DLL from the registry. Error Specifics: %1

Fields

Message

Failed to start MS DTC via the MS DTC Proxy DLL. Error Specifics: %1

Fields

Message

Unable to start MS DTC because initialization of cluster support failed.

Fields

Message

An MS DTC component was unable to allocate memory for a critical operation. That component is terminating. The category field identifies the component that failed. Please restart MS DTC if it does not restart automatically. Error Specifics: %1

Fields

Message

Failed to initialize the MS DTC Communication Manager.  Error Specifics: %1

Fields

Message

MS DTC is unable to communicate with MS DTC on a remote system. No common RPC protocol is supported between the two systems. Please ensure that one or more of the following RPC protocols are common to both systems: TCP/IP, SPX, or NetBEUI.  Error Specifics: %1

Fields

Message

The MS DTC Connection Manager is unable to register with RPC to use one of LRPC, TCP/IP, or UDP/IP. Please ensure that RPC is configured properly. If "ServerTcpPort" registry key is configured(DWORD value under the HKEY_LOCAL_MACHINE\Software\Microsoft\MSDTC for local DTC instance or under cluster hive for clustered DTC instance), please verify if the configured port is valid and the port is not already in use by a different component. Error Specifics:%1

Fields

Message

MS DTC is unable to communicate with MS DTC on a remote system. MS DTC on the primary system established an RPC binding with MS DTC on the secondary system. However, the secondary system did not create the reverse RPC binding to the primary MS DTC system before the timeout period expired. Please ensure that there is network connectivity between the two systems.  Error Specifics:%1

Fields

Message

Could not establish connection to trace transaction.

Fields

Message

No transaction is selected.

Fields

Message

Transaction not found.

Fields

Message

The version of the transaction manager is not compatible for this feature.

Fields

Message

The attempt to dump the transaction to a trace file failed.

Fields

Message

MS DTC Tracing infrastructure : the initialization of the tracing infrastructure failed. Internal Information : %1.

Fields

Message

MS DTC Tracing infrastructure : the attempt to create a new trace session failed. Internal Information : %1.

Fields

Message

MS DTC Tracing infrastructure : the attempt to stop the existing trace session failed. Internal Information : %1.

Fields

Message

MS DTC Tracing infrastructure : the attempt to flush the existing trace data failed. Internal Information : %1.

Fields

Message

MS DTC Tracing infrastructure : the attempt to update the maximum buffer count of the existing trace session failed. Internal Information : %1.

Fields

Message

MS DTC Tracing infrastructure : the infrastructure has reported that the number of trace events that have been lost until now is equal to %1.

Fields

Message

MS DTC Tracing infrastructure : the thread launched to update the trace settings has failed. Any changes to the trace settings made using the "Tracing Options" dialog box might not take the desired effect. Internal Information : %1.

Fields

Message

MS DTC Tracing infrastructure : the attempt to set the trace specific registry settings failed. Any tracing specific functionality will be disabled. Internal Information : %1.

Fields

Message

Failed to create a new trace session.

Fields

Message

Failed to stop the existing trace session.

Fields

Message

Failed to flush the existing trace data.

Fields

Message

Failed to update the maximum buffer count of the existing trace session.

Fields

Message

Failed to update all the trace settings in the registry.

Fields

Message

Failed to load all the trace settings from the registry.

Fields

Message

MS DTC Tracing infrastructure : the attempt to create the trace directory failed. Any tracing specific functionality will be disabled. Internal Information : %1.

Fields

Message

MS DTC Tracing infrastructure : the infrastructure has reported that an attempt to trace an event has failed cause of lack of enough buffer space. The tracing infrastructure will retry tracing this event. The total number of times this has happened so far is equal to %1. Increasing the max number of memory buffers might rectify the situation.

Fields

Message

Failed to read the needed name objects from the registry. Error Specifics: %1

Fields

Message

Failed to initialize the needed name objects. Error Specifics: %1

Fields

Message

Failed to stop MSDTC service or one of its dependent services. Error Specifics: %1

Fields

Message

Failed to set the security attributes on the MS DTC service. Internal Information : %1.

Fields

Message

Failed to stop the MS DTC service. Internal Information : %1.

Fields

Message

Failed to restart the MS DTC service. Internal Information : %1.

Fields

Message

A MS DTC component has encountered an internal error. The process is being terminated. Error Specifics: %1

Fields

Message

MS DTC was unable to start because this version of dtc is less than the least valid version allowable specified in the cluster database. This can happen if a higher incompatible version of MS DTC was installed on another node of the cluster. Error Specifics: %1

Fields

Message

MS DTC was unable to start because this version of dtc is not compatible with the version of MS DTC installed on another node of the cluster. This can happen if an incompatible version of MS DTC was installed on another node of the cluster. Error Specifics: %1

Fields

Message

Failed to prepare MSDTC for imaging. Sysprep phase: "%1" failed with error: %2

Fields

Message

Unexpected error (%1) when connecting to the Kernel Transaction Manager.

Fields

Message

Unable to create a communication channel to the Kernel Transaction Manager.  The attempt failed with error: %1.

Fields

Message

MSDTC was unable to migrate its log during Windows upgrade. The attempt failed with error: %1.

Fields

Message

MSDTC encountered an error during migration of contact identifiers. The attempt failed with error: %1.

Fields

Message

MSDTC encountered an error during Windows upgrade. Error specifics: %1.

Fields