Mega Search
23.2 Million


Sign Up

Make a donation  
Early bindings deployment error  
News Group: microsoft.public.biztalk.general

Hi

I get this error when I deploy my main project: 

Microsoft.BizTalk.Deployment.DeploymentException] Unable to deploy early 
bindings. [Microsoft.BizTalk.Deployment.Binding.BindingException] Failed 
updating binding information. BindingException: Cannot update send port 
"ProcessPurchaseOrders_1.0.0.0_ProcessPurchaseOrders.ProcessPurchaseOrder_SendPort_OutgoingPO_b54adb969191679c". 
[Microsoft.BizTalk.Deployment.Binding.BindingException] Cannot update send 
port 
"ProcessPurchaseOrders_1.0.0.0_ProcessPurchaseOrders.ProcessPurchaseOrder_SendPort_OutgoingPO_b54adb969191679c". 
[Microsoft.BizTalk.Deployment.Binding.BindingException] Transmit pipeline 
"SLPipelines.FlatFileOutPipe, SLPipelines, Version=1.0.0.0, Culture=neutral, 
PublicKeyToken=7e6a272c71ae5581" not found. 

As you can see I have my pipelines in a separate project and I am using 
dynamic binding on some ports including the one in the error above. I have 
deployed the pipelines project to the GAC, my main project references this 
assembly. I've changed the version number and redeployed the pipeline dll and 
then tried to deploy main project again but same error. Can anyone help?

Any suggestions would be appreciated.

Vote for best question.
Score: 0  # Vote:  0
Date Posted: 7-Oct-2004, at 2:21 AM EST
From: =?Utf-8?B?RGFyZW4=?=
 
Re: Early bindings deployment error  
News Group: microsoft.public.biztalk.general
Did you remove the reference to your old pipeline assembly and add the 
reference to the new pipeline assembly in your project? The project 
references will "reference" the assembly by name and version.

-- 
Jeff Lynch
"A BizTalk Enthusiast"
http://dotnetjunkies.com/WebLog/jlynch/


"Daren"  wrote in message 
news:B1C47D25-70BB-4FD4-BD1F-0512B5C10EDD@microsoft.com...
> Hi
>
> I get this error when I deploy my main project:
>
> Microsoft.BizTalk.Deployment.DeploymentException] Unable to deploy early
> bindings. [Microsoft.BizTalk.Deployment.Binding.BindingException] Failed
> updating binding information. BindingException: Cannot update send port
> "ProcessPurchaseOrders_1.0.0.0_ProcessPurchaseOrders.ProcessPurchaseOrder_SendPort_OutgoingPO_b54adb969191679c".
> [Microsoft.BizTalk.Deployment.Binding.BindingException] Cannot update send
> port
> "ProcessPurchaseOrders_1.0.0.0_ProcessPurchaseOrders.ProcessPurchaseOrder_SendPort_OutgoingPO_b54adb969191679c".
> [Microsoft.BizTalk.Deployment.Binding.BindingException] Transmit pipeline
> "SLPipelines.FlatFileOutPipe, SLPipelines, Version=1.0.0.0, 
> Culture=neutral,
> PublicKeyToken=7e6a272c71ae5581" not found.
>
> As you can see I have my pipelines in a separate project and I am using
> dynamic binding on some ports including the one in the error above. I have
> deployed the pipelines project to the GAC, my main project references this
> assembly. I've changed the version number and redeployed the pipeline dll 
> and
> then tried to deploy main project again but same error. Can anyone help?
>
> Any suggestions would be appreciated. 



Vote for best answer.
Score: 0  # Vote:  0
Date Posted: 7-Oct-2004, at 8:06 AM EST
From: Jeff Lynch
 
Re: Early bindings deployment error  
News Group: microsoft.public.biztalk.general
Hi Jeff - Yes I have removed the old pipeline assembly, redeployed the 
pipelines project with a new version number and updated references, still 
same error - any ideas?


> Did you remove the reference to your old pipeline assembly and add the 
> reference to the new pipeline assembly in your project? The project 
> references will "reference" the assembly by name and version.
> 
> -- 
> Jeff Lynch
> "A BizTalk Enthusiast"
> http://dotnetjunkies.com/WebLog/jlynch/
> 
> 
> "Daren"  wrote in message 
> news:B1C47D25-70BB-4FD4-BD1F-0512B5C10EDD@microsoft.com...
> > Hi
> >
> > I get this error when I deploy my main project:
> >
> > Microsoft.BizTalk.Deployment.DeploymentException] Unable to deploy early
> > bindings. [Microsoft.BizTalk.Deployment.Binding.BindingException] Failed
> > updating binding information. BindingException: Cannot update send port
> > "ProcessPurchaseOrders_1.0.0.0_ProcessPurchaseOrders.ProcessPurchaseOrder_SendPort_OutgoingPO_b54adb969191679c".
> > [Microsoft.BizTalk.Deployment.Binding.BindingException] Cannot update send
> > port
> > "ProcessPurchaseOrders_1.0.0.0_ProcessPurchaseOrders.ProcessPurchaseOrder_SendPort_OutgoingPO_b54adb969191679c".
> > [Microsoft.BizTalk.Deployment.Binding.BindingException] Transmit pipeline
> > "SLPipelines.FlatFileOutPipe, SLPipelines, Version=1.0.0.0, 
> > Culture=neutral,
> > PublicKeyToken=7e6a272c71ae5581" not found.
> >
> > As you can see I have my pipelines in a separate project and I am using
> > dynamic binding on some ports including the one in the error above. I have
> > deployed the pipelines project to the GAC, my main project references this
> > assembly. I've changed the version number and redeployed the pipeline dll 
> > and
> > then tried to deploy main project again but same error. Can anyone help?
> >
> > Any suggestions would be appreciated. 
> 
> 
> 

Vote for best answer.
Score: 0  # Vote:  0
Date Posted: 7-Oct-2004, at 3:33 PM EST
From: =?Utf-8?B?RGFyZW4=?=
 
Re: Early bindings deployment error  
News Group: microsoft.public.biztalk.general
Actually I think I have solved this but I'm not sure quite how......

I undeployed the pipelines project which I was deploying with GACUTIL and 
deployed with BTS Deploy Wiz and for the first time the pipelines became 
available to my physical ports in BTS explorer. At the same time in my orch I 
set all the logical ports with dynamic binding to use standard XML and 
PassThru pipes instead of my custom ones. I was hoping I would be able to set 
these to my custom pipes after deployment - which I can and it works....

"Daren" wrote:

> Hi Jeff - Yes I have removed the old pipeline assembly, redeployed the 
> pipelines project with a new version number and updated references, still 
> same error - any ideas?
> 
> 
> > Did you remove the reference to your old pipeline assembly and add the 
> > reference to the new pipeline assembly in your project? The project 
> > references will "reference" the assembly by name and version.
> > 
> > -- 
> > Jeff Lynch
> > "A BizTalk Enthusiast"
> > http://dotnetjunkies.com/WebLog/jlynch/
> > 
> > 
> > "Daren"  wrote in message 
> > news:B1C47D25-70BB-4FD4-BD1F-0512B5C10EDD@microsoft.com...
> > > Hi
> > >
> > > I get this error when I deploy my main project:
> > >
> > > Microsoft.BizTalk.Deployment.DeploymentException] Unable to deploy early
> > > bindings. [Microsoft.BizTalk.Deployment.Binding.BindingException] Failed
> > > updating binding information. BindingException: Cannot update send port
> > > "ProcessPurchaseOrders_1.0.0.0_ProcessPurchaseOrders.ProcessPurchaseOrder_SendPort_OutgoingPO_b54adb969191679c".
> > > [Microsoft.BizTalk.Deployment.Binding.BindingException] Cannot update send
> > > port
> > > "ProcessPurchaseOrders_1.0.0.0_ProcessPurchaseOrders.ProcessPurchaseOrder_SendPort_OutgoingPO_b54adb969191679c".
> > > [Microsoft.BizTalk.Deployment.Binding.BindingException] Transmit pipeline
> > > "SLPipelines.FlatFileOutPipe, SLPipelines, Version=1.0.0.0, 
> > > Culture=neutral,
> > > PublicKeyToken=7e6a272c71ae5581" not found.
> > >
> > > As you can see I have my pipelines in a separate project and I am using
> > > dynamic binding on some ports including the one in the error above. I have
> > > deployed the pipelines project to the GAC, my main project references this
> > > assembly. I've changed the version number and redeployed the pipeline dll 
> > > and
> > > then tried to deploy main project again but same error. Can anyone help?
> > >
> > > Any suggestions would be appreciated. 
> > 
> > 
> > 

Vote for best answer.
Score: 0  # Vote:  0
Date Posted: 7-Oct-2004, at 3:47 PM EST
From: =?Utf-8?B?RGFyZW4=?=
 
Re: Early bindings deployment error  
News Group: microsoft.public.biztalk.general
Daren wrote:
> Actually I think I have solved this but I'm not sure quite how......
>
> I undeployed the pipelines project which I was deploying with GACUTIL
and
> deployed with BTS Deploy Wiz and for the first time the pipelines
became
> available to my physical ports in BTS explorer. At the same time in
my orch I
> set all the logical ports with dynamic binding to use standard XML
and
> PassThru pipes instead of my custom ones. I was hoping I would be
able to set
> these to my custom pipes after deployment - which I can and it
works....
>
> "Daren" wrote:
>
> > Hi Jeff - Yes I have removed the old pipeline assembly, redeployed
the
> > pipelines project with a new version number and updated references,
still
> > same error - any ideas?
> >
> >
> > > Did you remove the reference to your old pipeline assembly and
add the
> > > reference to the new pipeline assembly in your project? The
project
> > > references will "reference" the assembly by name and version.
> > >
> > > --
> > > Jeff Lynch
> > > "A BizTalk Enthusiast"
> > > http://dotnetjunkies.com/WebLog/jlynch/
> > >
> > >
> > > "Daren"  wrote in message
> > > news:B1C47D25-70BB-4FD4-BD1F-0512B5C10EDD@microsoft.com...
> > > > Hi
> > > >
> > > > I get this error when I deploy my main project:
> > > >
> > > > Microsoft.BizTalk.Deployment.DeploymentException] Unable to
deploy early
> > > > bindings.
[Microsoft.BizTalk.Deployment.Binding.BindingException] Failed
> > > > updating binding information. BindingException: Cannot update
send port
> > > >
"ProcessPurchaseOrders_1.0.0.0_ProcessPurchaseOrders.ProcessPurchaseOrder_SendPort_OutgoingPO_b54adb969191679c".
> > > > [Microsoft.BizTalk.Deployment.Binding.BindingException] Cannot
update send
> > > > port
> > > >
"ProcessPurchaseOrders_1.0.0.0_ProcessPurchaseOrders.ProcessPurchaseOrder_SendPort_OutgoingPO_b54adb969191679c".
> > > > [Microsoft.BizTalk.Deployment.Binding.BindingException]
Transmit pipeline
> > > > "SLPipelines.FlatFileOutPipe, SLPipelines, Version=1.0.0.0,
> > > > Culture=neutral,
> > > > PublicKeyToken=7e6a272c71ae5581" not found.
> > > >
> > > > As you can see I have my pipelines in a separate project and I
am using
> > > > dynamic binding on some ports including the one in the error
above. I have
> > > > deployed the pipelines project to the GAC, my main project
references this
> > > > assembly. I've changed the version number and redeployed the
pipeline dll
> > > > and
> > > > then tried to deploy main project again but same error. Can
anyone help?
> > > >
> > > > Any suggestions would be appreciated. 
> > > 
> > > 
> > >


Vote for best answer.
Score: 0  # Vote:  0
Date Posted: 15-Dec-2004, at 5:31 PM EST
From: Jatt
 
Re: Early bindings deployment error  
News Group: microsoft.public.biztalk.general
Daren wrote:
> Actually I think I have solved this but I'm not sure quite how......
>
> I undeployed the pipelines project which I was deploying with GACUTIL
and
> deployed with BTS Deploy Wiz and for the first time the pipelines
became
> available to my physical ports in BTS explorer. At the same time in
my orch I
> set all the logical ports with dynamic binding to use standard XML
and
> PassThru pipes instead of my custom ones. I was hoping I would be
able to set
> these to my custom pipes after deployment - which I can and it
works....
>
> "Daren" wrote:
>
> > Hi Jeff - Yes I have removed the old pipeline assembly, redeployed
the
> > pipelines project with a new version number and updated references,
still
> > same error - any ideas?
> >
> >
> > > Did you remove the reference to your old pipeline assembly and
add the
> > > reference to the new pipeline assembly in your project? The
project
> > > references will "reference" the assembly by name and version.
> > >
> > > --
> > > Jeff Lynch
> > > "A BizTalk Enthusiast"
> > > http://dotnetjunkies.com/WebLog/jlynch/
> > >
> > >
> > > "Daren"  wrote in message
> > > news:B1C47D25-70BB-4FD4-BD1F-0512B5C10EDD@microsoft.com...
> > > > Hi
> > > >
> > > > I get this error when I deploy my main project:
> > > >
> > > > Microsoft.BizTalk.Deployment.DeploymentException] Unable to
deploy early
> > > > bindings.
[Microsoft.BizTalk.Deployment.Binding.BindingException] Failed
> > > > updating binding information. BindingException: Cannot update
send port
> > > >
"ProcessPurchaseOrders_1.0.0.0_ProcessPurchaseOrders.ProcessPurchaseOrder_SendPort_OutgoingPO_b54adb969191679c".
> > > > [Microsoft.BizTalk.Deployment.Binding.BindingException] Cannot
update send
> > > > port
> > > >
"ProcessPurchaseOrders_1.0.0.0_ProcessPurchaseOrders.ProcessPurchaseOrder_SendPort_OutgoingPO_b54adb969191679c".
> > > > [Microsoft.BizTalk.Deployment.Binding.BindingException]
Transmit pipeline
> > > > "SLPipelines.FlatFileOutPipe, SLPipelines, Version=1.0.0.0,
> > > > Culture=neutral,
> > > > PublicKeyToken=7e6a272c71ae5581" not found.
> > > >
> > > > As you can see I have my pipelines in a separate project and I
am using
> > > > dynamic binding on some ports including the one in the error
above. I have
> > > > deployed the pipelines project to the GAC, my main project
references this
> > > > assembly. I've changed the version number and redeployed the
pipeline dll
> > > > and
> > > > then tried to deploy main project again but same error. Can
anyone help?
> > > >
> > > > Any suggestions would be appreciated. 
> > > 
> > > 
> > >


Vote for best answer.
Score: 0  # Vote:  0
Date Posted: 15-Dec-2004, at 5:31 PM EST
From: Jatt
 
Re: Early bindings deployment error  
News Group: microsoft.public.biztalk.general
Daren,

I get the exact same error when I try to deploy an Orchestration to a
new PC (different from the one on which the development and build was
done) using the MSI installer. I used the BTSInstaller utility that
ships in the SDK to create the MSI installer file.

My custom pipelines are part of the same project that has my schemas.

Did you figure out what the real cause of this problem was/is? Any
ideas of what I can try to resolve it? 

Thanks.


Vote for best answer.
Score: 0  # Vote:  0
Date Posted: 15-Dec-2004, at 5:43 PM EST
From: Jatt