Article ID: 900339 - View products that this article applies to.
In Microsoft BizTalk Server 2004, you may experience slow performance when you configure the Health and Activity Tracking (HAT) tool to save all tracked messages for an orchestration.
Additionally, you may receive an error message that is similar to the following:
Typically, this problem occurs when the BizTalkDTADb database is very large.
Exception of type System.OutOfMemory Exception was thrown
Hotfix informationA 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 this specific problem. 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=supportNote 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.
Warning You cannot roll back this hotfix from the BizTalk Server environment. Therefore, make sure that you fully test this hotfix in a test environment before you apply this hotfix to a production environment. Do not try to use Add or Remove Programs to remove this hotfix because this does not roll back the database changes, and leaves the BizTalk Server environment in an inconsistent state.
PrerequisitesYou must have Microsoft BizTalk Server 2004 Service Pack 1 (SP1) installed to apply this hotfix.
Restart requirementYou must restart the computer after you apply this hotfix.
Hotfix replacement informationThis hotfix does not replace any other hotfixes.
File informationThe 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 tool in Control Panel.
Note Because of file dependencies, the most recent hotfix that contains these files may also contain additional files.
Collapse this tableExpand this table
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
This hotfix updates the internal version stamp that is used by BizTalk Server 2004 to identify the version of the database that is used. If you reconfigure BizTalk Server 2004 and the existing BizTalk Server databases are deleted, the internal version stamp reflects a new BizTalk Server 2004 installation. In this case, you may receive an error message that is similar to the following when you run the Microsoft BizTalk Server 2006 Configuration Wizard:
To resolve this problem, reinstall the hotfix that is described in this article.
Procedure 'dtasp_GetServiceInstanceMessages' expects parameter '@uidActivityId', which was not supplied.
For more information, click the following article number to view the article in the Microsoft Knowledge Base:
(http://support.microsoft.com/kb/824684/ )Description of the standard terminology that is used to describe Microsoft software updates
Article ID: 900339 - Last Review: October 9, 2011 - Revision: 3.0