Microsoft has released an Update Rollup Package for
Microsoft BizTalk Server 2004 that corrects the following problems:
The Microsoft BizTalk Message Queuing Adapter may not send acknowledgment responses after
many hours of stress. The BizTalk Message Queuing Adapter (MSMQT) may not send acknowledgment (ACK) responses back to its clients after several hours of
The MSMQT may experience a memory leak and may create orphaned records
in the Message Box database when the MSMQT processes large messages. The MSMQT may experience a memory leak and may create orphaned records in the Message Box
database when the MSMQT processes messages that are larger than 100 kilobytes (KB).
Orchestrations may not dehydrate as expected. Under certain circumstances,
orchestrations that are running become dehydrated and will not rehydrate as
You cannot save a message in Health and Activity Tracking if the message is in a
suspended state. If you receive messages from an adapter that is configured to run in a different process than
the BizTalk Server application, and if you turned on the Message Body Tracking option,
you cannot save messages that are received by this adapter if the Health and Activity Tracking (HAT) interface has marked the messages as
suspended (not resumable).
The SQL Adapter generates a System.OutOfMemoryException error when it polls a large-sized message. The SQL Adapter may
generate a System.OutOfMemoryException error when it receives a file that is larger than
10 megabytes (MB).
The SEED does not deploy a package that contains
dependent assemblies. The Spoke Side SEED Wizard
does not deploy a BizTalk project that contains an orchestration and its dependent
An empty tracking stream is inserted into the tracking database even when
global tracking is disabled. Even when the GlobalTrackingOption property
is disabled, a call is made to the bts_InsertTracking stored procedure. This
procedure call causes an empty tracking stream to be inserted in the TrackingData table.
The GlobalTrackingOption property is a property of the MSBTS_GroupSetting WMI class. The MSBTS_GroupSetting WMI class represents a logical grouping of computers that are running Microsoft BizTalk Server. This property can be modified with the Windows Management Instrumentation Tester tool. To do this, follow these steps:
Click Start, click Run, type wbemtest, and then click OK.
In the Windows Management Instrumentation Tester, click Connect.
In the Namespace box, type root\MicrosoftBizTalkServer, and then click Connect.
Click Open Class, type MSBTS_GroupSetting in the Enter Target Class Name box, and then click OK.
In the Properties list, click GlobalTrackingOption, and then click Edit Property.
To disable the Global Tracking option for the BizTalk Group, change the Value that is listed from 1 (0x1) to 0 (0x0), and then click Save Property.
To enable the Global Tracking option for the BizTalk Group, change the Value that is listed from 0 (0x0) to 1 (0x1), and then click Save Property.
To close the Windows Management Instrumentation Tester tool, click Close in the Object Editor for MSBTS_GroupSetting dialog box, and then click Exit in the Windows Management Instrumentation Tester dialog box.
The %datetime_bts2000% symbol incorrectly generates the UTC date and time in the BizTalk Server 2002 format. The
%datetime_bts2000% symbol generates the UTC date and time in the
format that is used by Microsoft BizTalk Server 2002 (YYYYMMDDThhmmsss). The
%datetime_bts2000% symbol should generate the UTC date and time in
the format YYYYMMDDhhmmsss. This format is used by Microsoft BizTalk Server 2000.
A race condition that generates
errors may occur if you run schedules by using
parallelism on multiple processor computers. If you run an
orchestration that contains parallel paths of execution on a multiple processor
computer, a race condition may occur that may generate errors.
An incorrectly handled orchestration
engine exception may cause orchestration instances to enter an infinite
dehydration/rehydration loop. If you shut down and
then restart the BizTalk host for running orchestrations, these orchestrations may
enter an infinite dehydration/rehydration loop. This problem may occur if the
orchestrations implement transactions.
An orchestration may generate
a PersistenceException error when BizTalk Server sends out messages through a parallel construct. An orchestration may
generate a PersistenceException error if BizTalk Server sends messages through a parallel
contruct that is configured in a long-running transaction scope.
The BizTalk Framework schema validation fails when it
processes documents that are received from BizTalk Server 2002. BizTalk Framework-compliant documents fail schema validation and an error
is generated if the documents were sent from BizTalk Server 2002 and if the documents are processed by using the BizTalk
Framework disassembler pipeline component. This error occurs because the BizTalk Framework disassembler
pipeline component uses a different namespace than the namespace that is used by BizTalk Framework-compliant documents from BizTalk Server 2002.
You receive a "The constructor to deserialize an object of type
Microsoft.BizTalk.Component.Interop.DocumentSpecException was not found" error
message when BizTalk Server generates a DocumentSpecException error. When BizTalk Server tries to
generate a DocumentSpecException error, BizTalk Server cannot generate the exception error, and you receive the following error message:
constructor to deserialize an object of type
Microsoft.BizTalk.Component.Interop.DocumentSpecException was not
This problem occurs because the DocumentSpecException class is
missing a default constructor.
If you change the value of the the Timeout property of the Scope shape of the orchestration, you receive an
"Unknown exception" error message when you compile the orchestration. If you change the value of the Timeout property of the Scope shape of the orchestration, an internal state may not be
reinitialized correctly. This behavior generates an "Unknown exception" error message when you compile the orchestration.
The English version of this software update has the file attributes (or later) 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.