There seems to be an intermittent deployment problem with BizTalk 2006, that has been the cause of much time wasting. When attempting to deploy BizTalk artefacts either explicitly using the BizTalk Administration Console or the Visual Studio deploy functionality results in the following:
Error 26 Failed to add resource(s). Change requests failed for some resources. BizTalkAssemblyResourceManager failed to complete end type change request. Failed to update binding information. Could not enlist orchestration ‘Net.Bencode.Orchestration,Orchestration, Version=184.108.40.206, Culture=neutral’. Could not enlist orchestration ‘Orchestration.TestProcess’. All orchestration ports must be bound and the host must be set.
Most unusual—binding validation issues at deployment time. Thanks to James French soon discovered that the issue is related to the bindings cache that BizTalk maintains. In short, BizTalk creates (using assembly reflection) and maintains (using the BizTalkMgmt database) BindingInfo.xml files in the C:\Documents and Settings\User\Application Data\Microsoft\BizTalk Server\Deployment\BindingFiles directory. Destroying these temporary BindingInfo files forces fresh binding files to be generated and solves the above error.