After never really having much to do with Dynamics all of the sudden in the past few weeks I’ve found myself almost exclusively working with clients using the Microsoft BizTalk Server Adapter for Microsoft Dynamics CRM 4.0 adapter. Developing, troubleshooting, and deploying. One particular scenario involved using CRM 4.0 with BizTalk Server 2010. There’s a gotcha here, the installation package fails. Ugh, the workaround is to hack the registry changing the product name to “Microsoft BizTalk Server 2006”
HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\BizTalk Server\3.0\ProductName = “Microsoft BizTalk Server 2006”
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\BizTalk Server\3.0\ProductName = “Microsoft BizTalk Server 2006”
Don’t forget to reset back to “Microsoft BizTalk Server 2010” after installation.