subscribe to the RSS Feed

Friday, March 12, 2010

BizTalk Server 2004: FIX: The TrackedMessages_Copy_BizTalkMsgBoxDb SQL Server Agent job fails

By TechSupport


SUPPORT PROBLEM: FIX: The TrackedMessages_Copy_BizTalkMsgBoxDb SQL Server Agent job fails

Applications Supported:

COPYRIGHT NOTICE: (c) 2007 Microsoft Corporation. All rights reserved.

SUPPORT SOLUTION:
On a server that is running Microsoft BizTalk Server 2004, BizTalk Server 2006, or BizTalk 2006 R2, the TrackedMessages_Copy_BizTalkMsgBoxDb SQL Server Agent job does not run. When this occurs, an error message that resembles the following is logged in the SQL Server Agent job log:

Server Server_name
Job Name TrackedMessages_Copy_BizTalkMsgBoxDb
Step Name Purge
Duration Duration_time
Sql Severity Severity
Sql Message ID Message_ID
Operator Emailed
Operator Net sent
Operator Paged
Retries Attempted 0

Message
Executed as user: User_name. … hint is used.
[SQLSTATE 01000] (Message message_ID) Transaction (Process ID process_ID) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction.

.This problem occurs because of an error in a stored procedure that is contained in the TrackedMessages_Copy_BizTalkMsgBoxDb SQL Server Agent job..Hotfix information
2, ‘resolution’);
For Microsoft BizTalk Server 2006 R2

3, ‘resolution’);
To resolve this problem, apply the hotfix package that is described in the following Microsoft Knowledge Base article:
967931 

(http://support.microsoft.com/kb/967931/
)
FIX: Unused subscription predicates are not purged from the NotEqualsPredicates table of the BizTalkMsgBoxDB database in BizTalk Server 2006 and in BizTalk 2006 R2

For Microsoft BizTalk Server 2006
3, ‘resolution’);
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next Microsoft BizTalk Server 2004 service pack that contains this hotfix.To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:http://support.microsoft.com/default.aspx?scid=fh;[LN];CNTACTMS
(http://support.microsoft.com/default.aspx?scid=fh;%5Bln%5D;cntactms)
Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.Prerequisites
3, ‘resolution’);
There are no prerequisites for installing this hotfix package.Restart requirement
3, ‘resolution’);
You do not have to restart the computer after you apply this hotfix package.Hotfix replacement information
3, ‘resolution’);
This hotfix does not replace a previously released hotfix package.File information
3, ‘resolution’);
The English (United States) version of this hotfix package uses a Microsoft Windows Installer package to install the hotfix package. The dates and the times for these files are listed in Coordinated Universal Time (UTC) in the following table. When you view the file information, the date 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 tableFile nameFile versionFile sizeDateTimePlatformMsgboxlogic.sqlNot applicable542,75011-Apr-200813:21Not applicableNote Because of file dependencies, the most recent hotfix that contains these files may also contain additional files.For Microsoft BizTalk Server 2004
3, ‘resolution’);
A supported hotfix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Only apply it to systems that are experiencing this specific problem. This hotfix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next Microsoft BizTalk Server 2004 service pack that contains this hotfix.To resolve this problem immediately, contact Microsoft Product Support Services to obtain the hotfix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:http://support.microsoft.com/default.aspx?scid=fh;[LN];CNTACTMS
(http://support.microsoft.com/default.aspx?scid=fh;%5Bln%5D;cntactms)
Note In special cases, charges that are ordinarily incurred for support calls may be canceled if a Microsoft Support Professional determines that a specific update will resolve your problem. The usual support costs will apply to additional support questions and issues that do not qualify for the specific update in question.Prerequisites
3, ‘resolution’);
There are no prerequisites.Restart requirement
3, ‘resolution’);
You do not have to restart the computer after you apply this hotfix package.Hotfix replacement information
3, ‘resolution’);
This hotfix does not replace a previously released hotfix package.File information
3, ‘resolution’);
The English (United States) version of this hotfix package uses a Microsoft Windows Installer package to install the hotfix package. The dates and the times for these files are listed in Coordinated Universal Time (UTC) in the following table. When you view the file information, the date 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 tableFile nameFile versionFile sizeDateTimePlatform Msgboxlogic.sqlNot applicable351,09225-Nov-200818:18Not applicableNote Because of file dependencies, the most recent hotfix that contains these files may also contain additional files..Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the “Applies to” section of this article..For more information about database structure and jobs, visit the following Microsoft Developer Network (MSDN) Web site:
http://msdn.microsoft.com/en-us/library/aa561960%28BTS.20%29.aspx
(http://msdn.microsoft.com/en-us/library/aa561960%28BTS.20%29.aspx)
For more information about viewing tracked message and instance data, visit the following MSDN Web site:

http://msdn.microsoft.com/en-us/library/aa561587%28BTS.10%29.aspx
(http://msdn.microsoft.com/en-us/library/aa561587%28BTS.10%29.aspx)

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

919776 

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

Description of the SQL Server Agent jobs in BizTalk Server

For more information about how to maintain and troubleshoot BizTalk Server databases, click the following article number to view the article in the Microsoft Knowledge Base:

952555 

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

How to maintain and troubleshoot BizTalk Server databases

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

824684 

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

Description of the standard terminology that is used to describe Microsoft software updates

.

For File Repair and Data Recovery, visit File Repair / Data Recovery