| Event Id | 8520 |
| Source | MSSQLServer |
| Description | Commit of internal MSDTC transaction failed: %hs. |
| Event Information | According to Microsoft Cause: Microsoft Distributed Transaction Coordinator (MS DTC) can ask transaction participants, such as COM+ components or one or more SQL Server instances, to PREPARE as part of the two-phase commit (2PC) protocol. If SQL Server responds that it is ready to COMMIT, but MS DTCs ask for an ABORT for any of a number of reasons, this error appears on the server that issued the COMMIT. Similary, if SQL Server initiated the transaction request and it asked another participant to PREPARE, but in the meantime any of the participants requested an ABORT, the server that initiated the request will report this error. Examples of reasons why the ABORT might be requested are: 1.The transaction timed out based on the application's time-out settings. 2.Another resource manager participating in the transaction may have requested the ABORT. 3.MS DTC may have been shut down during the transaction. The exact result code returned as part of the message varies, and a search on the result code may provide more details about the root cause. For more information about MS DTC, see "MS DTC Service," "Distributed Transactions," "Distributed Transactions Architecture," "Configuring Linked Servers," and "How Immediate Updating Works" in Books Online. Resolution: This message is an indication of normal two-phase commit activity. If you are not sure which application or SQL Server query is calling MS DTC, you can use a SQL Profiler trace to capture which command was aborted. |
| Reference Links | Event Id:8520 of Source Id:MSSQLServer |
Catch threats immediately
We work side-by-side with you to rapidly detect cyberthreats
and thwart attacks before they cause damage.