Notice: This website is an unofficial Microsoft Knowledge Base (hereinafter KB) archive and is intended to provide a reliable access to deleted content from Microsoft KB. All KB articles are owned by Microsoft Corporation. Read full disclaimer for more details.

Articles for product: BizTalk Server 2006 R2 Branch Edition

Article ID Article Title Hidden
959143 FIX: Message types MT535, MT564, and MT566 fail the BRE validation when you use Microsoft BizTalk Accelerator for SWIFT Message Pack 2008
959251 FIX: You receive an error message when a computer that is running BizTalk Server 2006 R2 tries to receive an IDOC message from SAP by using the WCF-based SAP adapter
959315 FIX: You do not see any messages that pass through the ordered send port when you run some message queries in Health and Activity Tracking in BizTalk Server 2006 or in BizTalk Server 2006 R2
960237 FIX: The HHMMSSd time format is now available for selection for the GS5 element when you configure EDI properties of BizTalk party in BizTalk Server 2006 R2
960473 Invalid 997 functional acknowledgements are generated in Microsoft BizTalk Server 2006 R2
960731 FIX: Transactions remain active for a long time when you use a WCF-based adapter in BizTalk Server 2006 R2
960912 FIX: Error message when you submit an MT564 message that contains both the OPST qualifier and the CLAS qualifier in Microsoft BizTalk Accelerator for SWIFT Message Pack 2008: "Message failed parsing; cannot be serialized"
960914 A hotfix rollup package is available for BizTalk Accelerator for SWIFT 3.0 Service Pack 1
960990 FIX: A hotfix is available for BizTalk Accelerator for SWIFT 2008 Message Pack to resolve several issues that are related to SWIFT message validation
961020 FIX: Event IDs 5812, 5743, and 5754 are logged when you use BizTalk Accelerator for HL7 2.0 or Microsoft BizTalk Accelerator for HL7 1.3
961023 FIX: Batched and unbatched messages log event 4119 as an informational event in BTAHL7, or the whole batch is suspended if any message contains a parsing error
961072 FIX: The VEF, GHS, SDG, and MZN currency codes are missing in Microsoft BizTalk Accelerator for SWIFT Message Pack 2008
961149 FIX: The receive location does not use the start date and the stop date that you set in BizTalk Server
961163 Batched EDI messages that are sent from the EdiSend pipeline are not saved for Health and Activity Tracking (HAT) in BizTalk Server 2006 R2
961330 FIX: The EDIMessageContent table is not purged correctly when DTA Archive and Purge job is run in BizTalk Server 2006 R2
961346 FIX: The BizTalk Adapter for TIBCO EMS does not delete messages from the JMS queue after the adapter successfully receives the messages in BizTalk Server 2006 R2
961534 FIX: You cannot configure BizTalk Accelerator for RosettaNet 3.5 when you log on to the server by using a user account from the trusted domain or when you use a named instance of SQL Server for the configuration
961541 FIX: The BizTalk Adapter for TIBCO EMS does not reconnect to the TIBCO EMS server after the TIBCO EMS server becomes available to reconnect
961708 FIX: You cannot configure BizTalk Accelerator for SWIFT 3.0, and you receive the following error message: "You need to be a BizTalk Administrator"
961810 FIX: The number of concurrently running orchestrations in BizTalk Server reaches 250, and you experience poor performance after you install the .NET Framework 2.0 SP1 or a later version of the .Net Framework
963000 FIX: BizTalk Server 2006 R2 does not process an XML message, and the following application event error is logged: "The targetNamespace attribute cannot have empty string as its value"
963013 FIX: The BizTalk Accelerator for RosettaNet 3.5 configuration tool (Configuration.exe) closes unexpectedly when you run the configuration tool on a computer that does not have Windows SharePoint Services 2.0 installed
963690 FIX: Arithmetic overflow exception after you run a BAM activity for a long time in Microsoft BizTalk Server 2006 R2: "Arithmetic overflow error converting expression to data type int"
967036 FIX: Binding configurations for some binding types are not saved in the WCF-Custom adapter or in the WCF-CustomIsolated adapter in BizTalk Server Administration Console
967606 FIX: The BizTalk Server FTP adapter does not retrieve files successfully from an IBM AIX-based FTP server that is set to the fr_FR locale
967765 FIX: A Business Activity Monitoring (BAM) activity does not track the first message of a batch in BizTalk Server 2006 R2
967939 FIX: You receive a NullReferenceException error message after you rehydrate an XLANG orchestration that was running for a long time in BizTalk Server 2006 R2
967945 FIX: The generated XML files are much larger than expected when you try to split an EDI document that contains multiple sub-documents by using a "multiple" type schema in BizTalk Server 2006 R2 or BizTalk Server 2009
968016 FIX: The BizTalk Server 2006 R2 FTP adapter randomly stops retrieving files from an FTP server until you restart the BizTalk host instance
968654 FIX: A message of the System.Xml.Xmldocument type that is sent from an orchestration is suspended and a routing failure report is generated when you specify the Direct Binding type for the ports in the orchestrations in BizTalk Server 2006 R2
968706 Importing a signing certificate fails with an error
969147 FIX: Message type MT941 and message type MT942 fail XML validation when you use Microsoft BizTalk Accelerator for SWIFT Message Pack 2008
969193 XLANG/s error message with Event ID: 10033 occurs if solicit-response SOAP send port is configured with the PassThruReceive receive pipeline
969217 FIX: Event ID 14014 is logged in the BizTalk Server Application log and BAM Alerts are not sent as expected
969221 The published message could not be routed because no subscribers were found
969870 FIX: The tracking data is not moved as expected from the BizTalkMsgBoxDb database to the BizTalkDTADb database in BizTalk Server 2006 R2
969987 FIX: You cannot suspend or terminate service orchestration instances after you incorrectly shut down a BizTalk Server host instance in Microsoft BizTalk Server 2006 R2
970075 FIX: A Message Disposition Notification (MDN) is not received when the compression feature is enabled for the AS2 adapter in Microsoft BizTalk Server
970194 FIX: A Target server receives only the last message when you use a BizTalk FileAct adapter to send over PUT FILE requests that have the same "Sw:LogicalName" logical name specified in BizTalk Server 2006 R2
970231 FIX: Event ID: 208 is logged, and the MessageBox_Message_Cleanup_BizTalkMsgBoxDb job may fail in BizTalk Server
970292 FIX: Error message when you view the EDI Batching Report in BizTalk Server 2006 R2: "This operation failed while accessing at least one of the Message Box databases"
970493 FIX: A hotfix is available that lets you manage BizTalk RFID in Microsoft BizTalk Server 2006 R2 or in Microsoft BizTalk Server 2009 by using an account that is not a local administrator
970856 FIX: Messaging properties are not tracked for some messages in an interchange in Microsoft BizTalk Server 2006 R2 or BizTalk Server 2009
971924 Enabling tracking on an MLLP receive port or BTAHL72XReceivePipeline fails to save the inbound message
971998 FIX: BizTalk Accelerator for SWIFT 3.0 support for the MT202COV and MT205COV message types of the SWIFT 2009 Standard
972449 FIX: The BizTalk RFID service stops generating management events after you uninstall a BizTalk RFID hotfix in BizTalk Server 2006 R2
972478 FIX: The SE Segment delimiter/terminator is missing intermittently in outgoing 997 functional acknowledgements when you send and receive EDI messages in BizTalk Server 2006 R2 or BizTalk Server 2009
972530 Some interchanges are suspended if you use the EDI receive pipeline to receive multiple interchanges that are included in a single EDI message in BizTalk Server 2006 R2 (972530)
972538 FIX: Some BAM events are not tracked for a batch of messages if continuation is defined in the tracking profile in BizTalk Server 2006 R2
972849 Fix: In BizTalk Server 2006 R2, you cannot build a BizTalk Server project if the project refers to a schema and the first part of the schema namespace is a substring of the project namespace