Hello All, It’s time for a little Biz Talk…
Gone through this error recently and I wanted to blog this so that users who might face this kind of issue are relieved. From the above error; what’s the main issue cause cannot be so easily guessable or displayed for quick resolution approach for a system admin. The primary cause for this kind of error is name resolution between BizTalk and SQL servers. We have to ensure that the name resolution is proper between Web/BizTalk and SQL servers. Check the ping results from Web to SQL for FQDN (Fully Qualified Domain Name; example.test.com) and DNS Name only(example) of the SQL server, and be assured that proper reach of the right server is seen in this case. And ensure in the NIC settings of SQL server that DNS suffix is not specified particularly to any other domains, or for safe side the domain this SQL server resides can be mentioned, however not required when auto register option is selected.
For this settings to check, Go to Network Connections; which can be opened via NCPA.CPL command and then open the Network Interface which is the connection interface between WEB and SQL nodes talk and then Go to properties of the Ethernet adapter and click on TCP/IP 4 version and click on properties again to have this accessed.
Then Ensure the above tick boxes are there for this NIC to have a proper name resolution in the network.
This must solve the case of name resolution between nodes for proper communication. Reach me out if you have any queries regarding this case.