Event ID - 4193

Event Id4193
SourceMicrosoft-Windows-MSDTC
DescriptionA resource manager performed recovery and called ReenlistmentComplete indicating that recovery was complete. However, there is at least one transaction that was enlisted with the resource manager whose state is still "In Doubt"%0
Event Information According to Microsoft :

Cause :

This event is logged when a resource manager performed recovery and called ReenlistmentComplete indicating that recovery was complete.

Resolution :

Resolve the In Doubt transactions

The Microsoft Distributed Transaction Coordinator service (MSDTC) reported that the outcome for a transaction has a status of In Doubt. This means that there is no information available about the outcome of this transaction. This can happen if the connection between the MSDTC proxy and the transaction manager that is acting as the commit coordinator was lost. 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 the transaction to commit manually by using the Component Services administrative tool.

Ensure that all Resource Managers (RM) that enlist in MSDTC transactions are consistent. RMs operate with relational databases, Message Queuing, transactional files, and object-oriented databases. After you are sure that all RMs are consistent, commit the transaction manually.

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

To commit the transaction manually:
  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 lick Distributed Transaction Coordinator .
  4. Click Local DTC , and then click Transaction List .
  5. In the Transaction List , right-click the transaction with the status of In Doubt , point to Resolve , and then click Commit .
    When a transaction's Commit outcome is forced (that is, when the transaction is committed manually), the transaction is designated as Forced Commit .
Verify :

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

To verify that the Microsoft Distributed Transaction Coordinator service (MSDTC) is running:
  1. Click Start , and then click Command Prompt .
  2. At the command prompt, type sc query msdtc , and then press ENTER.
  3. The system responds with information about the service. Confirm that these two items appear: SERVICE_NAME: msdtc and STATE : 4 RUNNING .
Reference LinksEvent ID 4193 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