FIX: The BizTalk Server host instance crashes when you use a dynamic WSS send port

Article translations Article translations
Article ID: 978059 - View products that this article applies to.
Expand all | Collapse all

On This Page

SYMPTOMS

Consider the following scenario in Microsoft BizTalk Server 2006 R2 or in Microsoft BizTalk Server 2009:  
  • You have a dynamic Windows SharePoint Services (WSS) send port that is in a BizTalk orchestration.

    Note For more information about how to configure WSS send ports, refer to the "More information" section.
  • You do not set the URI property for the send port. For example, you specify the following in an expression shape that is in the orchestration:
    WSSSend_Port(Microsoft.XLANGs.BaseTypes.Address)="wss://"
  • BizTalk Server tries to process a message by using this orchestration.
In this scenario, the BizTalk Server host instance crashes and restarts continuously. Additionally, the following error is logged in the Application log:
Event Type: Error
Event Source: BizTalk DW Reporting
Event Category: None Event ID: 1000 Description: Faulting application btsntsvc.exe, version 3.6.1404.0, stamp 4674b0a4, faulting module kernel32.dll, version 5.2.3790.4480, stamp 49c51f0a, debug? 0, fault address 0x0000bef7

Note If you use BizTalk Server 2009, the Event Source and Event Category in above events are “BizTalk Server 2009”.

CAUSE

This problem occurs because an exception is not handled by BizTalk Server when the URI property is not specified for the dynamic WSS send port.

RESOLUTION

Hotfix information

Cumulative update information

BizTalk Server 2009

The hotfix that resolves this issue is included in cumulative update package 2 for BizTalk Server 2009.

For more information about how to obtain the cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:

2497794 Cumulative update package 2 for BizTalk Server 2009

A supported hotfix is available from Microsoft. However, this hotfix is intended to correct only the problem that is described in this article. Apply this hotfix only to systems that are experiencing the problem described in this article. This hotfix might receive additional testing. Therefore, if you are not severely affected by this problem, we recommend that you wait for the next software update that contains this hotfix.

If the hotfix is available for download, there is a "Hotfix download available" section at the top of this Knowledge Base article. If this section does not appear, contact Microsoft Customer Service and Support to obtain the hotfix.

Note If additional issues occur or if any troubleshooting is required, you might have to create a separate service request. The usual support costs will apply to additional support questions and issues that do not qualify for this specific hotfix. For a complete list of Microsoft Customer Service and Support telephone numbers or to create a separate service request, visit the following Microsoft Web site:
http://support.microsoft.com/contactus/?ws=support
Note The "Hotfix download available" form displays the languages for which the hotfix is available. If you do not see your language, it is because a hotfix is not available for that language.

Prerequisites

You must have Microsoft BizTalk Server 2006 R2 installed to apply this hotfix.

Restart requirement

You do not have to restart the computer after you apply this hotfix.

Hotfix replacement information

This hotfix does not replace other hotfixes.

File information

The English version of this hotfix has the file attributes (or later file attributes) that are listed in the following table. The dates and times for these files are listed in Coordinated Universal Time (UTC). When you view the file information, it is converted to local time. To find the difference between UTC and local time, use the Time Zone tab in the Date and Time item in Control Panel.
Collapse this tableExpand this table
File nameFile versionFile sizeDateTimePlatform
Microsoft.biztalk.kwtpm.wssadapter.runtime.dll3.6.1555.2145,30422-Dec-200911:51x86

WORKAROUND

To work around this problem, make sure that a URI is appended after "wss://" when you specify the Microsoft.XLANGs.BaseTypes.Address property for the send port.

STATUS

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

MORE INFORMATION

For more information about how to configure a dynamic WSS send port, visit the following Microsoft Developer Network (MSDN) Web site:
http://msdn.microsoft.com/en-us/library/aa559141(BTS.20).aspx
For more information about BizTalk Server hotfixes, click the following article number to view the article in the Microsoft Knowledge Base:
2003907 Information on BizTalk Server hot fixes

Properties

Article ID: 978059 - Last Review: March 18, 2011 - Revision: 3.0
APPLIES TO
  • Microsoft BizTalk Server 2006 R2 Branch Edition
  • Microsoft BizTalk Server 2006 R2 Developer Edition
  • Microsoft BizTalk Server 2006 R2 Enterprise Edition
  • Microsoft BizTalk Server 2006 R2 Standard Edition
  • Microsoft BizTalk Server 2009 Branch
  • Microsoft BizTalk Server 2009 Developer
  • Microsoft BizTalk Server 2009 Enterprise
  • Microsoft BizTalk Server 2009 Standard
Keywords: 
kbexpertiseadvanced kbbtsadapters kbbiztalk2006r2presp2fix kbautohotfix kbsurveynew kbqfe KB978059

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com