| Event Id | 3437 |
| Source | MSSQLServer |
| Description | Error recovering database %.*ls. Could not connect to MSDTC to check the completion status of transaction %S_XID. |
| Event Information | CAUSE: When you are using MS DTC to manage a distributed transaction across multiple servers and a loss of connectivity occurs, the distributed transaction is left in an unknown or "in doubt" state. Common sources of interruptions are Network errors Stopping MSSQLSERVER or MS DTC Stopping other involved services on one or more computers that are involved in the distributed transaction. After the connection is disrupted, MS DTC leaves all the transactions in progress at that stage in an inconsistent state. The "in doubt" transactions cause these symptoms because SQL Server cannot determine whether to commit or to roll back the transactions, and SQL Server needs MS DTC to tell it how to proceed. RESOLUTION: There are several different methods that you can use to resolve the inconsistent distributed transactions: You can use the method described in "Troubleshooting MS DTC Transactions" in SQL Server Books Online. If you stop MS DTC on one or more of the servers that are involved in the distributed transaction (or transactions), you might resolve the problem when you restart MS DTC. Frequently, you can use the MS DTC administrative console: Windows 2000: 1. Type "mmc.exe" (without the quotation marks) in the Run dialog box to open Microsoft Management Console (MMC). 2. In MMC, on the Console menu, click Add/Remove Snap-in. 3. In the Add/Remove Snap-in dialog box, click Add. 4. In the Add Standalone Snap-in dialog box, click Component Services, and then click Add to add the snap-in. 5. Click Close. 6. In the Add/Remove Snap-in dialog box, click OK. 7. In the console root under Component Services, expand Component Services, point to Computers, point to My Computer, and then click Distributed Transaction Coordinator. 8. Select Transaction List. You see transactions in the details pane. Right-click the transaction, and then click Resolve. You now have three options: Commit, |
| Reference Links | Microsoft product: SQL Server Version: 2000.80.760.0 Event Source: MSSQLServer Event ID: 3437 |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.