Microsoft KB Archive Search

Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

  1. Home
  2. FIX: BizTalk Document Tracking may stop working after you install cumulative update package 1 for BizTalk Server

FIX: BizTalk Document Tracking may stop working after you install cumulative update package 1 for BizTalk Server

View products that this article applies to.

Symptoms

After you install cumulative update package 1 for Microsoft BizTalk 2009 or Microsoft BizTalk 2010 on a computer, BizTalk Document Tracking may stop working. Additionally, an error message that resembles the following is logged in the Application log:
Event Type: Error
Event Source: BAM EventBus Service
Event Category: None
Event ID: 6
Description:
Execute event error. Error(s) occurred while executing events, see TDDS_FailedTrackingData table for more details. SQLServer: <SQL Server>, Database: BizTalkDTADb.

The TDDS_FailedTackingData table contain the following entries:

TDDS failed to execute event. Stored Procedure dtasp_ServiceInsert failed to run.Stored Procedure dtasp_ServiceInsert Parameter Count and IPersistQueryable Item count not the same, Expected Count: 0, IPersistQueryable Count: 14.

TDDS failed to execute event. Stored Procedure dtasp_MsgIn failed to run.Stored Procedure dtasp_MsgIn Parameter Count and IPersistQueryable Item count not the same, Expected Count: 0, IPersistQueryable Count: 14.

TDDS failed to execute event. Stored Procedure dtasp_MsgOut failed to run.Stored Procedure dtasp_MsgOut Parameter Count and IPersistQueryable Item count not the same, Expected Count: 0, IPersistQueryable Count: 14.

Additionally, the TDDS_FailedTrackingData table may grow very large in the BizTalkDTADb database.

↑ Back to the top

Cause

This issue occurs because the BizTalk Application Users group loses the execute permissions for the following stored procedures after you install cumulative update package 1 for Microsoft BizTalk 2009:
  • [dbo].[dtasp_MsgIn]
  • [dbo].[dtasp_MsgOut]
  • [dbo].[dtasp_ServiceInsert]

↑ Back to the top

Resolution

Cumulative update information
 

BizTalk Server 2010

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:
2497789 Cumulative update package 1 for BizTalk 2010

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

↑ Back to the top

Workaround

To work around this issue, follow these steps in BizTalk Administration Console:
  1. Click to select the Allow Host Tracking check box in another BizTalk Server host, and then click to clear this option in the current tracking host.
  2. Restart BizTalk Server host instances.
  3. Click to select the Allow Host Tracking check box in the original tracking host, and then click to clear this option in the other tracking host.
  4. Restart the host instances to correctly apply the permissions.

↑ Back to the top

Status

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

↑ Back to the top

More Information

For more information about BizTalk Server hotfixes, click the following article number to view the article in the Microsoft Knowledge Base:

2003907 Information about BizTalk Server hotfixes

↑ Back to the top

Keywords: kb, kbqfe, kbexpertiseadvanced, kbsurveynew, kbfix, kbhotfixdev, kbbiztalk2009presp1fix, kbbtsbam

↑ Back to the top

Article Info
Article ID : 2508913
Revision : 2
Created on : 9/10/2018
Published on : 9/11/2018
Exists online : False
Views : 501