Shulou(Shulou.com)05/31 Report--

This article introduces how to enable diagnostic tracking of MSDTC on the computer of Windows Server 2003. The content is very detailed. Interested friends can use it for reference. I hope it will be helpful to you.

Transaction manager trace

You can enable transaction manager tracing by using the snap-in (Comexp.msc) of the component Services Microsoft Management console (MMC). Open the component Services MMC snap-in, expand component Services, expand the computer, expand my computer, right-click my computer, and then click Properties. Click the MSDTC tab. Click the trace option on the lower right side of the MSDTC tab. The following options are available:

Turn off the non-tracking feature

Track only aborted transactions

Tracking only transactions open multiple for 1 minute

Track all transactions

When you change the TM tracking configuration, the MSDTC service process detects those changes while reclaiming the process's requirements. For example, when you change the location of a tracked transaction or tracking file, the MSDTC service process detects the changes made in the registry. You did not recycle the MSDTC service process.

MSDTC connection Manager

Note: make sure that the process has access to the registry key. By default, we set permissions that do not create this registry key, and that it does not flow to the key. To configure the tracking feature, you can use Registry Editor. Make sure that the registry value for the trace feature is located in the following registry key:

HKEY_LOCAL_MACHINE\ SOFTWARE\ Microsoft\ MSDTC

To create a registry key for the trace feature, follow these steps:

TraceCMErr

Type: DWORD

Default value: 0

Function: the TraceCMErr registry key specifies whether CM errors are to be tracked.

The following table provides information about the values for the TraceCMErr registry key.

Put away the form and expand the form

The value means 0 to turn off the non-tracking function 1CM error tracking is on, and the value of the TraceCMErrLogName registry key is used as the location of the trace output TraceCMErrLogName

Type: REG_SZ

Default value: if this registry key is set to a non-zero value when the TraceCMErr registry key does not exist, the user id of the process is the TEMP directory. In addition, the name of the file is MsDtcCMErr.txt. The default user ID's MSDTC service is a network service. By default, the temporary folder for the network service is hidden. Typically, this folder is located under the C:\ Documents and Settings\ NetworkService\ Local Settings\ Temp folders on most computers.

Notice that the file name is a placeholder, process id.

Function: the TraceCMErrLogName registry key specifies the fully qualified name of the CM error tracking log file without an extension. The .txt extension will be appended. Because multiple processes can generate CM error tracking log files, the process ID of the process is appended to this name.

Note that the folder specified in the fully qualified name must exist. If the folder does not exist, tracing does not occur. There is no need to track the file name specified in the fully qualified name that occurred.

Go back to the top

Performance

You should not enable the trace feature on the production system unless the Microsoft support representative indicates trace information to diagnose the problem. The performance of the computer may be affected. Once the cause of the problem has been identified and resolved, you should disable the tracking feature.

By default, tracing is disabled. As a result, there is no regular installation of any performance impact.

The process loaded by the Msdtcprx.dll file is recycled when your changes to the tracking configuration for this content management error take effect. For example, for CM error tracking, the MSDTC service process is recycled when changes made to the configuration take effect.

When you change the TM tracking configuration MSDTC service process detects these changes while in the recycling process requirements. For example, the MSDTC service process detects changes made in the registry for a tracking file of a transaction or location tracked by a change. You did not recycle the MSDTC service process.

Ensure that these entries are included in all registries on all nodes installed for the cluster. Any node cluster code that does not have these entries ignores the registry entries shared in because the entries do not exist in the local computer registry.

Go back to the top

Example of output

The trace log file contains information about the process, thread, date, and transaction identification and activities that have been tracked.

TM tracking

The TM trace log file information in might be similar to the following:

Pid=3132; tid=280; time=01/25/2005-17 time=01/25/2005 43 20. 120; seq=85; eventid=TRACE_SETTINGS;; "Trace Configuration (OFF = 0 and ON = 1): Tracing Of DTC = 1, Tracing Of Transactions = 1, Tracing Of Aborted Transactions = 1, Tracing Of Long-Lived Transactions = 1, Tracing Of All Transactions = 1, Max Limit on Memory Buffers = 25." pid=3132; tid=3324; time=01/25/2005-17 14 43 Tracing Of Aborted Transactions 23.592 Seq=86; eventid=TRANSACTION_BEGUN; tx_guid=d3c61c1d-9528-44ff-b2f6-5acaf6b83095; "transaction got begun, description:''"pid=3132"; tid=2832; time=01/25/2005-17 eventid=CHECKPOINTING_STOPPED; 46.945; seq=87; eventid=CHECKPOINTING_STOPPED; "MSDTC is suspending the checkpointing of transactions due to lack of activity" pid=3132; tid=3324; time=01/25/2005-17 Seq=88; eventid=TRANSACTION_BEGUN; tx_guid=d3c61c1d-9528-44ff-b2f6-5acaf6b83095; "transaction got begun, description:''"pid=3132"; tid=2844; time=01/25/2005-17 seq=88 4515; 23.592; seq=89; eventid=TRANSACTION_PROPOGATED_TO_CHILD_NODE; tx_guid=d3c61c1d-9528-44ff-b2f6-5acaf6b83095; "transaction propagated to 'F07M03'as transaction child node # 1" pid=3132; tid=2932 Time=01/25/2005-17 44ff-b2f6 45 time=01/25/2005 23.608; seq=90; eventid=RECEIVED_COMMIT_REQUEST_FROM_BEGINNER; tx_guid=d3c61c1d-9528-44ff-b2f6-5acaf6b83095; "received request to commit the transaction from beginner" CM error tracking

Tracking log file information in content management errors may be similar to the following:

08-04-2004 10:35 08 com 710: CM Error Value = 0x00000000, Calling RpcServerRegisterAuthInfo with Someone@somehwere.com as SPN, d:\ nt\ com\ complus\ dtc\ dtc\ cm\ src\ iomgrrpc.cpp (401) 08-04-2004 10:35 08 Calling RpcServerRegisterAuthInfo with Someone@somehwere.com as SPN 710: CM Error Value = 0x000006d9, Call to RpcMgmtInqServerPrincName failed-- Could not determine if partner supports secure calls, d:\ nt\ com\ complus\ dtc\ dtc\ cm\ src\ iomgrclt.cpp: CM Error Value = 0x80000171, Call to SetRpcSecurity failed D:\ nt\ so much for the MSDTC enabled Diagnostics trace on Windows Server 2003 computers. I hope the above content can be of some help to you and learn more knowledge. If you think the article is good, you can share it for more people to see.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.