You receive an error message when you try to apply a tracking profile to an x64-based computer in the Tracking Profile Editor

Problem

When you apply a tracking profile to a BizTalk server running on an x64-based computer you receive the error "Failed to apply the tracking profile" along with one or more of the following exception details:

· System.Runtime.InteropServices.COMException: The transaction has already been implicitly or explicitly committed or aborted

· Communication with the underlying transaction manager has failed. (System Transactions)

· Unhandled Exception: System.InvalidOperationException: The Promote method returned an invalid value for the distributed transaction.

Cause

This issue can occur if one or more of the following conditions are true:

· The Microsoft Distributed Transaction Coordinator (MSDTC) service cannot be initialized. This occurs if a lightweight remote procedure call (LRPC) association contains an incorrect Service Principal Name (SPN) in its authentication information structure because of the Winspool.drv file.

· The Tracking Profile Editor tries to use RPC to connect to the MSDTC transaction coordinator. When this occurs, the interface may perform additional security checks.

Resolution

When the Tracking Profile Editor tries to connect to the MSDTC on the local computer, the interface that is used may perform additional security checks. Depending on the operating system version and service packs that are installed on the computer, RPC may perform these additional security checks when the interface does not have a registered security callback.

There are two potential resolutions:

· Use the Group Policy Object Editor to disable the RestrictRemoteClients setting that the RPC configuration enforces.

· Use the Registry Editor to disable the RestrictRemoteClients setting that the RPC configuration enforces.

Source: Microsoft