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.%0
The local domain controller received an intersite replication message with an incompatible message version number. The message ...
The local folder for the namespace root share could not be created. To resolve this issue use the DFS Management snap-in ...
The local folder specified ({0}) already exists on the server ({1}). The file system access control lists (ACL) on the folder ...
The local forest contains multiple name suffixes. To prevent routing authentication requests using a particular suffix to ...
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 ...
The local path for the namespace must be on a cluster managed disk resource in the same group as the cluster managed network ...
The Local Security Authority is unable to obtain an RPC connection to the Active Directory Domain Controller %s. Please check ...
The local security settings database cannot be edited from the Security Configuration and Analysis snap-in. Use the Group ...
The local WINS has been informed by a remote WINS with address, %1, to update the version number of a record. This is because ...