BUG: You cannot enlist a dynamic send port in BizTalk Server 2004 (913021)


The information in this article applies to:

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

SYMPTOMS

You cannot enlist a dynamic send port in Microsoft BizTalk Server 2004. You may receive an error message that is similar to the following:
Could not enlist Send Port 'portname'
Notes
  • In this error message, portname is a placeholder for the name of the dynamic send port.
  • You may receive this error message for dynamic one-way ports and for solicit-response ports.
When you click Details, you receive an error message that is similar to the following:
A database failure occurred due to an unexpected failure.
Additionally, an event that is similar to the following may be logged in the Application log:The following stored procedure call failed: " { call [dbo].[]( ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)}". SQL Server returned error string: "The statement has been terminated.;Cannot insert the value NULL into column 'uidSubID', table 'BizTalkMsgBoxDb.dbo.Subscription'; column does not allow nulls. INSERT fails

CAUSE

This problem occurs if you try to enlist an existing dynamic send port after you install the BizTalk Message Queuing adapter (MSMQT).

WORKAROUND

To work around this problem, delete the existing dynamic send port, and then re-create the dynamic send port.

Note To re-create the dynamic send port, you can use the BizTalk Explorer Object Model, Microsoft Windows Management Instrumentation (WMI), BizTalk Explorer, or import bindings.

STATUS

Microsoft has confirmed that this is a bug in the Microsoft products that are listed in the "Applies to" section.
Modification Type:MajorLast Reviewed:2/3/2006
Keywords:kbprb kbBTS kbtshoot kbnofix kbBug KB913021 kbAudDeveloper
©2004 Microsoft Corporation. All rights reserved.