BizTalk Server Administration Error – Failed to enable constraints

6 min read December 23, 2021

Failed to enable constraints. One or more rows contain values violating non-null, unique, or foreign-key constraints. (Microsoft.BizTalk.Administration.SnapIn)

Table of Contents

Introduction

I have recently encountered an error during some troubleshooting related to BizTalk. The error was pretty much known to me, and I want to share the solution with the community. So in the future, if anyone faces this issue, they can try this option as well.

When I was trying to expand the applications, the below error popped up, and it failed to load the applications.

Error – Failed to enable constraints

TITLE: BizTalk Server Administration

——————————

Failed to enable constraints. One or more rows contain values violating non-null, unique, or foreign-key constraints. (Microsoft.BizTalk.Administration.SnapIn)

——————————

BUTTONS: OK

Even I was able to open Host and HostInstance.

Cause

There could be multiple causes for this issue, and the most common cause is connectivity issues between the BizTalk application and database. So to troubleshoot this issue, we have to check the connectivity and then the event log for any type of error.

Resolution

In such cases, first check if you are able to connect BizTalk databases, mainly BizTalkMgmtDb. If yes, then you are good at the connectivity part.

Now the second step is to check if the DTC (Distributed Transaction Coordinator) service is running or not on the BizTalk application server. If the DTC service is stopped, then start it; if it’s already running, then just restart the DTC service.

Most BizTalk Server runtime operations require Microsoft Distributed Transaction Coordinator (MSDTC) support to ensure that the operations are transactionally consistent. If MSDTC transaction support is not available, then the associated BizTalk Server runtime operations cannot proceed. The components of BizTalk that are commonly affected when MSDTC transaction support is not configured correctly include (but are not limited to) the Single Sign-On Service, BizTalk host instances, and any SQL Server instances that are connected to BizTalk Server. This section contains information that describes MSDTC-related errors and steps that can be followed to diagnose and resolve problems with MSDTC.

Errors that can occur if MSDTC transaction support is not configured correctly

Errors similar to the following may occur on BizTalk Server when MSDTC transaction support is not configured correctly on the computers in a BizTalk environment:

“A Microsoft Distributed Transaction Coordinator problem prevented connection to the Configuration database. The transaction manager has disabled its support for remote/network transactions”.
“A Microsoft Distributed Transaction Coordinator problem prevented connection to the Configuration database. The transaction has already been implicitly or explicitly committed or aborted”.
“Error Code: 0x8004d00a, New transaction cannot enlist in the specified transaction coordinator”.
“Could not retrieve transport type data for Receive Location ‘MySample ReceiveLocation’ from config store. Primary SSO Server ‘MyServer’ failed. The RPC server is unavailable”.
“Error Code: 0x8004d025, The partner transaction manager has disabled its support for remote/network transactions”.
“Error Code: 0xc0002a24, Could not import a DTC transaction. Please check that MSDTC is configured correctly for remote operation”.
“0x8004d01c
[0x1705] There was a failure creating the internal work item.
Make sure that SQL Server is running.”

To resolve MSDTC configuration errors, follow the steps below.

Ensure NetBIOS name resolution between the BizTalk Server and remote servers is successful
Ensure that a firewall between the BizTalk Server and remote servers is not blocking ports required for RPC dynamic port allocation
Set the appropriate MSDTC Security Configuration options
Set the appropriate values for the EnableAuthEpResolution and RestrictRemoteClients options
If Windows Firewall is running, add an exception for the MSDTC service
Use DTCTester or DTCPing to verify MSDTC functionality over the network
Ensure that MSDTC is assigned a unique CID value
Consider reinstalling the Distributed Transaction Coordinator service if other troubleshooting steps are not successful

Verification

Issue resolved and try to refresh the BizTalk admin console, Boom, all set to go!

Integration Techie