You must first install the BizTalk Server 2004 Administration tools on your Business Activity Services (BAS) computer before you upgrade the BAS portal to BizTalk Server 2006. If you don't do this, the upgrade may fail.

Problem: When you restore a database, the restore operation does not correctly update the list of databases and servers referred to by the upgrade process.

The adm_otherdatabases table in the BizTalk Management database contains the names of the servers and databases in the BizTalk group. It is used specifically to locate other databases when you upgrade or patch your system. So an upgrade from BizTalk Server 2004 or beta versions of BizTalk Server 2006 may fail if in the past you restored the BizTalk group from a backup version.

This problem occurs in the following upgrade paths:

• BizTalk Server 2004 Service Pack 1 (SP1) to BizTalk Server 2006 Beta 1
  
  
• BizTalk Server 2004 SP1 to BizTalk Server 2006 Beta 2
  
  
• BizTalk Server 2004 SP1 to BizTalk Server 2006
  
  
• BizTalk Server 2006 Beta 2 to BizTalk Server 2006 (general released version)
  
  

Solution: After you restore a database, ensure that the server and database names are correct in the adm_otherdatabases table in the BizTalk Management database. You can manually correct the names of the servers and databases in the adm_otherdatabases table if necessary.

For additional information about upgrading from the Microsoft BizTalk Server 2006 Beta 1 version to the Beta 2 version, see the Microsoft BizTalk Server 2006 Beta 2 Installation Instructions available on the Internet.

The following constraints exist for using MSI files built in the Beta 1 version in BizTalk Server 2006 Beta 2:

• In the Beta 2 version, you cannot install any MSI files that were created in Beta 1. However, you can import these MSI files.
  
  
• In the Beta 2 version, you cannot uninstall any MSI file that you installed in Beta 1.
  
  

To ensure that you can work with your MSI files after you upgrade, we recommend that you perform the following steps before upgrading:

1. Ensure you have back-up copies of your resources.
   
   
2. Open the BizTalk Administration console, and identify any applications that have resources of type preprocessingscript or postprocessingscript or file.
   
   
3. Delete those resources, and then add them back to the application. The resources should have been installed to the hard disk when you set up the application, so you can add them from there.
   
   
4. Uninstall all the BizTalk Server applications that were installed. Although you are uninstalling the applications from the hard drive, they will not be deleted from the BizTalk Management database.
   
   
5. Now upgrade to the Beta 2 version. This will upgrade the BizTalk Management database.
   
   
6. Export all your applications to MSI files.
   
   
7. Install all of the MSI files that you exported in step 6. Your BizTalk Server application is now usable.
   
   

After you upgrade from the Beta 1 version to Beta 2, perform the following steps to ensure that all of your Beta 1 functionality has been preserved.

You must install Microsoft SQL Server Client Tools before installing BizTalk Server. If BizTalk Server Beta 2 is already installed, you must remove Microsoft Office Web Components (OWC) before installing SQL Server Client Tools.

For multicomputer deployments of the Base EDI adapter, where SQL Server 2005 is on a different computer than the BizTalk Server 2006 runtime, you must install one of the following in the runtime environment:

• SQL Server 2005 Database Services.
  
  
• SQL Server Management Studio or SQL Server 2005 Database Services: Install one of these on the runtime server, but only if you have a multicomputer deployment using SQL Server 2005.
  
  
• Client connectivity component of SQL client tools: This is required for all deployments, whether SQL Server 2000 or SQL Server 2005.
  
  

Problem: You cannot configure the Base EDI Adapter if you are using a local non-administrative account for the EDI subsystem. The EDI subsystem service fails to start.

Solution: Add the local service account that you want to use for the Base EDI Adapter subsystem to the BizTalk Server Administrators group that is created during group configuration. After you do this, the EDI subsystem service starts normally.

After configuring alerts on SQL Server 2005, you must execute the following command on the BAM Alerts Application database to grant appropriate privileges to the Notification Services user:

GRANT SELECT ON [dbo].[bam_Metadata_AlertInstance] TO NSRunService

Otherwise, the BAM instance alert will not work.

Problem: If you have both Microsoft .NET Framework version 1.1 and version 2.0 installed on your computer, you will get the following error message when you use the Web Services Publishing Wizard to create a virtual root (vroot folder):

Configuration Error 
Description: An error occurred during the processing of a 
configuration file required to service this request. Please review 
the specific error details below and modify your configuration file
appropriately. 

This error occurs because the Web Services Publishing Wizard creates a virtual root and configures the web.config file to use ASP.NET version 2.0. To browse an .asmx file, ASP.NET must use version 2.0, rather than version 1.1.

If your Web site is configured to use ASP.NET version 2.0, you can create and browse the individual virtual root. However, if it is configured to use ASP.NET version 1.1, an error results.

Solution: When you publish an orchestration as a Web service to the Web site, ensure that the Web site you are publishing to is using ASP.NET version 2.0 and not version 1.1. You can do this even after you have published an orchestration.

To change your configuration to use ASP.NET version 2.0:

1. In the Run box, type inetmgr.
   
   
2. Navigate to the Web site, and right-click Properties.
   
   
3. Click the ASP.NET tab.
   
   
4. In the ASP.NET version box, select the 2.0 version, and then click OK.
   
   

Problem: If you have installed the COM+ hotfix, MS05-051: Vulnerabilities in MSDTC and COM+ could allow remote code execution, on a 64-bit computer, you may encounter the following error while deploying or configuring BizTalk Server, or while using the BizTalk Administration Console:

The ServicedComponent being invoked is not correctly configured 
Use regsvcs to re-register).

After getting this error, if you try to restart the COM+ system application service from the Service Control manager, it fails.

Solution: Perform the following steps to reinstall COM+ components:

1. From the Start menu, click Control Panel, double-click Add or Remove Programs, and then click Add/Remove Windows Components.
   
   
2. In the Windows Component Wizard, highlight Application Server, and then click Details.
   
   
3. Verify that Enable network COM+ access is selected, click OK, and then click Next.
   
   
4. Click Finish to close the Windows Components Wizard.
   
   
5. Restart the COM+ System Application service, and restart the BizTalk services using the Service Control Manager.
   
   

Problem: The Base EDI Adapter service process esp_srv.exe continues to grow in memory size even if the adapter is not processing any documents. For example, when you monitor the process in Performance Monitor, you may see an increase of approximately 12288 bytes every 8 to 12 seconds. This memory leak is bigger when a non-existent path is specified for the EDI pickup location in the EDI receive handler.

Solution: Periodically restart the Base EDI Adapter service. If the Base EDI Adapter service is not actively being used, stop the service, and set it to Manual so that the service does not start up automatically upon a reboot.

Problem: You cannot debug an orchestration. After setting a breakpoint in an orchestration, when you try to "Attach" to the orchestration in the orchestration debugger, you get the following error: No such Host is found.

This problem only occurs in the following scenario: You are using Microsoft SQL Server 2000 to host your BizTalk Tracking database, and your BizTalk Server is in a Workgroup mode.

Solution: Either add your server to a Microsoft Active Directory domain, or use SQL Server 2005 instead of SQL Server 2000.

Problem: Microsoft Operations Manager (MOM) 2005 Service Pack 1 (SP1) currently does not support SQL Server 2005.

Solution: If you plan to deploy the BizTalk Management Pack for BizTalk Server 2006, use SQL Server 2000 for your MOM databases. For more information, see the Microsoft Operations Manager Web site.

When you import an application, if the MSI file contains BAS resources, a dialog box appears. While the dialog box is present, the database is locked and runtime is blocked.

Do not start an import process and then leave your console unattended.

This Beta 2 release includes the following new SDK samples:

• Error Handling
  
  
• Composed Message Processor
  
  
• Aggregator
  
  
• OperationsOM
  
  

To use these samples, follow the instructions in the "Samples" documentation found in the "Developing" node of BizTalk Server 2006 Help. The instructions are accurate.

The documentation for all other SDK samples, however, is incorrect. If you try to run the samples using the documentation, the samples will not work.

The following SDK sample does not work with the Beta 2 release:

• HTTP.NET Adapter SDK Sample
  
  

Problem:If you start the Human Workflow Services (HWS) Server Administration after you have configured the Human Workflow Services (HWS) Runtime and HWS Web services, you may get the following error:

The selected server does not exist or does not have a valid Human Workflow Services installation.

Solution: Restart the WMI service in services.msc.

Problem: By default, network Distributed Transaction Coordinator (DTC) access is disabled on Microsoft Windows Server 2003 and Windows XP with SP2.

Solution: Before configuring Beta 2, you must enable DTC access on the computer.

When you make the following changes, ensure that all servers in your environment have compatible settings. For example, if you configure your BizTalk server to No Authentication Required because it is running on a Windows Server 2003 server without SP1, you must make sure that your SQL Server computer is also set to No Authentication Required, even if it is running under Windows Server 2003 with SP1.

To enable DTC access for Windows Server 2003 with SP1 or Windows XP with SP2, do the following:

1. From the Start menu, click Control Panel, double-click Administrative Tools, and then double-click Component Services.
   
   
2. Expand Component Services, and then expand Computers.
   
   
3. Right-click the computer you need to set, and then select Properties.
   
   
4. In the Properties window, select the MSDTC tab.
   
   
5. In the Transaction Configuration area, click Security Configuration.
   
   
6. In the Security Settings area, select the Network DTC Access check box.
   
   
7. In the Transaction Manager Communication area, select the Allow Inbound and the Allow Outbound check boxes.
   
   
8. Click OK to close each open dialog box.
   
   
9. Restart your computer to enable the remote DTC option.
   
   

To enable DTC access for Windows Server 2003 without SP1, do the following:

1. From the Start menu, double-click Control Panel, double-click Administrative Tools, and then double-click Component Services.
   
   
2. Expand Component Services, and then expand Computers.
   
   
3. Right-click the computer you need to set, and then select Properties.
   
   
4. In the Properties window, select the MSDTC tab.
   
   
5. In the Transaction Configuration area, click Security Configuration.
   
   
6. In the Security Settings area, select the Network DTC Access check box.
   
   
7. In the Security Settings area, select the Network Transactions and Network Clients check box.
   
   
8. Ensure Allow Remote Clients is selected, and ensure No Authentication Required is selected.
   
   
9. Click OK to close each open dialog box.
   
   
10. Restart your computer to enable the remote DTC option.
    
    

Problem: When you access the Group Hub page on the BizTalk Administration console and you refresh the page or run certain queries, a SQL Server DateTime overflow exception may appear. This problem occurs only if you are in a time zone that is ahead of Coordinated Universal Time (UTC, also known as Greenwich Mean Time). That is, this error occurs if your local time is UTC + n hours.

Solution: Set the time on your computer to either UTC or to a time zone that is behind UTC; that is, UTC - n hours. Change the clock time before opening the Administration console, or open a new Administration console window, so that the changes are in effect. After you do this, users can reset the clock on their computer back to their original GMT+ time.