I received a request to help reconfigure a BizTalk server and point it to a new BizTalk group and reconfigure the BizTalk HL7 Accelerator to use the new SQL Server as well. Reconfiguring the Primary BizTalk server went as smooth as to be expected, but when we went to reconfigure the BizTalk server, we ran into a strange issue regarding the database server. Everything was going fine, until we came to configuring the Auditing and Logging Database. The database name will still set to the old server (in our case it ended with 0144).
I checked the file system and couldn’t find any reference to the old server. I, also, did a quick scan of the Registry for the old server name, but came up with nothing. I decided to open up the installation MSI with ORCA and I found a registry setting that looked promising.
I checked the registry again, but I couldn’t find the registry setting. This is installed on a 64-bit Windows Server 2008 R2 server, so 32-bit components are stored separately in the registry (more information at Microsoft). Looking in the Wow6432Node, I finally found the registry setting that was causing the issue.
Windows Server 2008 64-bit Registry Path / Key Name:
- HKEY_LOCAL_MACHINESOFTWAREWow6432NodeMicrosoftBizTalk Accelerator for HL7
- HKEY_LOCAL_MACHINESOFTWAREWow6432NodeMicrosoftBizTalk Accelerator for HL7Version 2009Setup
Windows Server 2008 32-bit Registry Path / Key Name:
- HKEY_LOCAL_MACHINESOFTWAREMicrosoftBizTalk Accelerator for HL7
- HKEY_LOCAL_MACHINESOFTWAREMicrosoftBizTalk Accelerator for HL7Version 2009Setup
After making the changes to the DbConnStr and DatabaseServer registry entries, I was able to re-run the installer and this time the configuration came up with the correct database server.
I am not sure how often this situation comes up, but it has come up at least twice for me. Let me know if you have any questions.