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
ネットワーク エラー
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.
For more information about errors 3437, 3437, and "Could Not Connect to DTC" when you start SQL Server, see the Microsoft Knowledge Base article 306366.
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.
To use the MS DTC administrative console:
.Type "mmc.exe" (without the quotation marks) in the Run dialog box to open Microsoft Management Console (MMC)
.In MMC, on the Console menu, click Add/Remove Snap-in
.In the Add/Remove Snap-in dialog box, click Add
.In the Add Standalone Snap-in dialog box, click Component Services, and then click Add to add the snap-in.
.[閉じる] をクリック
.In the Add/Remove Snap-in dialog box, click OK
.In the console root under Component Services, expand Component Services, point to Computers, point to My Computer, and then click Distributed Transaction Coordinator
.Select Transaction List.You see transactions in the details pane.Right-click the transaction, and then click Resolve.You now have three options: Commit, Abort, or Forget.Choose the one that is appropriate for your situation
Target | Microsoft.SQLServer.2012.DBEngine | ||
Category | EventCollection | ||
Enabled | True | ||
Event_ID | 3437 | ||
Event Source | $Target/Property[Type="SQL!Microsoft.SQLServer.DBEngine"]/ServiceName$ | ||
Alert Generate | True | ||
Alert Severity | Warning | ||
Alert Priority | Normal | ||
Remotable | True | ||
Alert Message |
| ||
Event Log | Application | ||
Comment | Mom2012ID='{6B1C776D-E075-4F73-B9C0-66CEF9024905}';MOM2012GroupID={467ECC75-C5DA-42BD-955C-A73BBB51AF74} |
ID | Module Type | TypeId | RunAs |
---|---|---|---|
_F6DA1507_12AF_11D3_AB21_00A0C98620CE_ | DataSource | Microsoft.Windows.EventProvider | Microsoft.SQLServer.SQLDefaultAccount |
GenerateAlert | WriteAction | System.Health.GenerateAlert | Default |
<Rule ID="Microsoft.SQLServer.2012.Error_recovering_database_._Could_not_connect_to_MSDTC_to_check_the_completion_status_of_transaction_1_5_Rule" Target="SQL2012Core!Microsoft.SQLServer.2012.DBEngine" Enabled="true" ConfirmDelivery="true" Remotable="true" Comment="Mom2012ID='{6B1C776D-E075-4F73-B9C0-66CEF9024905}';MOM2012GroupID={467ECC75-C5DA-42BD-955C-A73BBB51AF74}">
<Category>EventCollection</Category>
<DataSources>
<DataSource ID="_F6DA1507_12AF_11D3_AB21_00A0C98620CE_" Comment="{F6DA1507-12AF-11D3-AB21-00A0C98620CE}" TypeID="Windows!Microsoft.Windows.EventProvider" RunAs="SQL!Microsoft.SQLServer.SQLDefaultAccount">
<ComputerName>$Target/Host/Property[Type="Windows!Microsoft.Windows.Computer"]/NetworkName$</ComputerName>
<LogName>Application</LogName>
<Expression>
<And>
<Expression>
<SimpleExpression>
<ValueExpression>
<XPathQuery>PublisherName</XPathQuery>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value>$Target/Property[Type="SQL!Microsoft.SQLServer.DBEngine"]/ServiceName$</Value>
</ValueExpression>
</SimpleExpression>
</Expression>
<Expression>
<SimpleExpression>
<ValueExpression>
<XPathQuery>EventDisplayNumber</XPathQuery>
</ValueExpression>
<Operator>Equal</Operator>
<ValueExpression>
<Value>3437</Value>
</ValueExpression>
</SimpleExpression>
</Expression>
</And>
</Expression>
</DataSource>
</DataSources>
<WriteActions>
<WriteAction ID="GenerateAlert" TypeID="SystemHealth!System.Health.GenerateAlert">
<Priority>1</Priority>
<Severity>1</Severity>
<AlertMessageId>$MPElement[Name="Microsoft.SQLServer.2012.Error_recovering_database_._Could_not_connect_to_MSDTC_to_check_the_completion_status_of_transaction_1_5_Rule.AlertMessage"]$</AlertMessageId>
<AlertParameters>
<AlertParameter1>$Data/EventDescription$</AlertParameter1>
</AlertParameters>
<Suppression>
<SuppressionValue/>
</Suppression>
</WriteAction>
</WriteActions>
</Rule>