List of bugs that are fixed in BizTalk Server 2004 Service Pack 2

Article translations Article translations
Article ID: 924330 - View products that this article applies to.
Expand all | Collapse all

On This Page

SUMMARY

This article is a listing of article numbers for bugs that were fixed in BizTalk Server 2004 Service Pack 2 (SP2). Click the article number that comes before the title of the bug to view the article.

For more information about how to obtain the latest service pack for BizTalk Server 2004, 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

MORE INFORMATION

Service Pack 2

838963 FIX: Only the first FTP command runs when you specify multiple FTP commands in the "After Put" property of an FTP send handler in BizTalk Server 2004
884062 A System.OutOfMemory exception occurs when you compile a solution map that has a complex source schema or a complex destination schema
884582 The character of the segment terminator of a functional acknowledgement may be ignored in the Microsoft BizTalk Server 2004 EDI adapter
886674 FIX: The signed message that you receive from BizTalk SharePoint Messaging Adapter cannot be verified in BizTalk Server 2004
886966 FIX: Slow performance on startup when you process a high volume of messages through the SOAP adapter in BizTalk Server 2006 or in BizTalk Server 2004
888309 FIX: The Value Extractor functoid may return a value that is not correct when BizTalk Server 2004 is under a heavy load
888320 FIX: Some party aliases may not be created when you run the BizTalk Deployment Wizard in BizTalk Server 2004
889077 FIX: Delivery notification in a send port causes performance degradation in BizTalk Server 2004
889164 FIX: The edi_datatype property is set to "A" when the value should be "AN" in BizTalk Server 2004
889322 FIX: The SQL Transport Schema Generation Wizard generates a schema that contains only a Success node in BizTalk Server 2004
890174 FIX: The BizTalk Server 2004 HTTP receive adapter does not fully support IIS ISAPI authentication filters for incoming messages
890241 FIX: A newer version of an assembly may unexpectedly stop working when you undeploy an older version of the assembly in BizTalk Server 2004
890530 FIX: You receive a "The root element is missing" error message when you try to process a message by using a Message Queuing transport adapter send port in BizTalk Server 2004
890731 FIX: The Btsntsvc.exe process uses a high amount of CPU resources and an orchestration never finishes in BizTalk Server 2004
890754 FIX: SQL Server blocking may occur when you have the Message Body Tracking feature enabled in BizTalk Server 2004
890769 BUG: The Base EDI adapter may generate incorrect XML for some schemas in BizTalk Server 2004
890840 FIX: The Before Receive tracking feature may not capture the correct message in BizTalk Server 2004
890842 FIX: You may experience suboptimal performance when you use Value Mapping functoids in BizTalk Server 2004
891015 Event ID 5720 is logged in the Application log after you remove an assembly in BizTalk Server 2004
891045 FIX: You receive an "error B1000" error message when you try to export an orchestration to a BPEL file when the orchestration contains a variable of type System.Xml.XmlDocument in BizTalk Server 2004
891441 You may receive a "Document Locked" error message in the BizTalk Server 2004 error log when you save an InfoPath document directly to a Windows SharePoint Services site
891447 FIX: A distinguished field returns incorrect content when you use the empty <FieldName /> element tag form for the empty field in BizTalk Server 2004
892048 FIX: An orchestration in BizTalk Server 2004 is suspended and is marked as "not resumable" when the SQL Server-based cluster fails over
892138 FIX: A message is discarded when you start a serial convoy orchestration after multiple messages are submitted in BizTalk Server 2004
892405 FIX: Messages are processed and delivered even if the orchestration instance finishes with a status of "Completed with discarded messages" in BizTalk Server 2004
892491 FIX: BizTalk Server 2004 performance may be poor and your CPU utilization may be high on the SQL Server-based server that hosts the BizTalk Server databases
892921 You receive different HTTP status codes when you post a document to a one-way HTTP receive port in BizTalk Server 2004
893287 FIX: The resulting XML instances do not contain the correct number of N1Loop occurrences after the BizTalk Server 2004 Base EDI adapter processes an EDI flat-file document
893754 FIX: You experience an unexpected increase in memory usage when you deploy and enlist an orchestration in BizTalk Server 2004
894060 FIX: BizTalk Server 2004 incorrectly generates repeated NACK messages for a BizTalk Framework message that remains in the suspended queue
894177 FIX: You receive an "Exception Caught: Cannot use a prefix with an empty namespace" error message when you use a Transform shape to generate a map in BizTalk Server 2004 Service Pack 1
894253 FIX: The dtasp_PruneTrackingdatabase() stored procedure may take many hours to clean up the DTA database in BizTalk Server 2004
894683 FIX: The Base EDI Adapter does not process a large EDI message and Event ID 23 is logged in the Application log in BizTalk Server 2004
894785 FIX: You receive a "Native serialization error: (The target document in this mapping is not recognized)" error message when you test a map that uses a valid 4030 format 810 schema in BizTalk Server 2004
894792 FIX: The receive locations do not accept the newly submitted documents when you deploy a new version of a pipeline assembly in BizTalk Server 2004
894919 FIX: You receive a "Timeout expired" error message when you try to compile a BizTalk Server 2004 project that contains an EDI schema in Visual Studio .NET 2003
894920 FIX: The EDI X-12 856 Ship Confirmation (X12_4010_856) schema has only two HL segments in BizTalk Server 2004
895107 The HTTP adapter incorrectly converts the whole ContentType header to lowercase characters in BizTalk Server 2004 Service Pack 1
895175 FIX: An orchestration is not completed successfully, and an exception is logged in an atomic transaction in BizTalk Server 2004 Service Pack 1
895264 FIX: You receive an error message when you call the GetCommonValue method against an empty element in a BizTalk Server map
895955 FIX: Error message when you run the sp_GetRemoteServerName stored procedure in BizTalk Server 2004 Service Pack 1: "Msg 7403, Level 16, State 1"
896080 FIX: Some messages that are picked up by using a File receive adapter location may be lost in BizTalk Server 2004
896152 FIX: The exception handler in Orchestration is not triggered if you experience an error in your outbound map in BizTalk Server 2004
896673 FIX: A 10-second delay occurs before a message is received by the file receive location in BizTalk Server 2004
898106 FIX: Message processing may slow or stop after you install BizTalk Server 2004 Service Pack 1
899654 FIX: You may receive a "btm1050: XSL transform error" error message when you test a map in BizTalk Server 2004
900083 FIX: The tracking event stream is not exposed in BizTalk Server 2004 orchestrations
900339 FIX: You may experience slow performance when you configure the HAT tool to save all tracked messages for an orchestration in BizTalk Server 2004
900400 FIX: You may experience intermittent lock conditions when you have multiple BizTalkMsgBoxDb databases configured in BizTalk Server 2004
900467 FIX: You experience deadlocks on the BizTalkMsgBox database after you install BizTalk Server 2004 Service Pack 1
901028 FIX: Event ID 5719 may occur when you use a custom receive pipeline to validate a document structure in BizTalk Server 2004
901186 FIX: Message processing may stop, you may receive an event ID error message, and the MSDTC service may stop committing transactions when you map a large document in BizTalk Server 2004
902102 FIX: The BizTalk Server 2004 FTP send adapter may send duplicate messages when you configure two FTP send ports to use the same BTS.ReceivePortName filter
902397 FIX: You receive a "SQL Server does not exist or access denied" error message when you try to view tracked policy execution events in the Health and Activity Tracking tool
903874 FIX: An "Index was outside the bounds of the array" error message is logged and existing messages do not correctly correlate after you install BizTalk Server 2004 Service Pack 1
904168 FIX: An "Enterprise Single Sign-On is offline" error message may be logged in the Configuration log when you try to use the "Configframework /s" command to silently reconfigure BizTalk Server 2004
904844 FIX: Error message when a flat file parser parses a message that contains blank spaces in BizTalk Server 2004 Service Pack 1: "The element 'MessageUserReference_108' has incomplete content"
904950 FIX: The performance of a singleton orchestration that contains a Call Orchestration shape may decrease over time in BizTalk Server 2004
905290 FIX: The rule engine may return incorrect values in BizTalk Server 2004
905571 FIX: The Business Rule Engine may not process rules that have different priorities when a server is under a heavy load in BizTalk Server 2004
905830 FIX: The XLANG engine may not report a failed DTC transaction and may not end the transaction in BizTalk Server 2004
907344 FIX: You may receive a "Failed to create project" error message when you try to publish an orchestration as a Web service in BizTalk Server 2004
908023 FIX: Per-instance pipeline configuration does not work as expected in BizTalk Server 2004
908157 FIX: You notice many dehydrated service instances when you run a query in BizTalk Server 2004 Health and Activity Tracking
908257 FIX: Error message when you use the ISSOTicket.IssueTicket method in BizTalk Server 2004: "80070057: Invalid parameter"
908359 FIX: The Business Activity Services Messaging Adapter does not work as expected in BizTalk Server 2004 after you install Windows SharePoint Services Service Pack 2
909009 FIX: Error message when you try to save message bodies that are tracked by a PassThrough pipeline in BizTalk Server 2004: "Internal failure"
909945 FIX: You receive out-of-memory exception error messages when an orchestration contains Delay shapes in BizTalk Server 2004
910142 FIX: The BizTalk Service may appear to stop responding and you may receive out-of-memory error messages in BizTalk Server 2004
910400 FIX: The bts_fnFindConvoySet function in BizTalk Server 2004 uses lots of SQL Server CPU resources
910912 FIX: The generated file contains two message body parts when you create a custom pipeline that contains only a MIME Decoder in BizTalk Server 2004
912031 FIX: You cannot deploy a BizTalk assembly, and you may receive an error message in BizTalk Server 2004
912276 FIX: Performance may decrease over time when you use a long-running orchestration in BizTalk Server 2004
912483 FIX: A property may not be promoted as expected when you use the BTF Disassembler pipeline component in a custom pipeline to process BTF documents in BizTalk Server 2004
912504 FIX: After a failover of the SQL Server cluster resource, response messages are suspended in BizTalk Server 2004
913669 FIX: The Base EDI adapter reads only the first AK2 segment in the 997 functional acknowledgement in BizTalk Server 2004
914018 FIX: A memory leak may occur in the BizTalk service when a receive location uses the MSMQT adapter in BizTalk Server 2004
914299 FIX: The memory may not be released as expected when you compile a BizTalk Server 2004 project
915576 FIX: White spaces are removed from promoted fields after map execution in an orchestration after you install BizTalk Server 2004 S915576
915600 FIX: You must manually configure the Log Shipping feature in BizTalk Server 2004 Service Pack 1
917160 FIX: The SMTP adapter does not try to resend a BizTalk Framework document in BizTalk Server 2004
917871 FIX: In BizTalk Server 2004, a signed MIME message may be marked as falsified when the message is received by an SMTP client
918343 FIX: The MSMQT adapter may unexpectedly stop processing messages if you experience database failure or intermittent connectivity issues in BizTalk Server 2004
918758 FIX: An orchestration may stop responding and the message status is "Delivered Not Consumed" in BizTalk Server 2004
919229 FIX: The MSMQT receive adapter sends a BAD_DESTINATION_NACK negative acknowledgement after you manually fail over an MSMQT receive port in BizTalk Server 2004
919230 FIX: Error message when the MessageBox_Message_ManageRefCountLog_BizTalkMsgBoxDb SQL Server job fails in BizTalk Server 2004: "Arithmetic overflow error"
919339 FIX: Error message when you try to change the ADO.NET connection string of an SQL send port on a server that is running BizTalk Server 2004: "HRESULT: 0x80131500"
920136 FIX: Some Business Rule Engine values in the Windows registry are reset to the default values in BizTalk Server 2004
923056 FIX: Event ID: 5754 when you use the SOAP adapter or the HTTP adapter together with a client certificate in BizTalk Server 2004
923531 FIX: Field contents may be truncated when you use the BizTalk Server 2004 Flat File Assembler to serialize and then send a SWIFT FIN message to SWIFT
923534 You cannot configure the BizTalk host instance to use a Windows group name that exceeds 63 characters in BizTalk Server 2006 and in BizTalk Server 2004
904949 FIX: The MessageID property in the Health and Activity Tracking (HAT) tool does not match the MessageID property of the corresponding output file when you enable the Message Body Tracking feature in BizTalk Server 2004
911617 FIX: Side-by-side deployment does not work as expected when convoys are used in orchestrations in BizTalk Server 2004

Properties

Article ID: 924330 - Last Review: April 20, 2007 - Revision: 4.1
APPLIES TO
  • Microsoft BizTalk Server 2004 Standard Edition
  • Microsoft BizTalk Server 2004 Enterprise Edition
  • Microsoft BizTalk Server 2004 Developer Edition
  • Microsoft BizTalk Server 2004 Partner Edition
Keywords: 
kbinfo kbtshoot kbbtsservpack kbbts biztalk2004-2006swept KB924330

Give Feedback

 

Contact us for more help

Contact us for more help
Connect with Answer Desk for expert help.
Get more support from smallbusiness.support.microsoft.com