BizTalk Server Orchestration - Serious bug in undeploy?

Author

Serious bug in undeploy?

Brian Taylor

2004-04-18, 10:53 am

I have a problem with an orchestration undeployment.

1. Basically the orchestration is receive, create (new) message, send.
However the create message used the wrong namespace causing the process to
be suspended.
2. Then I changed the orchestration to just receive. I terminated the
suspended messages (with HAT), unenlisted, undeployed, deployed and enlisted
the orchestration.

However it fails with the message below. Why is it still trying to send a
message when there is no send action in the orchestration? Is it a problem
with a rehydrated orchestration. When the orchestration is view in the
debugger it shows the receive diagram and steps and then a number of blank
steps which were obviously the old send actions. How can I clear these out?
Note that in the project configuration properties I set the "redeploy"
deployment option to true (it defaults to false).

Note that this problem seems to occur regardless of the reason why the
orchestration is suspended. For example I deleted a reference to a library
function and this caused the same problem to occur.

bt
Uncaught exception terminated service
Logos.Function.RoomStatus.RoomTemperature(96891ed4-f584-5e86-c313-4162f68558
de), instance 1f18ad3f-a6b0-493f-81ea-9290e019917f

Failed while attempting to send message 'TemperatureOut'.

Exception type: SendFailedException

Source: Microsoft.XLANGs.BizTalk.Engine

Target Site: Void
WriteMessageState(Microsoft.BizTalk.Interop.IBTPEPInfoLookup, System.Guid,
Microsoft.XLANGs.BaseTypes.XLANGMessage, Microsoft.XLANGs.Core.Segment,
System.String, System.String, System.Collections.IList, Boolean,
System.Collections.IList)

Help Link:

Additional error information:

Exception from HRESULT: 0xC0C01672.

Exception type: COMException

Source: Microsoft.XLANGs.BizTalk.Engine

Target Site: Void PostToSendPort(System.Guid ByRef,
Microsoft.BizTalk.Agent.Interop.IBTMessageBatch,
Microsoft.BizTalk.Agent.Interop.IBTMessage, System.String, System.String,
Microsoft.BizTalk.Interop.IBTMMessageList ByRef)

Help Link:

Brian Taylor

2004-04-18, 10:53 am

I think I found the problem.
Every time a change is made to an orchestration and redeployed the version
number needs to be increased.
Is there anyway way of doing this automatically on a build?
bt

"Brian Taylor" <brian1taylor@hotmail.com> wrote in message
news:OrJ$X6OJEHA.1620@TK2MSFTNGP10.phx.gbl...
> I have a problem with an orchestration undeployment.
>
> 1. Basically the orchestration is receive, create (new) message, send.
> However the create message used the wrong namespace causing the process to
> be suspended.
> 2. Then I changed the orchestration to just receive. I terminated the
> suspended messages (with HAT), unenlisted, undeployed, deployed and
enlisted
> the orchestration.
>
> However it fails with the message below. Why is it still trying to send a
> message when there is no send action in the orchestration? Is it a problem
> with a rehydrated orchestration. When the orchestration is view in the
> debugger it shows the receive diagram and steps and then a number of blank
> steps which were obviously the old send actions. How can I clear these
out?
> Note that in the project configuration properties I set the "redeploy"
> deployment option to true (it defaults to false).
>
> Note that this problem seems to occur regardless of the reason why the
> orchestration is suspended. For example I deleted a reference to a library
> function and this caused the same problem to occur.
>
> bt
> Uncaught exception terminated service
>
Logos.Function.RoomStatus.RoomTemperature(96891ed4-f584-5e86-c313-4162f68558
> de), instance 1f18ad3f-a6b0-493f-81ea-9290e019917f
>
> Failed while attempting to send message 'TemperatureOut'.
>
>
> Exception type: SendFailedException
>
> Source: Microsoft.XLANGs.BizTalk.Engine
>
> Target Site: Void
> WriteMessageState(Microsoft.BizTalk.Interop.IBTPEPInfoLookup, System.Guid,
> Microsoft.XLANGs.BaseTypes.XLANGMessage, Microsoft.XLANGs.Core.Segment,
> System.String, System.String, System.Collections.IList, Boolean,
> System.Collections.IList)
>
> Help Link:
>
> Additional error information:
>
> Exception from HRESULT: 0xC0C01672.
>
>
> Exception type: COMException
>
> Source: Microsoft.XLANGs.BizTalk.Engine
>
> Target Site: Void PostToSendPort(System.Guid ByRef,
> Microsoft.BizTalk.Agent.Interop.IBTMessageBatch,
> Microsoft.BizTalk.Agent.Interop.IBTMessage, System.String, System.String,
> Microsoft.BizTalk.Interop.IBTMMessageList ByRef)
>
> Help Link:
>
>

Brian Taylor

2004-04-18, 10:53 am

Shankar Stanam[MSFT]

2004-06-29, 5:51 pm

You should probablu use the version attribute and specify a specific
version as oppsed to using the generated version number every time you
build. Try using 1.0.0.0 as the version number in the project properties
and update it when you have a major change
This posting is provided "AS IS" with no warranties, and confers no rights.

EBusiness Server Team

Rohith

2004-07-01, 11:05 am

i got this problem many times.....intialy i used to change version number every time!!

i feel better way is stop u r biztalk service once and restart before rebuld/Deploy Assemblem...i a sure this is the best way rather then every time changing version numbers!!!

CR-

quote:
Originally posted by Shankar Stanam[MSFT]
You should probablu use the version attribute and specify a specific
version as oppsed to using the generated version number every time you
build. Try using 1.0.0.0 as the version number in the project properties
and update it when you have a major change
This posting is provided "AS IS" with no warranties, and confers no rights.

EBusiness Server Team

sarbillgates

2006-01-26, 5:02 pm

Yes Brain, it is a bug in the Undeployment wizard as well as in the BizTalk Server explorer undeployment. I used BTSDeploye.exe for uninstalling, it was working fine. You no need to change the version number for you assembly.