Condividi tramite

List of Fixes included in BizTalk 2006 R2 SP1

  • Articolo

BizTalk 2004 - # of Fixes 3

  

Backup 

  
  • 958211 - FIX: The rules engine tables are not being purged when you use BizTalk Server
  

BAM 

  
  • 940483 - FIX: A BAM archive job fails because of a disk space shortage when you archive business activity data to the BAMArchive database in BizTalk Server 2004 or in BizTalk Server 2006
  

FTP 

  
  • 950577 - FIX: The size of a file is 0 bytes when the FTP adapter saves the file in a temporary folder in BizTalk Server 2004
  

BizTalk 2006 - # of Fixes 23

  

BAM 

  
  • 940483 - FIX: A BAM archive job fails because of a disk space shortage when you archive business activity data to the BAMArchive database in BizTalk Server 2004 or in BizTalk Server 2006
  
  • 948509 - FIX: The BAM Portal request view display may be incorrect in BizTalk Server 2006 or in BizTalk Server 2006 R2
  
  • 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"
  
  • 971984 - A hotfix is available that enables you to clear the BAM data from the BAMPrimaryImport database instead of having to archive the data to the BAMArchive database in BizTalk Server 2006
  

EPM 

  
  • 940457 - FIX: Event ID 5799 and Event ID 5677 occur if you have a running orchestration that has a nil value in BizTalk Server 2006 or BizTalk Server 2006 R2
  
  • 942024 - FIX: A Business Activity Monitoring (BAM) activity is not rolled back when the send port fails in delivering the output message in BizTalk Server 2006
  

FTP 

  
  • 942438 - FIX: The BizTalk Adapter for FTP stops working if a pipeline component does not process the complete FTP data stream in BizTalk Server 2006
  
  • 955651 - FIX: The FTP adapter stops processing the file transfer in a Microsoft BizTalk Server 2006 environment after a network connection recovers
  
  • 958235 - FIX: Event ID 5740 is logged in the Application log when you use an FTP adapter in BizTalk Server to receive files from an empty directory on an FTP server
  

General 

  
  • 948238 - FIX: Event ID 1000 occurs when you try to start a 32-bit SNL receiver process on a computer that is running the 64-bit version of BizTalk Server 2006 R2
  

General/Engine 

  
  • 938483 - FIX: BizTalk Server 2006 suspends the orchestration and logs event 10033 in the Application log when BizTalk Server 2006 detects a schema version mismatch
  
  • 943125 - The XLANG Scheduler Engine enters an infinite loop, and a BizTalk Server 2006 process uses 100 percent of the CPU resources if a time-out exception is handled by a non-transactional scope
  
  • 951762 - FIX: Outgoing 837 interchanges may contain incorrect GS and ST segment values in Microsoft BizTalk Server 2006 R2
  
  • 954877 - FIX: Zombie messages cause high CPU usage on servers that host BizTalk Server 2006
  

HTTP 

  
  • 944233 - FIX: A message is processed even if the delivery notification acknowledgement fails to route in Microsoft BizTalk Server 2006
  

Messaging 

  
  • 947258 - FIX: Health and Activity Tracking returns incorrect results in BizTalk Server
  

Msgbox 

  
  • 944234 - FIX: The CPU usage remains high for a long time on a computer that is running SQL Server and BizTalk Server 2006
  
  • 970231 - FIX: Event ID: 208 is logged, and the MessageBox_Message_Cleanup_BizTalkMsgBoxDb job may fail in BizTalk Server
  
  • 972196 - FIX: A BizTalk host instance stops and an Event ID 5410 is logged in the Application log in BizTalk Server 2006.
  

MSMQ 

  
  • 945719 - FIX: You cannot start a Terminal Services session on a server that is running BizTalk Server 2006 after a memory leak occurs in the BizTalk Server service
  

Setup 

  
  • 935960 - An update is available that lets you disable Routing Failure Reports in BizTalk Server 2006
  

SOAP 

  
  • 942133 - FIX: A NACK message from a Web service does not contain the details of the original exception in BizTalk Server 2006
  
  • 971799 - FIX: Error message in BizTalk Server 2006 in the Application Event log when you use a SOAP send port and messages are not sent successfully: "OutOfMemoryException: Exception of type 'System.OutOfMemoryException' was thrown"
  

BizTalk 2006 R2 - # of Fixes 95

  

Backup 

  
  • 944838 - FIX: The Log Shipping feature may not restore database backup files in BizTalk Server 2006 or in BizTalk Server 2006 R2
  
  • 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
  

BAM 

  
  • 942235 - FIX: S BAM aggregate alert is not sent as expected in BizTalk Server 2006 and in BizTalk Server 2006 R2
  
  • 969558 - FIX: Error message when you try to deploy BAM update when partitioning is enabled for an existing activity: "All queries combined using a UNION, INTERSECT or EXCEPT operator must have an equal number of expressions in their target lists"
  
  • 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
  

Biztalk Administration 

  
  • 952947 - FIX: A user in the BizTalk Server Operators group cannot enable or disable a SQL r or MSMQ receive location in BizTalk Server 2006 R2
  
  • 961149 - FIX: The receive location does not use the start date and the stop date that you set in BizTalk Server
  

BizTalk Editor 

  
  • 944320 - FIX: Error message when you try to import DTD schemas into a BizTalk project in BizTalk Server 2006 R2: "There were some errors generated during schema generation"
  

BizTalk Project Explorer 

  
  • 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"
  
  • 972849 - 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
  

BTS Runtime 

  
  • 975118 - FIX: Error message when you receive an 837 document in BizTalk Server 2006 R2: "Missing or invalid or duplicate Transaction set identifier"
  

Custom/Adapter Framework 

  
  • 943383 - FIX: An XML declaration is not added to an outgoing document when you use the BizTalk Framework Assembler pipeline component in a pipeline in BizTalk Server 2006 R2
  

Deployment 

  
  • 944158 - FIX: You may experience problems if a BizTalk application has a map configured on a send port in BizTalk Server 2006
  
  • 954814 - FIX: Importing an .msi file may take a very long time or you may get a "Timeout expired" error
  
  • 954906 - FIX: The number of connections to SQL Server may increase to over 500 when you try to import the same BizTalk application .msi file again in BizTalk Server 2006 R2
  
  • 957352 - FIX: You cannot select two or more maps that have source schemas the belong to the same multi-root schema file on the same send or on the same receive port in BizTalk Server 2006 R2
  

EDI 

  
  • 939080 - FIX: Error message when you use Microsoft BizTalk Server 2006 R2 to receive HIPAA messages
  
  • 942733 - FIX: Error message when you try to verify the signature of an incoming AS2 message or of an incoming MDN message on a computer that is running BizTalk Server 2006 R2
  
  • 944063 - FIX: In BizTalk Server 2006 R2, you cannot use the MIME.FileName context property to rename an EDI file when you use the SMTP adapter to send the EDI file as an attachment
  
  • 945165 - FIX: You may receive error messages when you receive an X12 997 functional ACK in a BizTalk Server 2006 R2 EDI application
  
  • 945998 - FIX: You cannot start a Terminal Services session on a server that is running BizTalk Server 2006 after a memory leak occurs in the BizTalk Server service
  
  • 947459 - FIX: The GS04 header value uses the CCYYMM format instead of the YYMMDD format in BizTalk Server 2006 R2
  
  • 948747 - FIX: You may receive an event ID 5753 error message when you try to use the BizTalk Server 2006 R2 EDI functionality
  
  • 949872 - FIX: You cannot correlate batched EDI/AS2 messages to incoming MDNs in BizTalk Server 2006 R2
  
  • 950673 - FIX: The size of a file is 0 bytes when the FTP adapter saves the file in a temporary folder in BizTalk Server 2004
  
  • 950868 - FIX: The size of a file is 0 bytes when the FTP adapter saves the file in a temporary folder in BizTalk Server 2004
  
  • 951203 - A hotfix is available for BizTalk Server 2006 R2 that enables support for AS2 File name preservation
  
  • 951760 - FIX: Outgoing 837 interchanges may contain incorrect GS and ST segment values in Microsoft BizTalk Server 2006 R2
  
  • 952195 - FIX: Outgoing 837 interchanges may contain incorrect GS and ST segment values in Microsoft BizTalk Server 2006 R2
  
  • 952202 - FIX: MDNs are not sent to the sending party in BizTalk Server 2006 R2
  
  • 953388 - FIX: You may experience poor performance when you try to split large EDI interchanges in BizTalk Server 2006 R2
  
  • 954557 - FIX: The BizTalk Server native EDI functionality swaps the GS02 field and the GS03 field in BizTalk Server 2006 R2
  
  • 955303 - FIX: The EDI description context property for the routing failure report has an unhelpful error description in BizTalk Server 2006 R2
  
  • 956051 - FIX: An update that adds a fourth option to process incoming EDI messages in BizTalk Server 2006 R2 is available
  
  • 956916 - FIX: An error message occurs when BizTalk Server receives an MDN that does not contain the Message-ID field in the HTTP header: "System.ArgumentException: Empty parameter string not allowed"
  
  • 957512 - FIX: An HIPAA 837 document that has noncompliant NM108 and NM109 data elements is not validated as expected 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
  
  • 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
  
  • 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
  
  • 970075 - FIX: A Message Disposition Notification (MDN) is not received when the compression feature is enabled for the AS2 adapter in Microsoft 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"
  
  • 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
  
  • 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)
  
  • 973474 - FIX: You receive a NullReferenceException exception when you use the Call Orchestration shape in BizTalk Server 2006 R2
  
  • 973901 - FIX: Error message when you receive an 837 document in BizTalk Server 2006 R2: "Missing or invalid or duplicate Transaction set identifier"
  

EPM 

  
  • 940457 - FIX: Event ID 5799 and Event ID 5677 occur if you have a running orchestration that has a nil value in BizTalk Server 2006 or BizTalk Server 2006 R2
  
  • 944532 - Four properties have been added to the ErrorReport namespace context of BizTalk Server 2006 R2
  
  • 950456 - FIX: In BizTalk Server 2006 or in BizTalk Server 2006 R2, the transformation may stop responding, and the CPU utilization may be 100 percent
  
  • 950878 - FIX: BizTalk does not consume messages when the Ordered Delivery feature is enabled
  
  • 954276 - FIX: The response message from the Web service is not tracked in BizTalk Server 2006 R2
  
  • 958296 - FIX: An XML message remains in the active queue instead of in the suspended queue when you enable tracking after port processing for a send port that uses the EdiSend pipeline in BizTalk Server 2006 R2
  

File 

  
  • 943859 - FIX: A receive location that uses the file adapter does not retry when a network failure occurs in BizTalk Server 2006 or in BizTalk Server 2006 R2
  

FTP 

  
  • 943228 - FIX: The BizTalk FTP Adapter reports that no files are available even though the files exist when you try to connect to a GXS server in BizTalk Server 2006 R2
  
  • 944513 - FIX: In BizTalk Server 2006, the FTP adapter may take a long time to transfer a file to an IBM AIX-based FTP server
  
  • 950980 - FIX: BizTalk does not consume messages when the Ordered Delivery feature is enabled
  
  • 959631 - FIX: The BizTalk Server FTP adapter does not send messages and event errors occur when the FTP send port uses "QUIT" as the AfterPut command in BizTalk Server 2006 R2
  
  • 961724 - FIX: The BizTalk 2006 FTP adapter does not retrieve a file from an FTP server when you issue the RETR command
  
  • 967154 - FIX: The FTP receive location does not receive a file if the FTP raw command is configured in the Before Get field in BizTalk Server
  
  • 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
  

HAT 

  
  • 938830 - FIX: You may experience a long delay when you use the Health and Activity Tracking (HAT) tool in a BizTalk Server environment
  

Msgbox 

  
  • 943165 - FIX: A CPU usage spike occurs on all the BizTalk hosts after you install security bulletin MS07-040 on a server that is running Microsoft BizTalk Server 2006 or Microsoft BizTalk Server 2006 R2
  
  • 944234 - FIX: The CPU usage remains high for a long time on a computer that is running SQL Server and BizTalk Server 2006
  
  • 944426 - FIX: Orphaned cache instances may be built in the Instances and Hosts Queue tables of the BizTalkMsgBoxDb database in BizTalk Server 2006 and in BizTalk Server 2006 R2
  
  • 952310 - FIX: MDNs are not sent to the sending party in BizTalk Server 2006 R2
  
  • 958210 - FIX: You cannot create a HOST instance when your user account is a member of BizTalk Server Administrators group in SQL Server
  
  • 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
  
  • 967931 - FIX: Unused subscription predicates are not purged from the NotEqualsPredicates table of the BizTalkMsgBoxDB database in BizTalk Server 2006 and in BizTalk 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
  
  • 970856 - FIX: Messaging properties are not tracked for some messages in an interchange in Microsoft BizTalk Server 2006 R2
  

MSMQ 

  
  • 942221 - FIX: Error message when you try to stop the BizTalk service in BizTalk Server 2006: "The service did not respond to the start or control request in a timely fashion"
  

Orchestration 

  
  • 927052 - FIX: Error message when you try to enlist two orchestrations at the same time in BizTalk Server: "Value does not fall within the expected range"
  
  • 973430 - FIX: You receive a NullReferenceException exception when you use the Call Orchestration shape in BizTalk Server 2006 R2
  

Pipelines 

  
  • 917871 - FIX: In BizTalk Server 2004, a signed MIME message may be marked as falsified when the message is received by an SMTP client
  
  • 954812 - BizTalk Server 2006 may be unable to decode the S/MIME information in the header of an incoming MIME message that was generated by BizTalk Server 2002
  
  • 967765 - FIX: A Business Activity Monitoring (BAM) activity does not track the first message of a batch in BizTalk Server 2006 R2
  

POP3 

  
  • 937173 - An update is available that lets you disable Routing Failure Reports in BizTalk Server 2006
  
  • 975826 - FIX: Error message when you use the POP3 adapter in BizTalk Server 2006 R2: "The POP3 adapter received a response line from a server that contains more than 512 characters"
  

Portal 

  
  • 973770 - FIX: You receive a NullReferenceException exception when you use the Call Orchestration shape in BizTalk Server 2006 R2
  

Runtime 

  
  • 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
  
  • 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
  

SMTP 

  
  • 944560 - FIX: BizTalk Server may output the wrong S/MIME information when you use BizTalk Server 2006 or the BizTalk Server SMTP Adapter with Microsoft Exchange Server 2003
  

SQL Adapter 

  
  • 939589 - FIX: You cannot insert a string that begins with a money sign in a database by using an XML updategram when you use Microsoft BizTalk Adapter for SQL Server
  
  • 942465 - FIX: An update is available that lets you dynamically configure certain properties on a server that is running BizTalk Server 2006 R2
  

WCF 

  
  • 959136 - FIX: The client's credentials are not used when an orchestration calls a second WCF service, and event ID 5754 is logged in BizTalk Server 2006 R2
  
  • 960731 - FIX: Transactions remain active for a long time when you use a WCF-Custom adapter in BizTalk Server 2006 R2
  

WCF Adapter 

  
  • 942612 - FIX: You may experience problems when you use a Windows Communication Foundation (WCF) adapter in Microsoft BizTalk Server 2006 R2
  
  • 943874 - FIX: You may experience time-outs when you use a receive location to connect to a WCF service and you use the WCF request-response adapter in BizTalk Server 2006 R2
  
  • 953995 - FIX: The WCF service that is generated may cause the IIS worker process to crash in a BizTalk Server 2006 R2 environment
  
  • 955522 - FIX: An event error is logged in the Application log when you stop a host that is running a WCF-based send adapter in a BizTalk Server 2006 R2 environment
  
  • 957622 - FIX: Text nodes in outgoing WCF message templates are ignored by the WCF Adapter in a BizTalk Server 2006 R2 environment
  
  • 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
  

WSS 

  
  • 957514 - FIX: You may receive an error message when you try to configure the Windows SharePoint Services adapter for Office SharePoint Server 2007 in a BizTalk Server 2006 R2 environment
  

LOB Adapters - # of Fixes 22

  

JD Edwards 

  
  • 939920 - FIX: Error message when you try to generate a schema for an adapter in BizTalk Server 2006: "Error reading WSDL file.[System.InvalidOperationException] There is an error in XML document (190, 41).[System.Xml.XmlException]"
  
  • 942420 - FIX: Some output messages may contain incorrect data when you use BizTalk Adapter for J.D. Edwards EnterpriseOne to process lots of messages in BizTalk Server 2006
  

Oracle Applications 

  
  • 941051 - FIX: A time-out error may occur when you use the BizTalk Adapter for Oracle Database as a receive adapter
  
  • 955456 - FIX: Event ID: 0 is logged when you use BizTalk Adapter for Oracle Database to send a batch of messages to an Oracle table, and a few messages are suspended
  

Oracle DB 

  
  • 934040 - FIX: One of the Microsoft BizTalk Adapters for Enterprise Applications stops processing incoming messages until you restart the BizTalk Host instance
  
  • 941726 - FIX: Error message when you use a BizTalk adapter to send messages on a computer that is running BizTalk Server: "Only one usage of each socket address (protocol/network address/port) is normally permitted"
  
  • 942419 - FIX: Event ID: 1723 occurs when you use Adapters for Enterprise Applications together with BizTalk Server 2006 or BizTalk Server 2006 R2 to process lots of messages
  
  • 943355 - Event ID 0 is logged in the Application log when you use Microsoft BizTalk Adapter for Oracle Database on a 64-bit server
  
  • 945307 - FIX: The BizTalk Server process may crash after you change the properties of BizTalk Adapters for LOB applications in BizTalk Server 2006
  
  • 959105 - FIX: Multiple RunTimeAgent processes are created when you use the Microsoft BizTalk Adapter for Oracle database to connect to an Oracle server
  
  • 971274 - FIX: Slow performance when you use the BizTalk Adapter for Oracle Database as a receive adapter in Microsoft BizTalk Server
  
  • 973453 - FIX: You receive a NullReferenceException exception when you use the Call Orchestration shape in BizTalk Server 2006 R2
  

SAP 

  
  • 955976 - FIX: You receive an error message and the application fails when SAP Adapter 2.0 generates a proxy by using ECC 6.0 in BizTalk Server 2006
  

SAP R2 

  
  • 934328 - Implementation of the OpenReuse value and the ReuseOpenConnection value in the BizTalk SAP adapter
  
  • 939885 - FIX: Error message when you use BizTalk Adapter 2.0 for mySAP Business Suite: "Unable to cast object of 'xxxx'"
  
  • 940563 - FIX: Multiple lines of an IDOC record are not parsed correctly in BizTalk Adapter for mySAP Business Suite
  

SAP SP1 

  
  • 931757 - FIX: BizTalk Adapter 2.0 for mySAP Business Suite may not release the connection to the SAP server as expected, and the messages may not be delivered
  
  • 959139 - BizTalk Editor cannot load schemas that are generated from Schema Generation Wizard of BizTalk Adapter 2.0 for mySAP Business Suite if the type attributes begin with numbers
  
  • 976622 - FIX: An orchestration instance is dehydrated, and messages are not sent to the SAP server when you use Microsoft BizTalk Adapter 2.0 for mySAP Business Suite
  

Siebel 

  
  • 956939 - FIX: Error event when you use the BizTalk Adapter for Siebel eBusiness Applications to send messages on a computer that is running BizTalk Server 2006 R2: "No connection could be made as target machine actively refused"
  

TIBCO JMS 

  
  • 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
  
  • 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
  

Solutions - # of Fixes 45

  

FileAct and Interact v2.3 

  
  • 942580 - FIX: The BizTalk FileAct and InterAct Adapters for SWIFT 2.3 unexpectedly release the SWIFTNet SnF queue when you configure the adapters to use the SnF mode
  
  • 945118 - FIX: A response message may be incorrectly matched to an original message when you send multiple messages by using the BizTalk FileAct and InterAct Adapters for SWIFT 2.3
  

FileAct and Interact v2.3 SP1 

  
  • 947981 - FIX: Event ID 1000 occurs when you try to start a 32-bit SNL receiver process on a computer that is running the 64-bit version of BizTalk Server 2006 R2
  
  • 949217 - FIX: The returned Sw-HandleSnFRequest response flags the message ACK as invalid when you use the BizTalk FileAct and InterAct Adapters for SWIFT 2.3 in BizTalk Server 2006 R2
  
  • 970194 - FIX: A Message Disposition Notification (MDN) is not received when the compression feature is enabled for the AS2 adapter in Microsoft BizTalk Server
  

HL7v2.0 

  
  • 941261 - FIX: Event ID 5720 is logged when you specify the BTAHL72XPipeline pipeline in a send port in BizTalk Server 2006 R2
  
  • 941279 - FIX: Event ID 5784 and event ID 5753 are logged when you create a custom pipeline that uses the BizTalk Accelerator for HL7 2.x assembler/disassembler in BizTalk Server 2006 R2
  
  • 942735 - FIX: Error message when you use the BTAHL72XMLSendPipeline send pipeline to generate a 2.XML message in the BizTalk Accelerator for HL7 2.0: "Message is not a 2.Xml document"
  
  • 949781 - FIX: Event ID 4133 and event ID 5802 are logged when you use BizTalk Server Accelerator for HL7 v2 in a BizTalk Server 2006 R2 environment
  
  • 961020 - FIX: Event IDs 5812, 5743, and 5754 are logged when you use BizTalk Accelerator for HL7 2.0
  
  • 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
  
  • 971924 - Enabling tracking on an MLLP receive port or BTAHL72XReceivePipeline fails to save the inbound message
  
  • 974265 - FIX: Error message when you receive an 837 document in BizTalk Server 2006 R2: "Missing or invalid or duplicate Transaction set identifier"
  

HL7v2009 

  
  • 970492 - FIX: A BizTalk host instance consumes lots of memory and processes messages very slowly when BizTalk Server 2009 receives lots of HL7 messages
  

RosettaNetv3 

  
  • 939014 - FIX: A trade partner may reject a 0A1 message when you use BizTalk Accelerator for RosettaNet 3.0 or BizTalk Accelerator for RosettaNet 3.5 to send the 0A1 message to the trade partner
  
  • 944749 - FIX: Error messages may be logged when you use BizTalk Accelerator for RosettaNet 3.0 or for RosettaNet 3.5
  
  • 945107 - FIX: The HTTP header field for a signed RNIF 2.0 document incorrectly contains the multipart/related value in BizTalk Accelerator for RosettaNet 3.5 or in BizTalk Accelerator for RosettaNet 3.0
  
  • 970491 - FIX: Negative Acknowledgement (NACK) messages that contains an invalid DateTimeStamp value are not rejected in BizTalk Accelerator for RosettaNet (BTARN) 3.0
  

RosettaNetv3.3 

  
  • 938839 - FIX: A trade partner may reject an RNIF 1.1 document or an RNIF 2.0 document that you generate by using BizTalk Accelerator for RosettaNet 3.3 or for RosettaNet 3.5
  
  • 940753 - FIX: The 0A1 PIP message also incorrectly contains a namespace declaration when you use BizTalk Accelerator for RosettaNet 3.3 or BizTalk Accelerator for RosettaNet 3.5
  
  • 940868 - FIX: An incorrect value is generated in the UniversalResourceIdentifier field when you process PIPs to send a message that includes attachments to a trading partner in BizTalk Server 2006 and in BizTalk Server 2006 R2
  
  • 940950 - FIX: A trade partner may reject a 0A1 PIP message when you use BizTalk Accelerator for RosettaNet 3.3 or 3.5 to send the 0A1 message to the trade partner
  
  • 944749 - FIX: Error messages may be logged when you use BizTalk Accelerator for RosettaNet 3.0 or for RosettaNet 3.5
  
  • 945107 - FIX: The HTTP header field for a signed RNIF 2.0 document incorrectly contains the multipart/related value in BizTalk Accelerator for RosettaNet 3.5 or in BizTalk Accelerator for RosettaNet 3.0
  

RosettaNetv3.5 

  
  • 938839 - FIX: A trade partner may reject an RNIF 1.1 document or an RNIF 2.0 document that you generate by using BizTalk Accelerator for RosettaNet 3.3 or for RosettaNet 3.5
  
  • 939014 - FIX: A trade partner may reject a 0A1 message when you use BizTalk Accelerator for RosettaNet 3.0 or BizTalk Accelerator for RosettaNet 3.5 to send the 0A1 message to the trade partner
  
  • 940753 - FIX: The 0A1 PIP message also incorrectly contains a namespace declaration when you use BizTalk Accelerator for RosettaNet 3.3 or BizTalk Accelerator for RosettaNet 3.5
  
  • 940868 - FIX: An incorrect value is generated in the UniversalResourceIdentifier field when you process PIPs to send a message that includes attachments to a trading partner in BizTalk Server 2006 and in BizTalk Server 2006 R2
  
  • 940950 - FIX: A trade partner may reject a 0A1 PIP message when you use BizTalk Accelerator for RosettaNet 3.3 or 3.5 to send the 0A1 message to the trade partner
  
  • 942849 - The Configuration.exe configuration program cannot be started and no error is recorded in the event log after you install the BizTalk Accelerator for RosettaNet 3.5
  
  • 945107 - FIX: The HTTP header field for a signed RNIF 2.0 document incorrectly contains the multipart/related value in BizTalk Accelerator for RosettaNet 3.5 or in BizTalk Accelerator for RosettaNet 3.0
  
  • 954663 - FIX: An event ID 0 error message is logged in the BizTalk Server Application log when you receive RNIF documents from a trading partner in BizTalk Accelerator for RosettaNet 3.5
  
  • 955240 - FIX: Event ID 4096 is logged in the BizTalk Server Application log when you use BizTalk Accelerator for RosettaNet 3.5 to receive a 3A4 PIP message from a partner
  
  • 955705 - FIX: The "Encode all parts" option does not work in BizTalk Server 2006 R2
  
  • 957684 - FIX: Event ID 4096 is logged in the BizTalk Server Application log when you use BizTalk Accelerator for RosettaNet 3.5 to receive a 3A4 PIP message from a trading partner and when the value of the MonetaryAmount element is less than 1
  
  • 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
  
  • 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
  
  • 972853 - FIX: A hotfix is available that lets you remove white spaces in outgoing messages for BizTalk Accelerator for RosettaNet (BTARN) 3.5
  

SWIFTv3.0 

  
  • 946043 - FIX: You cannot click to select some check boxes in the installation wizard when you try to install BizTalk Accelerator for SWIFT 3.0 on a server that has BizTalk Server 2006 R2 installed
  
  • 949912 - FIX: Event ID: 10034 may be logged when you use BizTalk Accelerator for SWIFT 3.0 together with a 64-bit version of BizTalk Server 2006 R2 on a computer that is running a 64-bit version of Windows Server 2003
  
  • 950536 - Event ID 10034 was logged when I used BizTalk Accelerator for SWIFT 3.0 together with BizTalk Server 2006 R2
  
  • 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
  
  • 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"
  
  • 971998 - FIX: BizTalk Accelerator for SWIFT 3.0 support for the MT202COV and MT205COV message types of the SWIFT 2009 Standard
  

Comments

  • Anonymous
    January 29, 2010
    I wanted to add an additiona info about the Biztalk 2004 and Biztalk 2006 fixes included in R2 SP1.These were fixes that were released on the other versions and included in R2 SP1.  They do not have an individual forward/back port to R2.  The goal is to ensure that R2 SP1 has all fixes (available in all other versions) available for R2 customers, as this is our largest customer base.-Guru