Microsoft KB Archive/884977

= An error message is logged in the event log when you try to enlist a dynamic send port in BizTalk Server 2004 =

Article ID: 884977

Article Last Modified on 3/20/2007

-

APPLIES TO


 * Microsoft BizTalk Server 2004 Enterprise Edition
 * Microsoft BizTalk Server 2004 Developer Edition
 * Microsoft BizTalk Server 2004 Partner Edition
 * Microsoft BizTalk Server 2004 Standard Edition

-





SYMPTOMS
When you try to enlist either a dynamic one-way send port or a dynamic solicit-response send port in Microsoft BizTalk Server 2004, an error that is similar to the following is logged in the event log:

The following stored procedure call failed: &quot; { call [dbo].[]( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)}&quot;. SQL Server returned error string: &quot;The statement has been terminated.;Cannot insert the value NULL into column 'uidSubID', table 'BizTalkMsgBoxDb.dbo.Subscription'; column does not allow nulls. INSERT fails.

Note Only dynamic send ports experience this problem.



CAUSE
This problem occurs when you register the BizTalk Server Message Queuing Adapter (MSMQT) after the dynamic send port is created.



WORKAROUND
To work around this problem, follow these steps:
 * 1) Remove either the dynamic one-way port or the dynamic solicit-response port that was created before the MSMQT was registered.
 * 2) Re-create the dynamic one-way port or the dynamic solicit-response port.

Note When you enlist the dynamic send port, the enlistment is now successful.



STATUS
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the &quot;Applies to&quot; section.



Steps to reproduce the behavior

 * 1) Before you register the MSMQT adapter, add either a dynamic one-way send port or a dynamic solicit-response send port.
 * 2) Enlist and then start the dynamic send port. Notice that no error is reported in the event log.
 * 3) Stop and then unenlist the dynamic send port.
 * 4) Register the MSMQT adapter in BizTalk Server Administration.
 * 5) Enlist the dynamic send port. The error message is reported in the event log.

