This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(64, 19%, 16%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESE%3C/text%3E%3C/svg%3E)
I have a BTS 2013 with latest CU, on win2k12, SQL 2k16 where I have done so many POCs. Since almost 2 years, I did not have the need to work with it so the VM was shut down.
This morning, I needed to access one of the workflows, triggered the VM, when click on Biztalk group I get an error that BTS was unable to establish connection to BiztalkMgmtDb as follows
Of course all BTS services re stopped and not running. In event viewer, messagees do not helop a lot
So I am not sure where to investigate?
Have you checked that SQL is running? Do you have SQL Management Studio installed. Have you checked that you can connect from there to the SQL Server databases?
Hi Colin, any idea how to unearth this issue?
This comment has been deleted due to a violation of our Code of Conduct. The comment was manually reported or identified through automated detection before action was taken. Please refer to our Code of Conduct for more information.
Yes Colin, SQL is up and running, SSMS 20 (I imstalled it uesterday) and it can connect with no issues. .Net 4.7.2 as well
What Cumulative Update have you got installed? CU7?
Did you try logging in to the DB using the BizTalk Host Instance user?
I think is the latest one, CU8
Colin, in fact, I tried to apply the CU8, I got the following error
In the log, I see
[11/29/24 12:23:20] Begin distributed transaction.
[11/29/24 12:23:20] Apply patch: Server="SQL2K12", Database="BizTalkMgmtDb", Script="C:\Program Files (x86)\Microsoft BizTalk Server 2013\Schema\BTS_Tracking_Editor.sql".
[11/29/24 12:23:36] dataSource.Open HRESULT=0x80004005
[11/29/24 12:23:36] Failed to apply patch. HRESULT=0x80004005
[11/29/24 12:23:36] Abort distributed transaction.
[11/29/24 12:23:36] Failed to patch one or more BizTalk databases. See log for details. (HRESULT=0x80004005)
[11/29/24 12:23:36] The custom action returned -2147467259.
[11/29/24 12:23:36] One of the custom actions failed. The installation cannot continue. See log for details.
[11/29/24 12:31:47] Stopping services after installation. 0 services to stop.
[11/29/24 12:31:47] Restarting previously stopped services...
[11/29/24 12:31:47] Starting service WINMGMT...
Yes I opened a session with BizTalk Host Instance user ansd accessed the SQL without any issue and this user is an admin user
Colin, I mistakenly talked about CU, in fact I was mixing between 2 BTS platforms. The one where I had the issue where I cant apply the CU8 wit the error mentioned above, I checked the rgistry, I think it is oin RTM if I am not mistaken
Starting to seem like an issue with MSDTC. Have you checked the configuration of that?
Here are the resultas of DTCPing from both machines, BTS2k13 and sql, it seems everything is OK
Please refer to following log file for details:
C:\Temp\DTCPing\BTS2K133808.log
Invoking RPC method on SQL2K12
RPC test is successful
++++++++++++RPC test completed+++++++++++++++
Please start PING from SQL2K12 to complete the test
Please send following LOG to Microsoft for analysis:
Partner LOG: SQL2K129184.log
My LOG: BTS2K133808.log
++++++++++++Start Reverse Bind Test+++++++++++++
Received Bind call from SQL2K12
Trying Reverse Bind to SQL2K12
Reverse Binding success: BTS2K13-->SQL2K12
++++++++++++Reverse Bind Test ENDED++++++++++
++++++++++++Start DTC Binding Test +++++++++++++
Trying Bind to SQL2K12
Received reverse bind call from SQL2K12
Binding success: BTS2K13-->SQL2K12
++++++++++++DTC Binding Test END+++++++++++++
and here is the ouput from the sql VM
Please send following LOG to Microsoft for analysis:
Partner LOG: BTS2K133808.log
My LOG: SQL2K129184.log
++++++++++++Validating Remote Computer Name++++++++++++
Please refer to following log file for details:
C:\DTCPing\SQL2K129184.log
Invoking RPC method on BTS2K13
RPC test is successful
++++++++++++RPC test completed+++++++++++++++
++++++++++++Start DTC Binding Test +++++++++++++
Trying Bind to BTS2K13
Received reverse bind call from BTS2K13
Binding success: SQL2K12-->BTS2K13
++++++++++++DTC Binding Test END+++++++++++++
++++++++++++Start Reverse Bind Test+++++++++++++
Received Bind call from BTS2K13
Trying Reverse Bind to BTS2K13
Reverse Binding success: SQL2K12-->BTS2K13
++++++++++++Reverse Bind Test ENDED++++++++++
Your SQL server is called SQL2K12 but it is actually running SQL Server 2016? Using SQL Server 2016 for the BizTalk DBs isn't actually a supported configuration. You can only use up to SQL Server 2012 with BizTalk 2013, SQL Server 2012 with BizTalk 2013 R2. If you want to use SQL 2016, you needs aBizTalk 2020. If you want to use SQL 2022, you need BizTalk 2020 with CU 6.
OK, got it. This sl was in fact sql2k12 but I upgraded it to 2016. So, if I setup a new VM with SQL2k12,, restore BTS Dbs from the actual 2k16 to the new 2k12 VM would that work? If yes, Where or how I tell BTS to connect to the new SQL2K12?
You will have to unconfigure BizTalk and then re-configure BizTalk to point to a new database. If you are moving the databases, follow the steps in https://learn.microsoft.com/en-us/biztalk/core/how-to-move-the-biztalk-server-databases
I tried to backup all BTS DBs but cant restore them to th new sql2k12 because of version 130 and 110. I tried DAC package generated on the current sql, did not work neither. I know the reommended way is to do log shipping but afrais that it won't work neither. Any idea please?
You might have to unconfigure BizTalk and then re-configure it, so it re-creates the databases. Then of course you will need to re-deploy the BizTalk applications to the BizTalk DB.
Hi Colin, whatever I try I get errors except for SSO config
And same thing when I try basic config
Colin, the error displayed under group reminds me of the same issue with SSMS 20 and last updates for sql where we should explicity choose which encryption to use, since that time, I always was able to connect by chosing optional
So maybe the mentioned error in the BTS config might be related to this?