BUG: The BizTalk service may stop responding and you may receive an Event ID 25 error message when messages are processed in BizTalk Server 2004 (897653)



The information in this article applies to:

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

SYMPTOMS

The BizTalk service may stop responding when messages are processed in Microsoft BizTalk Server 2004. This issue occurs when there are multiple receive locations configured to use Microsoft Message Queuing. You may receive an error message in Event Viewer that is similar to the following:Event Type: Error
Event Source: BAM EventBus Service
Event Category: None
Event ID: 25
Description:
Either another TDDS is processing the same data or there is an orphaned session in SQL server holding TDDS lock. Timeout expired.

The timeout period elapsed prior to completion of the operation or the server is not responding. SQLServer: ServerName, Database: BAMPrimaryImport.

CAUSE

This issue occurs when not enough BizTalk Server 2004 worker threads exist.

WORKAROUND

To work around this issue, follow these steps:
  1. Download and then install BizTalk Server 2004 Service Pack 1 (SP1).
  2. Click Start, click Run, type Regedit, and then click OK.
  3. Locate and then click the following registry subkey:

    HKEY_LOCAL_MACHINE\SYSTEM\\CurrentControlSet\Services\BTSSvc{GUID}

  4. Right-click the registry key that you located in step 3, point to New, and then click Key.
  5. Type CLR Hosting, and then press ENTER.
  6. Right-click CLR Hosting, point to New, and then click DWORD Value.
  7. Type MaxWorkerThreads, and then press ENTER.
  8. Right-click MaxWorkerThreads, and then click Modify.
  9. In the Value data box, type a value for an appropriate number of BizTalk Server 2004 worker threads, and then click OK.

    Note The value that you type depends on the number of configured receive locations and the number of messages that are being processed.
  10. Close Registry Editor, and then restart the computer.

STATUS

Microsoft has confirmed that this is a bug in the Microsoft products that are listed in the "Applies to" section.

MORE INFORMATION

For more information about BizTalk Server 2004 SP1, visit the following Microsoft Web site:

Modification Type:MajorLast Reviewed:6/28/2005
Keywords:kbpending kbprb kbBizTalk2004preSP2fix kbbug kbmsccsearch kbpubtypekc KB897653 kbAudDeveloper kbAudITPRO