Select the product you need help with

FIX: Error message when you use an SQL adapter in BizTalk Server 2006 R2 SP1 or in BizTalk Server 2009

Article ID: 983185 - View products that this article applies to.

Hotfix Download Available

Expand all | Collapse all

SYMPTOMS

Consider the following scenario:

You have a computer that is running Microsoft BizTalk Server 2006 R2 Service Pack 1 (SP1) or Microsoft BizTalk Server 2009.
You have a send port that uses the SQL adapter as the transport type property and that uses "PassThruTransmit" as the send pipeline property.
You have a BizTalk application that uses the send port.
You create and then deploy a Business Activity Monitoring (BAM) activity for the BizTalk application.
In Tracking Profile Editor (TPE), you create and deploy a tracking profile that is based on the BAM activity definition.

In this scenario, the send port stops working. Then, BAM tracking does not work for the messages that arrive at the send port. Additionally, two events that resemble the following are logged in the application log.

Event 1

Event Type: Warning
Event Source: BizTalk Server 2006
Event Category: BizTalk Server 2006
Event ID: 5740
Description:
The adapter "SQL" raised an error message. Details "Unable to cast COM object of type 'System.__ComObject' to interface type 'Microsoft.BizTalk.PipelineOM.IInterceptor'. This operation failed because the QueryInterface call on the COM component for the interface with IID '{24394515-91A3-4CF7-96A6-0891C6FB1360}' failed due to the following error: Interface not registered (Exception from HRESULT: 0x80040155)."

Event 2

Event Type: Error
Event Source: BizTalk Server 2006
Event Category: BizTalk Server 2006
Event ID: 5754
Description:
A message sent to adapter "SQL" on send port "SQLBAMTrackedPassThruSendPort" with URI "SQL://<URI>" is suspended. Error details: Unable to cast COM object of type 'System.__ComObject' to interface type 'Microsoft.BizTalk.PipelineOM.IInterceptor'. This operation failed because the QueryInterface call on the COM component for the interface with IID '{24394515-91A3-4CF7-96A6-0891C6FB1360}' failed due to the following error: Interface not registered (Exception from HRESULT: 0x80040155). MessageId: {<Messge ID>} InstanceID: {<Instance ID>}

Note The issue does not occur when you enable BAM tracking on the same send port in BizTalk Server 2006 R2. If you use BizTalk Server 2009, the Event Source and Event Category in above events are “BizTalk Server 2009”.

Back to the top | Give Feedback

CAUSE

This issue occurs because the BAM interceptor interface is registered incorrectly. The SQL adapter is a .NET Framework serviced component and a COM+ service. When BAM tracking is enabled, this COM+ service accesses the BAM Interceptor interface. Because of this behavior, the COM+ marshaling fails and the send adapter stops working.

Back to the top | Give Feedback

RESOLUTION

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

(http://vkbexternal.partners.extranet.microsoft.com/VKBWebService/ViewContent.aspx?scid=KB;EN-US;2497794)

Cumulative update package 2 for BizTalk Server 2009

Hotfix information

The hotfix that resolves this problem is included in cumulative update package 2 for BizTalk Server 2006 R2 Service Pack 1. 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:

2211420

(http://support.microsoft.com/kb/2211420/ )

Cumulative update package 2 for BizTalk Server 2006 R2 Service Pack 1

Back to the top | Give Feedback