Event ID - 4191

Event Id4191
SourceMicrosoft-Windows-MSDTC
DescriptionMS DTC Transaction Manager start failed. Unable to unpack name object, error %1.%0
Event InformationAccording to Microsoft :
Cause
This event is logged when MS DTC Transaction Manager start failed.
Resolution
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 MSDTC.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 change the size of the log file.
To perform these procedures, must have membership in Administrators or must have been delegated the appropriate authority.
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 UAC dialog box appears, confirm that the action it displays is what 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, look for any transactions with a status of In Doubt.Right-click a transaction with the status of In Doubt, point to Resolve and then click 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 want and then click Continue.
  3. Click Component Services, click Computers, click My Computer and then click Distributed Transaction Coordinator.
  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 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.
Change the MSDTC log path
Ensure that the log path in the Component Services administrative tool points to a folder that exists in the file system.
To perform these procedures,must have membership in Administrators or must have been delegated the appropriate authority.
To open Component Services and check 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 want, and then click Continue.
  3. Click Component Services, click Computers, click My Computer and then click Distributed Transaction Coordinator.
  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, check whether the path in Location points to a valid folder on the file system. If it does not, type a new path in Location, and then restart MSDTC.
  • Restart MSDTC
    Free disk space or move the log file to another drive
    Check the location of the MSDTC log file
    To open Component Services and check 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 want, and then click Continue.
    3. Click Component Services, click Computers, click My Computer, and then click Distributed Transaction Coordinator.
    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, check the path in Location to identify the current drive and location of the log file. By default, the log file is located in the \windows\system32 folder.
    If decide to move the log file to another drive, first stop MSDTC, move the log file and then restart MSDTC.
    Stop MSDTC
    To stop MSDTC:
    1. Click Start and then click Command Prompt.
    2. At the command prompt, type net stop msdtc and then press ENTER.
    Move the MSDTC log file to another drive
    To open Component Services and move the MSDTC log file to another drive:
    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 want, and then click Continue.
    3. Click Component Services, click Computers, click My Computer and then click Distributed Transaction Coordinator.
    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,in Location, type a new drive letter and location for the log file.
  • Restart MSDTC
    Remove the read-only attribute from the MSDTC log
    The system indicates that the log file for the MSDTC is read only.Find the log file.By default, the log file is located in the \windows\system32 folder.
    When locate the log file, remove the read-only file attribute.
    To perform this procedure, you must have membership in Administrators, or you must have been delegated the appropriate authority.
    Run the MSDTC Resetlog utility
    The system indicates that the problem in the log file for the MSDTC may be resolved by running the Resetlog utility.Ensure that there are no transactions in the Transaction List with a status of In Doubt.
    A status of In Doubt means that there is no information available about the outcome of this transaction.This can happen if the connection was lost between the MSDTC proxy and the transaction manager that is acting as the commit coordinator.The transaction may have committed or not. MSDTC lost communication with that transaction manager after preparing, but before receiving,the information about the transaction's outcome.
    The transaction remains prepared and in doubt until communication is restored with the superior transaction manager.The system administrator can force an In Doubt transaction to commit manually by using the Component Services administrative tool.
    Verify that all RMs that enlist in MSDTC transactions are consistent.RMs operate with relational databases, Message Queuing, transactional files, and object-oriented databases.After sure that all RMs are consistent,can force an In Doubt transaction to commit manually.
    To perform these procedures, must have membership in Administrators, or must have been delegatedthe appropriate authority.
    To verify the status of transactions and commit In Doubt transactions manually:
    To run the Reset utility:
    1.Click Start, and then click Command Prompt.
    2.At the command prompt, type msdtc -resetlog, and then press ENTER.
  • Increase the number of MSDTC log buffers
  • Restore Msdtclog.dll, and restart MSDTC
  • Reinstall MSDTC
    • Reference LinksEvent ID 4191 from Source Microsoft-Windows-MSDTC

    Catch threats immediately

    We work side-by-side with you to rapidly detect cyberthreats
    and thwart attacks before they cause damage.

    See what we caught

    Did this information help you to resolve the problem?

    Yes: My problem was resolved.
    No: The information was not helpful / Partially helpful.
     Refresh