Symptoms
When you use a sequential convoy and a filter on a receive shape in a Microsoft BizTalk Server 2013 orchestration, and the receive shape activates the orchestration, the orchestration is suspended, the implementation of the sequential convoy fails, and you receive the following error message:
Uncaught exception (see the 'inner exception' below) has suspended an instance of service ‘ServiceInstanceName'.The service instance will remain suspended until administratively resumed or terminated.If resumed the instance will continue from its last persisted state and may re-throw the same unexpected exception.InstanceId: InstanceIDShape name: ShapeNameShapeId: ShapeIDException thrown from: segment 2, progress 4Inner exception: Exception occurred when persisting state to the database.Exception type: PersistenceExceptionSource: Microsoft.XLANGs.BizTalk.EngineTarget Site: Void Commit()
Additionally, the following "BizTalk Server"Â entry is logged in the Application log:
The following stored procedure call failed: " { call [dbo].[bts_AddConvoySetInstance]( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)}". SQL Server returned error string: "The statement has been terminated.;Cannot insert the value NULL into column '<column name>', table '<table name>'; column does not allow nulls. INSERT fails.".
Resolution
Cumulative update information
This issue was first fixed in the following cumulative update of BizTalk Server:
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
References
For information about the service packs and cumulative update list for BizTalk Server, see KB 2555976: Service pack and cumulative update list for BizTalk Server.For more information about BizTalk Server hotfixes, see KB 2003907: Information about BizTalk hotfixes and cumulative update support.
