BizTalk Server 2006 R2 has the following known issues:

• Issue: If SQLXML 3.0 SP2 is installed on the computer, BizTalk Server 2006 R2 installation or upgrade will fail when attempting to install SQLXML 3.0 SP3 during Platform pre-req installation.
  
  If you encounter this issue during installation or upgrade of BizTalk Server 2006 R2, you must uninstall SQLXML 3.0 SP2 and then install or upgrade to BizTalk Server 2006 R2.
  
  
• Issue: On a computer running Windows Vista™ with Microsoft SQL Server™, computer names shorter than seven characters will cause BizTalk Configuration to return "(local" as the default SQL Server name on custom configuration user interfaces.
  
  If both BizTalk Server and SQL Server 2005 are installed on a computer running Windows Vista, and the computer name is shorter than seven characters, the default SQL Server name will appear as "(local" on the BizTalk Server custom configuration user interfaces. You can either rename the computer with a name that is longer than 7 characters or manually change the database server name with the computer name on BizTalk Server custom configuration user interfaces so that you can complete the configuration.
  
  
• Issue: BizTalk Server will not save changed filter settings for a batch in progress if you attempt to save the start time.
  
  If you update the filter settings for a batch in progress, and the start time is in the past, BizTalk Server will display a dialog box asking you whether you want to save the start date time for the batch. (You update filter settings by changing the properties in the Batch Filter page of the EDI Properties dialog box; the start date time is set in the Interchange Batch Creation Settings page.) To save the filter settings, you must click No. You cannot save the start time for a batch in progress, so clicking Yes will not save the start time, and it will also not save the filter settings. For a batch that is not in progress, selecting either No or Yes will update the filter settings.
  
  
• Issue: The Application Deployment SDK Sample for EDI Schema is only applicable to the Base EDI during upgrade.
  
  For a clean installation, only the new EDI functionality is installed, and the Base EDI components are not installed; therefore this SDK is applicable only for upgrade scenarios.
  
  
• Issue: GetEndpointName does not get the endpoint name for the client.
  
  The endpoint name retrieved by the GetEndPointName task is not the endpoint specified in the client but the binding followed by an underscore and the contract name. For the service, however, it is the endpoint name specified in the App.config file as expected.
  
  
• Issue: You cannot view the message body of a suspended duplicate X12 or EDIFACT message that contains multiple interchanges.
  
  If an X12 or EDIFACT EDI message with multiple interchanges is received, and it is suspended because it is a duplicate message, you cannot view the message body when viewing details of the suspended message. This is an issue with the default EDI or EDI/AS2 receive pipelines.
  
  This occurs when the DetectMID property is set to "True" in the receive pipeline properties (to process multiple interchanges in a message), and the Check for Duplicate ISA13 party property is checked in the X12 Interchange Processing Properties page or the Check for Duplicate UNB5 party property is checked in the EDIFACT Interchange Processing Properties page (to reject an interchange with a duplicate interchange control number).
  
  The problem occurs if you have taken these steps: when you click "Suspended service instances" in the Group Hub page, double-click a message in the Suspended page, click the Messages tab, double-click the message in the Service Details dialog box, and then click "Body" in the console tree. The message body will not be displayed in the Body pane.
  
  You can avoid this issue by setting the DetectMID pipeline property to "False". However, when you do so the receive pipeline will not process multiple interchanges within a single physical message. It will process only the first interchange. The remaining data after the first interchange will be suspended.
  
  
• Issue: In a failover cluster scenario involving the WCF-NetMsmq adapter, you must start the MSMQ cluster resource before starting the BizTalk clustered host resource.
  
  When a failover occurs in a failover cluster scenario, you must start the MSMQ cluster resource before starting the BizTalk clustered host. Otherwise the WCF-NetMSMQ Receive location will be disabled. You must restart the BizTalk clustered host to re-enable the WCF-NetMSMQ Receive location.
  
  To ensure that the MSMQ cluster resource starts before the BizTalk clustered host, you must make the BizTalk clustered host dependent on MSMQ cluster resource using the Cluster Management Console.
  
  
• Issue: Character-count-based batching that is scheduled to terminate at a certain time does not release the last batch. The last batch with all of its input messages is trapped in the orchestration, which gets suspended after the termination time.
  
  This issue is not observed for character-count-based batching that has no termination date time or character-count-based batching that terminates after a fixed number of batch releases.
  
  
• Issue: You cannot create batched EDIFACT messages if "Generate UNA Segment" is not checked on the “UNA Segment Definition” Properties page under the “EDIFACT Interchange Envelope Generation” of the EDI Property pages of the party performing the batching.
  
  To generate an EDIFACT batched message, you must select Generate UNA Segment on the UNA Segment Definition Properties page for that party.
  
  
• Issue: Use of the Base EDI adapter with BizTalk Server 2006 R2 on Windows Vista is unsupported.
  
  If you have an installation of BizTalk Server 2006 (with the Base EDI adapter) on Windows Server 2000, Windows XP, or Windows Server® 2003, you can upgrade the installation to BizTalk Server 2006 R2 on Windows Vista. If you do so, the Base EDI adapter will be installed. However, use of the Base EDI adapter in that upgraded installation will be unsupported.
  
  
• Issue: In BizTalk RFID Beta 2, the Device Service Provider Interface (DSPI) does not support default values in the properties of array type.
  
  While creating RfidEntityMetadata, a developer must pass null as the default value in properties of array type.
  
  
• Issue: Disabling anonymous access in Internet Information Services (IIS) Manager can cause BizTalk RFID provider processes to fail.
  
  In Windows Server 2003, in Internet Information Services (IIS) Manager, the authentication method for BizTalk RFID providers and for process-related virtual directories is set to anonymous access. Disabling anonymous access for these providers or directories may cause the provider or the corresponding process to fail.
  
  
• Issue: You cannot resume a batch orchestration after termination of a suspended instance of this service.
  
  If an instance of the batching orchestration is suspended, there is a control in the Interchange Batch Creation Settings page to resume the batching orchestration. If you terminate the suspended orchestration instance in the Group Hub page, and then refresh the Interchange Batch Creation Settings page, you can click the Resume button. However, this action may not succeed in re-starting the batching orchestration. If so, you have to click the Stop button, and then click the Start button to restart the orchestration. When you click the Start button, you also have to select the command to reset the start date time to the current time, or the orchestration will be not started. However, if you change any other setting on the Interchange Batch Creation Settings page, you can start the orchestration without resetting the time to the current time.
  
  
• Issue: BizTalk Server 2006 Orchestration Designer for Business Analysts (ODBA) is not supported on Microsoft Office Visio 2007.
  
  For more information about ODBA requirements or to download ODBA, see BizTalk Server 2006 Orchestration Designer for Business Analysts at http://go.microsoft.com/fwlink/?LinkID=63132.
  
  
• Issue: Future releases of BizTalk Server 2006 R2, starting with R2 Beta 2, will not support Base EDI adapter technology, as this technology is being deprecated.
  
  You will be required to use EDI Pipelines and associated technology for EDI Protocol support.
  
  

  Note
  Components of the Base EDI adapter technology are installed in the folder <drive>:\Program Files\Microsoft BizTalk Server 2006\EDI, and include the following: EDI adapter (Send and Receive); EDI Reports in Reporting node in HealthAndActivityTracking infrastructure; and XSD Schemas with CovastEdiSchemaEditorExtension.

• Issue: The BAM tools page appears with an error icon if an already configured BAM Alerts service account is changed through the View or Edit Service accounts.
  
  Instead, use Nscontrol to change accounts to change BAM Alerts service accounts.
  
  
• Issue: If an attempt to configure the BAM portal fails, the BAM portal configuration shows all controls disabled.
  
  To access the BAM portal configuration options, use the bm.exe update-config command without a portal address in the xml file.
  
  
• Issue: When using the WCF-WSHttp Send-Adapter (Transactional Only) under high load, the send host can appear to leak memory and handles. This is because the MSDTC Log-File-Size capacity setting is too low. By default, the MSDTC Log-File-Size capacity is set to 4 MB. You can avoid this problem by raising the value of the capacity. The maximum possible value is 512 MB.
  
  To increase the value of the MSDTC Log-File-Size capacity

  1. Click Start, point to Programs, point to Administrative Tools, and then click Component Services.

  2. Expand Component Services, expand Computers, right-click My Computer and then click Properties.

  3. In the Properties dialog box, on the MSDTC tab, in the Log Information section, change the value for Capacity.

If you have technical questions about BizTalk Server 2006 R2 not answered in this document or in the Microsoft Knowledge Base articles, Microsoft offers technical support and services.

Product name: Microsoft BizTalk Server 2006 R2

Support options: To obtain the latest information about your support options, see the Help and Support Web site at http://go.microsoft.com/fwlink/?LinkId=36792.

Worldwide support: Options, hours, and cost in your country or region may differ from the United States; contact your local office for details.

Conditions: Technical support services are subject to the then-current prices, terms, and conditions at Microsoft, which are subject to change without notice.

Information in this document, including URL and other Internet Web site references, is subject to change without notice. Unless otherwise noted, the companies, organizations, products, domain names, e-mail addresses, logos, people, places, and events depicted in examples herein are fictitious. No association with any real company, organization, product, domain name, e-mail address, logo, person, place, or event is intended or should be inferred. Complying with all applicable copyright laws is the responsibility of the user. Without limiting the rights under copyright, no part of this document may be reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any means (electronic, mechanical, photocopying, recording, or otherwise), or for any purpose, without the express written permission of Microsoft Corporation.

Microsoft may have patents, patent applications, trademarks, copyrights, or other intellectual property rights covering subject matter in this document. Except as expressly provided in any written license agreement from Microsoft, the furnishing of this document does not give you any license to these patents, trademarks, copyrights, or other intellectual property.

© 2007 Microsoft Corporation. All rights reserved.

Microsoft, MS-DOS, Windows, Windows Server, Windows Vista, BizTalk, Microsoft Dynamics, and Windows Server System are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.

All other trademarks are property of their respective owners.