| Charles Young 2004-03-11, 10:42 pm |
| I found a workaround by simply making a temporary change
to the definition of the BizTalkMsgBoxDb.dbo.TrackingData
table (which was empty) to allow null values on the
strDBServer field. I could then happily unenlist,
undeploy and re-deploy a new version of the
orchestration. The orchestration instances disappeared
from HAT, as well!
Is this a bug? Should we all amend the schema for this
table permanently?
>-----Original Message-----
>I'm using the release version of BizTalk 2004 and have
>run into a problem. While testing an orchestration it
>failed due to a straightforward problem with one of my
>schemas. The orchestration was suspended in the normal
>way. However, I cannot now unenlist and undeploy the
>orchestration, or re-deploy the fixed version. Each
>time I attempt to unenlist, I get an error in the event
>log saying:
>
>The following stored procedure call failed: " { call
>[dbo].
>
& #91;bts_AdminPreemptAndGetInstances_BizT
alkServerApplication]
>( ?, ?, ?)}". SQL Server returned error string: "The
>statement has been terminated.;Cannot insert the value
>NULL into column 'strDBServer',
>table 'BizTalkMsgBoxDb.dbo.TrackingData'; column does
not
>allow nulls. INSERT fails.".
>
>I can terminate suspended orchestrations from with HAT,
>which reports that :
>
>"One or more service instances could not be terminated.
>It is possible that the instance(s) has already
completed
>or terminated, or it may have a pending control message."
>
>I ran into much the same problem a couple of weeks ago
on
>a different build. Has anyone else experienced this,
or
>have any idea of a solution?
>
>.
>
|