List of bugs that are fixed in BizTalk Server 2004 Service Pack 1 (888740)

811250 FIX: You experience high CPU utilization and no timeout exception when using a timed scope in orchestration

813845 BizTalk Server 2004 rejects reliable receipts from BizTalk Server 2000 and from BizTalk Server 2002

814041 BizTalk Server may fail persisting state to the database and may end the orchestration instance

821934 FIX: BizTalk Server 2004 rejects BTF receipts in Coordinated Universal Time (Greenwich Mean Time) + X time zones

831307 FIX: You cannot use content-based routing with a solicit-response port in BizTalk Server

837441 FIX: The BizTalk Server 2004 HTTP Adapter does not support setting HTTP headers on response from the server

838221 FIX: You receive an "unhandled exception" error message in the event log when you use the flat file parser in BizTalk Server 2004

838225 FIX: You experience slow performance when large maps contain many logical functoids in BizTalk Server 2004

838226 FIX: You experience slow performance when you use the CrossReference APIs in BizTalk Server 2004

838441 FIX: "A service or property can only be accessed on the current service" error message when one orchestration references another orchestration in the same project in BizTalk Server 2004

838454 FIX: You cannot access information about messages in the MessageBox database or track messages in your archives in BizTalk Server 2004

838458 FIX: Rule sets may not be evaluated correctly when you use the NOT operator in BizTalk Server

838535 FIX: The HTTP adapter fails when you try to send large messages in BizTalk Server 2004

838572 FIX: The xsl:for-each statement is put at the parent field of the child field of the destination schema in BizTalk Server 2004

838763 FIX: The Database Lookup functoid/Value Extractor functoid produces inconsistent results

838795 FIX: Element references do not resolve in BizTalk Server 2004

838836 HTTP send port properties do not override HTTP Adapter properties in BizTalk Server 2004

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

838991 FIX: Rules may not be re-evaluated correctly when you use the Update facts function in BizTalk Server 2004

839336 FIX: BizTalk Server 2002 rejects reliable receipts over HTTP from BizTalk Server 2004

839440 FIX: A BizTalk Server project may stop responding when you add schemas and the schemas are opened in Visual Studio .NET

839450 FIX: Many Csc.exe processes may be running on a computer that is running BizTalk Server 2004

839524 FIX: The BizTalk Server 2004 Business Rule Engine may use incorrect values when it evaluates a rule

839663 You cannot disable HTTP chunked encoding in BizTalk Server

839723 FIX: ConfigFramework.exe fails while granting access to the Single Sign-On Database in BizTalk Server 2004

839818 FIX: The Backup BizTalk Server SQL job reports success when the backup has failed in BizTalk Server 2004

840008 FIX: You cannot access the headers and the body of an HTTP failure response in a SOAPException exception

840113 FIX: The BizTalk Server EDI Adapter only supports a limited set of document types

840177 FIX: Some nodes are not expandable in Tracking Profile Editor in BizTalk Server 2004

840262 FIX: The BPEL Import Wizard quits unexpectedly at the last step in BizTalk Server 2004

840296 FIX: A BizTalk 2004 project may stop responding when you add a schema or pipeline to the project and then you open the project

840537 FIX: You cannot view the Message Details in HAT when BizTalk Server 2004 is running under a heavy load condition

840588 The BizTalk Server 2004 MIME/SMIME Decoder component cannot decrypt incoming messages

840740 FIX: "Exception caught: Object reference not set to an instance of an object" error message when you compile a large map in BizTalk Server 2004

840831 You experience an OutOfMemory exception in Visual Studio when you open or close maps

841275 FIX: The scoping parameter of the Cumulative Sum functoid does not generate the results that you expect in BizTalk Server 2004

841333 FIX: You receive error messages when you build your BizTalk Server project or when you validate the schema in the project

841396 FIX: The appID column of the xref_IDXRefData table is limited to 50 characters

841543 The Target charset property may output the incorrect encoding type in an XML document in BizTalk Server 2004

841563 FIX: The CDATA section and formatting is removed when you use a custom XSLT file in BizTalk Server 2004

841564 FIX: Pipeline-initiated transactions are not aborted when message publishing fails in BizTalk Server 2004

841778 FIX: The Openness property is not promoted by the IInterchange shim in BizTalk Server 2004

841781 BUG: You receive an "XSD2EDI failed to convert XSD" error message when you try to validate an EDI instance in BizTalk Server 2004

841994 FIX: The BizTalk Server 2004 HTTP adapter does not support adding custom headers or modifying standard headers

842138 FIX: BizTalk Server 2004 RTM Version does not support the transactional protocol in the BAM API

842495 FIX: You receive an "XSL transform error" error message when you test a map in BizTalk Server 2004 Mapper

842703 FIX: BizTalk Server 2004 may experience high CPU utilization in disassembling XML messages

842860 FIX: The effect of the Constraint.IsPositive property is reversed in Human Workflow Services (HWS) in BizTalk Server 2004

842931 FIX: Outbound maps do not work on a request-response receive port

843031 BUG: BizTalk Server 2004 Health and Activity Tracking shows a completed business process as incomplete

843040 FIX: Changes in an EDI schema in BizTalk Server do not take effect

843269 FIX: Generated data is incorrect in BizTalk Server 2004 when you test a map by using sample XML data as input in Visual Studio .NET

843405 FIX: The complete Electronic Data Interchange interchange is suspended if any one of the subdocuments fails validation in BizTalk Server 2004

843529 FIX: The orchestration stops responding (hangs) on an HTTP Send request, and you receive an unhandled exception error message in BizTalk Server 2004

867449 FIX: Recovery of a lost database connection causes many messages to be put in the BizTalkServerIsolatedHostQ table of the BizTalkMsgBoxDb database

867769 FIX: You receive a "schemaLocation could not be resolved" compiler error message when you import schemas from assemblies in BizTalk Server 2004

870619 FIX: A memory leak in Visual Studio .NET may occur when you deploy a project that contains a schema with a number of roots and then you edit or you create ports in BizTalk Server 2004

870720 FIX: You may receive an error message if multiple Terminal Server sessions run the "Validate Instance" command at the same time in BizTalk Server 2004

870996 FIX: Certain characters in the UNOC character set and certain Swedish characters may not translate when an EDI document is processed with Microsoft BizTalk Server 2004

871008 FIX: Performance may decrease when you use the BizTalk Adapter for FTP when delivery notification is enabled

871198 FIX: Receive locations are disabled in BizTalk Server 2004 when you fail over the MessageBox database (BizTalkMsgBoxDB)

872773 You must back up all the BizTalk Server 2004-related databases when you want to back up an instance of BizTalk Server

872780 FIX: You cannot use the Electronic Data Interchange (EDI) Adapter and use the Uniform Naming Convention path for the receive handler location in BizTalk Server 2004

872805 FIX: Two messages are suspended in the BizTalk Server 2004 Health and Activity Tracking (HAT) tool when one exception occurs in an orchestration

872809 FIX: A transaction is deadlocked and your job fails in BizTalk Server 2004

873385 Messages may not be transmitted correctly when you configure a side-by-side installation of Message Queuing and MSMQT

873394 FIX: The "Wrap segments" property for the EDI Adapter send port may be ignored when documents are serialized in BizTalk Server 2004

873442 FIX: Event ID 23 is repeatedly logged in the Application log on a computer that is running BizTalk Server 2004

875494 FIX: You receive a "Public Responder encountered a processing error on receiving a Asynchronous action" error message in BizTalk Accelerator for RosettaNet 3.0

875497 FIX: Processing seems to stop when you use ordered delivery ports, and you have an increased load of messages in Microsoft BizTalk Server 2004

875499 FIX: BizTalk Server 2004 may slow down when you use MSMQT to send messages

875540 FIX: You receive a "Specified cast is not valid" error message in BizTalk Server 2004 when you use a rule set in Rules Composer or you use a rule set in an orchestration

883663 FIX: You may receive a "hexadecimal value 0x3A, cannot be included in a name" error message in BizTalk Server 2004

883674 FIX: You may receive an "InitializeSecurityContext failed" error message when you try to use the EDI Adapter in BizTalk Server 2004

884519 FIX: Activity model observers cannot retrieve activity flow information unless they are participating in the activity flow in BizTalk Server 2004

884535 You may receive a "failure executing the receive pipeline" event log error message when you deploy a schema assembly in BizTalk Server 2004

884565 FIX: Event ID 5701 and Event ID 5699 are logged in the Application log in BizTalk Server 2004

884873 FIX: Error message details for pipeline failures for a Receive Location are not entered in the event log in BizTalk Server 2004

884876 FIX: Context properties of messages are not saved in the Message Box database for incoming non-seekable large messages in BizTalk Server 2004

884887 The result of the Index functoid is an empty string when you specify the Attribute FormDefault property of the source schema as Qualified in BizTalk Server 2004

885405 FIX: The MessageBox database (BizTalkMsgBoxDb) continues to grow larger and may eventually consume all available disk space in BizTalk Server 2004

885448 FIX: You receive an "An exception occurred" error message when you use a .NET class in the Business Rule Composer

885847 FIX: You may receive a "The Record Tag is not within the total length of the record" error message when you compile a flat file schema in BizTalk Server 2004

885888 FIX: Business Activity Monitoring (BAM) data may not be written to the database if tracking is not enabled in BizTalk Server 2004

885902 FIX: You receive an "Invalid URI" error message when you configure the "Logical address" property for the send handler that is used by the EDI Adapter

885905 FIX: You receive a "SQL Server does not exist" error message when you connect to a BizTalk Server 2004 Management database from BizTalk Explorer

885913 FIX: The "Backup BizTalk Server" SQL Server job is unsuccessful in BizTalk Server 2004

885935 FIX: You receive a "The chosen transport HTTP does not support solicit-response protocol" error message in BizTalk Server 2004

886226 FIX: The BizTalk Server 2004 File Adapter may cause a NonPagedPool memory leak

886966 FIX: Slow performance on startup when you process a high volume of messages through the SOAP adapter in BizTalk Server 2004

887575 FIX: BizTalk Server 2004 stops responding when you use the file adapter to receive messages that are larger than 100 KB

887692 FIX: You receive a "NullPartException" error message when you use nested orchestrations in BizTalk Server 2004

887795 FIX: You receive a "COMException" exception event message when you run an orchestration in BizTalk Server 2004

887918 FIX: A data loss may occur in a published BizTalk one-way Web service in Microsoft BizTalk Server 2004

887959 You may notice significant loss of performance in BizTalk Server 2004 when the bts_PurgeSubscriptions stored procedure is used to delete subscriptions

891844 FIX: You may receive compilation error messages when you create orchestrations that have a very specific relationship in BizTalk Server 2004

841618 FIX: The BizTalk Adapter for SQL Server may repeatedly try to process a bad message

884532 The TrackedMessages_Copy_BizTalkMsgBoxDb SQL Server Agent job fails and you receive a "Cannot insert the value null into column uidBodyPartID" error message in BizTalk Server 2004

885897 FIX: The BizTalk Server HTTP Adapter pre-appends the byte order mark (BOM) to output messages in BizTalk Server 2004