FIX: You receive an error message when you use the WMI MSBTS_DeploymentService API to deploy large assemblies in BizTalk Server 2004 (838977)

SYMPTOMS

In Microsoft BizTalk Server 2004, when you use the Microsoft Windows Management Instrumentation (WMI) classes MSBTS_DeploymentService API to deploy large assemblies in BizTalk Server 2004, you may receive an error message that is similar to the following:

15:50:58: BizTalk 2004 Configuration Server 'MSTEST04', Database 'BizTalkMgmtDb'
15:50:58: Deploying BizTalk 2004 assembly 'assembly file name'...
15:51:03: Exception when processing a BizTalk 2004 action. Stack trace:
System.Runtime.InteropServices.COMException (0x80004005):
Unspecified exception:
External component has thrown an exception.

Note In this sample error message, assembly file name is a placeholder for the name of the affected assembly file.

RESOLUTION

Service pack information

To resolve this problem, obtain the latest service pack for Microsoft BizTalk Server 2004. For more information, click the following article number to view the article in the Microsoft Knowledge Base:

888751 How to obtain the latest BizTalk Server 2004 service pack

Hotfix 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 tool in Control Panel.

   Date         Time   Version     Size     File name
   ----------------------------------------------------------
   13-Mar-2004  01:31  3.0.5256.0  356,864  Btsmetadataom.dll

Note Because of file dependencies, the most recent hotfix that contains this file may also contain additional files.

MORE INFORMATION

For additional information about the terminology that is used to describe Microsoft product updates, click the following article number to view the article in the Microsoft Knowledge Base: