Geeks With Blogs
Neil Thompson BizTalk | .NET | SQL |

BizTalk 2006 seems to have a deployment quirk that has been no small source of frustration for me.  I don't know if this is widespread or if I just have a bad install but it seems that whenever I change a port (add a port or remove a port) I get an error similar to the following when I try to deploy that assembly from Visual Studio,

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 'Orchestration.UpdateRequestStatus,Orchestration, Version=1.0.0.0, Culture=neutral, PublicKeyToken=f96e91b6b75bb727'. Could not enlist orchestration 'Orchestration.UpdateRequestStatus'. All orchestration ports must be bound and the host must be set.

I've done some reading and a lot of thinking and all I can come up with is that BizTalk must be cacheing the binding information and reapplying it when I redeploy the assemblies. The part of it that burns me is that the DEPLOYMENT of the orchestrations fails because of a binding error. If you think about that for a second you realise that you can not change the binding information for assemblies that are not deployed so you get stuck.

I have not been able to find references to the binding cache, though my research is admittedly limited.  On the hunch that this cache exists and is the source of my problem I tried incrementing the version on my orchestration assembly so BizTalk would ignore its previously cached info (its a new assembly version after all) and voila! It deployed my assemblies without complaining.

Two possible solutions to this that i know of are:

  1. Change version (or key I suppose) on the orchestration assemblies
  2. Deploy the orchestration assembly by adding it as a resource to the appropriate app in the biztalk admin tool

 

Posted on Thursday, October 12, 2006 8:39 AM BizTalk Server 2006 | Back to top


Comments on this post: Orchestrations fail to deploy due to binding errors

# re: Orchestrations fail to deploy due to binding errors
Requesting Gravatar...
I had a simlar problem. I changed the Port binding to "Specify Later" and that did work
Left by Antonio Addario on Feb 22, 2007 12:05 AM

# re: Orchestrations fail to deploy due to binding errors
Requesting Gravatar...
I also run into this trouble...
The fastest way to solve it is your option 2, then rebind your orchestrations in VS. After fixing the bindings, deploying from VS works fine again.
Left by Bas de Gier on Apr 18, 2007 9:58 AM

# re: Orchestrations fail to deploy due to binding errors
Requesting Gravatar...


Solution :

1) go to biztalk server 2006 administration console
2) look on resources, rightr click add Biztalk Assemblies
(all missing ones those that are usually automatically
deployed)
3) Go to VS deploy all will work like before, Cheers

:) love this tricky beast
Left by Mohamed Hachem on May 31, 2007 9:59 PM

# re: Orchestrations fail to deploy due to binding errors
Requesting Gravatar...
I have the same problem. I resolved it by setting "redploy=false".

Solution

1. right click on orchestration project
2. choose properties
3. choose deployment on left panel
4. set redeploy=false under general on right panel
Left by wchen on Oct 19, 2007 9:20 AM

# re: Orchestrations fail to deploy due to binding errors
Requesting Gravatar...
Additional info to above.

On deployment the deployment program which is run by Visual Studio creates/updates one or more BindingInfo.xml files in the folder C:\Documents and Settings\[user name]\Application Data\Microsoft\BizTalk Server\Deployment\BindingFiles. There are two versions of this file depending on whether you are deploying to a new application or are redeploying.

If you deploy a new application the file is created based on reflection of the Assembly which contains the orchestration and is prefixed with a ~ (tilda) character.

If you re-deploy an existing application the binding file is created based on the binding info held in the BizTalkMgmt database for the assembly being published. This file does not have the ~ (tilda) prefix.

The deployment process attempts to apply these bindings after (re)deployment.

I have found that by deleting the Binding.Info.Xml files in the temp folder as well as deleting the Application via the BizTalk management console that the above mentioned error no longer occurs because the deployment program always uses a fresh binding.info.xml file based on the assembly and not what was previously in the database. (PS: Note that I am developing on one machine and deploying onto a second machine).
Left by James French on Jan 03, 2008 7:50 AM

# re: Orchestrations fail to deploy due to binding errors
Requesting Gravatar...
Solution by James French worked for me.
Left by shankarpv on Jan 04, 2008 12:13 PM

# re: Orchestrations fail to deploy due to binding errors
Requesting Gravatar...
Change version is right solution
Left by sprinter on Mar 21, 2008 4:03 AM

# re: Orchestrations fail to deploy due to binding errors
Requesting Gravatar...
this worked ... thank you

"I have the same problem. I resolved it by setting "redploy=false".

Solution

1. right click on orchestration project
2. choose properties
3. choose deployment on left panel
4. set redeploy=false under general on right panel "
Left by pavel on Apr 21, 2008 6:06 PM

# MSI fails to install due to binding errors
Requesting Gravatar...
I am getting this error while trying to import an MSI file for the first time from one BT2006 implementation to an entirely different BT2006 implementation. I am tried installing it from explorer which appears to work correctly, but then it notifys that I must now import via Admin... I go to do that and it fails. I then have nothing to look at in Admin and I have to options to select to do anything differently. what could I be doing wrong?

I am assuming this could still be relevant to the current topic due to the error text being the same... apologies if I am incorrect.
Left by Frank Castle on Jul 03, 2008 12:26 PM

# re: Orchestrations fail to deploy due to binding errors
Requesting Gravatar...
I got it working by deleting the application dll binding files from C:\Documents and Settings\[UserName]\Application Data\Microsoft\BizTalk Server\Deployment\BindingFiles
Left by Srikanth Dasari on Sep 05, 2008 12:52 PM

# re: Orchestrations fail to deploy due to binding errors
Requesting Gravatar...
Thanks - solution provided by James French worked for me!! Thanks for this.
Left by Consuelo Sanders on Sep 09, 2008 2:32 PM

# re: Orchestrations fail to deploy due to binding errors
Requesting Gravatar...
Thnaks Dasari, your solution just worked fine.
Left by Basil on Apr 14, 2009 8:56 AM

# re: Orchestrations fail to deploy due to binding errors
Requesting Gravatar...
Check the Project|Properties|Configuration Properties|Deployment|Server value, and make sure that it is set to (LOCAL). This resolved my issue.
Left by Lexi on Oct 20, 2010 11:03 AM

# re: Orchestrations fail to deploy due to binding errors
Requesting Gravatar...
thanks to Dasari. His solution worked fine for me
Left by Virendra Nath Pandey on Feb 18, 2011 8:37 AM

# re: Orchestrations fail to deploy due to binding errors
Requesting Gravatar...
thank you wchen. This worked.
Left by Mike on Mar 13, 2011 12:25 PM

# re: Orchestrations fail to deploy due to binding errors
Requesting Gravatar...
I was getting similar deployment error. My port was referring to a schema from a referenced dll. Once I restarted the Visual Studio this message went away and deployed successfully. Caching it was I guess!
Left by Kakur on May 26, 2011 5:17 PM

# re: Orchestrations fail to deploy due to binding errors
Requesting Gravatar...
I had the same issue. Right click the application in you admin console, then click Configure. In the configure dialog, select the orchestration and then assign a host.
Left by Jay Varma on Dec 05, 2012 5:37 PM

Your comment:
 (will show your gravatar)


Copyright © Neil Thompson | Powered by: GeeksWithBlogs.net