Battling with BizTalk

MSI Import - Phantom Binding

Had an error today when attempting to import a BizTalk MSI through the Admin Console. It was complaining that a particular adapter had not been configured to work with a particular host. Indeed this was true, however what puzzled me was that there was no refernce to this host in the binding file which had been added to the MSI.
 
After a fair amount of head scratching I tracked back to the orchestration that contained the logical port which matched to the physical port (SOAP) that was mentioned in the error message. It seems that the problem was caused by the fact that the binding on the logical port had been inadvertently set to 'Specify Now'. It seems that this cause a physical port to be created - which in turn was bound to an endpoint not present on the server to which I was ultimately deploying.
 
To resolve this I deleted I changed the binding of the logical orchestration to 'Specify Later' and deleted the 'auto-created' physical port before re-deploying to the build server the exporting the MSI ready for import to the test server.

Feedback

No comments posted yet.