PSS ID Number: 326845
Article Last Modified on 9/29/2003
The information in this article applies to:
- Microsoft BizTalk Server 2002
- Microsoft BizTalk Server Accelerator for HIPAA 1.0
This article was previously published under Q326845
SUMMARY
The Microsoft BizTalk Server Rollup corrects the problems that are described in the following Microsoft Knowledge Base articles:
321112 FIX: HTTP Receive Function Cannot Handle Chunked Data
319448 FIX: Possible Memory Leak with MIME or SMIME Encryption
292599 FIX: BizTalk Server May Use All Available System Memory
325171 FIX: BizTalk Assumes 'MIME-Version' Is the First Header of a MIME-Encoded Message
321950 Fix: Receive Functions Cannot Recover from SQL Failover
319450 INFO: BizTalk Priority-Based Message Processing Improvement
325582 FIX: Output Data Overwritten When Input Data Is Larger than Destination Field
325401 FIX: Problems with HTTP Transport
324437 FIX: DateTime Macro Format Different in BizTalk 2002 and BizTalk 2000
322054 Use BTF to Handle Different Message Types with the Same Root Node Name
320994 FIX: BizTalk Fails Under Stress with HIPAA 1.0 and 2.0
322017 FIX: BizTalk Server Incorrectly Logs the nError Code of 8 in the Document Tracking Database
324164 BUG: BizTalk Server May Use the Incorrect Certificate Store After the Installation of Q319448 or Q322017
MORE INFORMATION
A supported fix is now available from Microsoft, but it is only intended to correct the problem that is described in this article. Apply it only to computers that are experiencing this specific problem. This fix may receive additional testing. Therefore, if you are not severely affected by this problem, Microsoft recommends that you wait for the next BizTalk Server 2002 Service Pack that contains this fix.
To resolve this problem immediately, contact Microsoft Product Support Services to obtain the fix. For a complete list of Microsoft Product Support Services phone numbers and information about support costs, visit the following Microsoft Web site:
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 typical support costs will apply to additional support questions and issues that do not qualify for the specific update in question.
Date Time Version Size File name
----------------------------------------------------------------------
23-Jul-2002 18:09 3.0.1530.0 172,304 Biztalkhttpreceive.dll
23-Jul-2002 18:09 3.0.1530.0 53,520 Btsshim.dll
23-Jul-2002 18:08 3.0.1530.0 24,848 Btstrace.dll
23-Jul-2002 18:08 3.0.1530.0 131,344 Cisapi.dll
23-Jul-2002 18:09 3.0.1530.0 524,560 Ciscore.dll
23-Jul-2002 18:08 3.0.1530.0 86,288 Cisdav.dll
23-Jul-2002 18:09 3.0.1530.0 250,128 Cisdta.dll
23-Jul-2002 18:09 3.0.1530.0 405,776 Cisengine.dll
23-Jul-2002 18:08 3.0.1530.0 61,712 Ciserrlog.dll
23-Jul-2002 18:08 3.0.1530.0 172,304 Cismsg.dll
23-Jul-2002 18:09 3.0.1530.0 712,976 Cisparser.dll
23-Jul-2002 18:08 3.0.1530.0 20,752 Cisperf.dll
23-Jul-2002 18:09 3.0.1530.0 471,312 Cisserializer.dll
23-Jul-2002 18:08 3.0.1530.0 53,520 Dbaccessor.dll
23-Jul-2002 18:09 3.0.1530.0 348,432 Mscis.exe
23-Jul-2002 18:09 3.0.1530.0 188,688 Serializedoc.dll
23-Jul-2002 18:08 3.0.1530.0 528,656 Sharedcomp.dll
23-Jul-2002 18:09 3.0.1530.0 504,080 Validatedoc.dll
11-Apr-2002 16:41 19,632 Sq_priorityupgrade.sql
11-Apr-2002 16:41 13,680 Btm_priorityupgrade.sql
11-Apr-2002 16:41 1,496 Updatechannel.vbs
Note You must install Q321431 as part of this fix. For additional information, click the article number below to view the article in the Microsoft Knowledge Base:
321431 Possible Memory Leak in CDOSYS When You Use IBodyPart Interface
Note You must install this rollup on all BizTalk servers, including your partners' BizTalk servers.
Installation Instructions
- Run the Hotfixsetup.exe file.
- For each computer that is running BizTalk Server and for each database group, execute Btm_priorityupgrade.sql against the BizTalk InterchangeBTM database, and execute Sq_priorityupgrade.sql against the BizTalk InterchangeSQ database. To do this, you must execute the stored procedures against the affected BizTalk database.
- Restart the BizTalk Messaging Service.
Keywords: kbinfo kbQFE KB326845
Technology: kbAudDeveloper kbBizTalkSearch kbBizTalkServ2002 kbBiztalkServAccHIPAA100 kbBiztalkServAccHIPAASearch kbBiztalkServAccSearch kbBiztalkServSearch
