Event ID 4166 — Microsoft Distributed Transaction Coordinator Service Log Availability

Updated: December 3, 2008

Applies To: Windows Server 2008 R2

red

The Microsoft Distributed Transaction Coordinator service (MSDTC) is running on a clustered server for increased reliability, based on the failover capabilities of the clustered servers.

Event Details

Product: Windows Operating System
ID: 4166
Source: Microsoft-Windows-MSDTC
Version: 6.1
Symbolic Name: IDS_DTC_E_TMLOGFULL
Message: The maximum number of active transactions that the MS DTC log file can accomodate has been exceeded. You must increase the size of the MS DTC log file if you wish to initiate more concurrrent transactions.%0

Resolve

Increase the log size or resolve old transactions

The system indicates that there is a problem with the size of the log file for the Microsoft Distributed Transaction Coordinator service (MSDTC). You may be able to fix the problem by resolving old transactions in the Transactions List in the Component Services administrative tool or by increasing the size of the log file. Restart MSDTC if you change the size of the log file.

To perform these procedures, you must have membership in Administrators, or you must have been delegated the appropriate authority.

Open Component Services and manually resolve old transactions:

To open Component Services and manually resolve old transactions:

  1. Click Start, and then click Run.
  2. Type comexp.msc, and then click OK. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
  3. Click Component Services, click Computers, click My Computer, and then click Distributed Transaction Coordinator.
  4. Click Local DTC, and then click Transaction List.
  5. In the Transaction List, right-click the transaction that you want to resolve, point to Resolve, and then click Commit.

    When a transaction's Commit outcome is forced (that is, the transaction is resolved manually as committed), the transaction is designated as Forced Commit.

Open Component Services and change the size of the MSDTC log file:

To open Component Services and change the size of the MSDTC log file:

  1. Click Start, and then click Run.
  2. Type comexp.msc, and then click OK. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
  3. Click Component Services, click Computers, click My Computer, click Distributed Transaction Coordinator, and then click Local DTC.
  4. Right-click the Local DTC, and then click Properties.
  5. In the Local DTC properties dialog box, click the Logging tab. Under Log Information, increase the size of the log file by typing a new number in Capacity, and then click OK.

Restart MSDTC:

To restart MSDTC:

  1. Click Start, and then click Run.
  2. Type comexp.msc, and then click OK. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
  3. Click Services.
  4. In the Services pane, right-click Distributed Transaction Coordinator, and then click Restart.

    The system stops and then restarts MSDTC.

Verify

Use the Component Services administrative tool to verify that the log file for the Microsoft Distributed Transaction Coordinator service (MSDTC) is created in the appropriate location.

To perform this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority.

To open Component Services and verify the location of the MSDTC log file:

  1. Click Start, and then click Run.
  2. Type comexp.msc, and then click OK. If the User Account Control dialog box appears, confirm that the action it displays is what you want, and then click Continue.
  3. Click Component Services, click Computers, click My Computer, click Distributed Transaction Coordinator, and then click Local DTC.
  4. Right-click the Local DTC, and then click Properties.
  5. In the Local DTC properties dialog box, click the Logging tab. Under Log Information, verify that the location of the log file is appropriate for the MSDTC.

Related Management Information

Microsoft Distributed Transaction Coordinator Service Log Availability

Application Server

Community Additions

ADD
Show: