SUMMARY
This article is a listing of article numbers for bugs that
were fixed in BizTalk Server 2002 Service Pack 1 (SP1). Click the Content ID
number that precedes the title of the bug to view the
article.
For additional information about
how to obtain the latest service pack for BizTalk Server 2002, click the
following article number to view the article in the Microsoft Knowledge Base:
815781
INFO: How to Obtain the Latest BizTalk Server 2002 Service Pack
MORE INFORMATION
Service Pack 1
292599 FIX: BizTalk Server May Use All Available System Memory
295613 FIX: Cannot Edit XPath Filters in BizTalk 2002
319290 FIX: HIPAA Properties Lost When You Save Schema in BizTalk Editor
319339 FIX: Some Messages in the Retry Queue Are Not Processed for a Long Time
319448 FIX: Possible Memory Leak with MIME or SMIME Encryption
319450 INFO: BizTalk Priority-Based Message Processing Improvement
320370 FIX: An HTTP Protocol Violation Occurs When BizTalk Server Communicates with an HTTP 1.0 Server
320527 Fix: Orchestration Stops Responding When You Correlate Messages to Existing XLANG Schedules
320635 FIX: Supporting Multiple MBCS Document Submissions in One Interchange::Submit
320994 FIX: BizTalk Fails Under Stress with HIPAA 1.0 and 2.0
321112 FIX: HTTP Receive Function Cannot Handle Chunked Data
321950 Fix: Receive Functions Cannot Recover from SQL Failover
322017 FIX: BizTalk Server Incorrectly Logs the nError Code of 8 in the Document Tracking Database
322054 Use BTF to Handle Different Message Types with the Same Root Node Name
324164 BUG: BizTalk Server May Use the Incorrect Certificate Store After the Installation of Q319448 or Q322017
324437 FIX: DateTime Macro Format Different in BizTalk 2002 and BizTalk 2000
325171 FIX: BizTalk Assumes "MIME-Version" Is the First Header of a MIME-Encoded Message
325401 FIX: Problems with HTTP Transport
325582 FIX: Output Data Overwritten When Input Data Is Larger than Destination Field
326578 FIX: Visual Basic Runtime Error When You Test Data in BizTalk Mapper
326660 BizTalk Server Performance Monitor Counters May Not Reset Correctly
326775 PRB: Error Message: The Parser Cannot Parse the ISA Section of the X12 Document
327036 FIX: Schedules That Have a WHILE Loop May Fail During a Controlled Shutdown
327467 FIX: The Dta_purge_old_records Stored Procedure May Cause Exclusive Table Locking
327525 FIX: Cannot Append to a File Monitored by Another Process
328352 FIX: Hotfix to Turn Off Automatic Envelope Specification Lookup
328638 Error When You Validate an X12 Document Instance in BizTalk Editor
329108 Fix: Cannot Submit a Document That Starts with a NULL Character
329176 FIX: Custom Parser Cannot Gain Access to IInterchange::SubmitSync Parameters
329518 FIX: Retain MIME Content-Type Header in HTTP Body
330121 FIX: The BizTalk Mapper May Not Correctly Serialize a Flat File Document
330584 FIX: HIPAA Accelerator Serializes Fields That Do Not Exist in the Input Document
331076 XLANG Scheduler and the Message Queueing Service Consume 100 Percent of the System CPU
331142 BizTalk
Server Partner Edition may not start after you install a hotfix
810563 "The XML Document Has Failed Validation" error message after you execute the SubmitSync
method two times
810277 Message
correlation fails when you try to use the %server% variable
810828 FIX:
BizTalk Server does not correctly validate an S/MIME-encoded message
811092 BizTalk
Server uses <prop:identity> instead of
<rcpt:deliveryReceipt>
812234 FIX: Queues show incorrect number of items
813205 FIX: BizTalk Server does not preserve white space in XML documents
813320 Text box fields do not accept special characters when layout settings are set to certain languages
814243 FIX: Blank error dialog box when you load Document Tracking interface
815206 MS03-016: Cumulative Patch for Microsoft BizTalk Server
815208 MS03-016: HTTP Receiver Buffer Overflow and DTA SQL Injection Vulnerabilities in Microsoft BizTalk Server 2002
815321 FIX: Pooled interchange component never restores lost connection to the BizTalk document tracking database
815478 Documents are not moved to the suspended queue after a custom pre-processing component failure
816369 FIX: Cannot process binary data by using a C# postprocessor and the BizTalk Adapter or MQSeries 1.0
818137 FIX: BizTalk may return a DTC timeout on non-transactional receive functions
820610 FIX: BizTalk uses incorrect object identifier for digest algorithm on signed messages
821396 FIX: Channel filtering expression is truncated when you view or edit an existing channel
824998 FIX: Documents may be stranded in private MSMQ queues after catastrophic failure
319840 FIX: BizTalk document tracking user interface connection string is not updated correctly