January 23, 2004
**********************************************************************
© 2004 Microsoft Corporation. All rights reserved.
**********************************************************************
Welcome to Microsoft® BizTalk® Server 2004. This Readme contains important, late breaking information about this release of BizTalk Server 2004.
Prior to installing BizTalk Server 2004, you must review this document, as well as "BizTalk Server 2004 Installation Guide," which provides instructions for installing BizTalk Server 2004, and is located in the root directory of BizTalk Server 2004 installation CD.
For information about current known issues in BizTalk Server 2004, see Knowledge Base article 834624 located at http://go.microsoft.com/fwlink/?LinkId=22784.
A documentation set is provided with this product. To use the documentation after you install BizTalk Server, click Start, point to All Programs, point to Microsoft BizTalk Server 2004, and then click BizTalk Server Documentation.
To ensure adequate performance, verify that the computers on which you install BizTalk Server 2004 meet the recommended hardware requirements and that all required software has been installed in the correct order. For information about hardware and software requirements for BizTalk Server 2004, see "BizTalk Server 2004 Installation" in the root directory of the BizTalk Server 2004 installation CD.
The following topics contain installation and configuration information not available in BizTalk Server 2004 Help:
The Base EDI Adapter service may not start if the EDI database is on a remote SQL Server. You must install the SQL Server Client Tools on the computer where the Base EDI Adapter service is running.
BizTalk Server 2004 is in an active-active configuration by design, without clustering. All servers are able to receive, process, and send messages.
If Enterprise Single Sign-On fails to start on a cluster, check the event log for ENTSSO service account permissions and modify the permissions as needed.
To check ENTSSO account permissions
If you use Microsoft® SQL Server 2000 Desktop Engine (MSDE) for the Credential database, and you are using an individual account as the Single Sign-On (SSO) Administrator account, you may receive database access errors indicating that the logged in user already has an account under a different user name.
If you are using MSDE, you cannot use an individual account for the SSO Administrator. You must use a group account.
For more information about working with SSO accounts, see the "SSO Accounts" topic in "BizTalk Server 2004 Configuration" in the Deployment node of BizTalk Server 2004 Help.
During the installation of Microsoft® Visual Studio® .NET 2003, a prerequisite for BizTalk Server 2004, write permissions are automatically granted to the Network Service account for the folder %SystemRoot%\temp.
The following error message may appear during configuration:
Failed to deploy BizTalk system assembly "C:\Program Files\Microsoft BizTalk Server 2004\Microsoft.BizTalk.DefaultPipelines.dll. Unspecified exception: File or assembly name <file name>.dll, or one of its dependencies, was not found."
If this error message appears, you must either install Visual Studio .NET 2003 on the target computer or grant the required permissions manually to the temp folder and then rerun configuration.
If you want to use Health and Activity Tracking (HAT) Analysis (OLAP) databases in a multiple-computer installation scenario, you must install the Microsoft SQL Server Administrative Tools on the computer used to create the BizTalk group during the installation process.
The SQL Server Administrative Tools are required to create the Analysis databases. For more information, see the topic "Installing Prerequisite Software" in the document "BizTalk Server 2004 Installation Guide," located in the root directory of BizTalk Server 2004 installation CD.
If you want to use the Business Activity Monitoring (BAM) utility manager to remotely administer an Analysis (OLAP) Services database, the connection to the database may fail.
To prevent this failure, select the following items in the Select Components dialog box during SQL Server 2000 Analysis Services installation:
In addition, ensure that you have installed Analysis Services with Service Pack 3a or greater.
If the Analysis Server is remote, the Configuration Wizard may fail during BAM configuration of OLAP objects.
To prevent this failure, select the following items in the Select Components dialog box during SQL Server 2000 Analysis Services installation: Decision Support Objects; Client components. In addition, ensure that you have installed Analysis Services with Service Pack 3a or greater.
The Base EDI database is the default database that stores EDI document tracking and processing data. During configuration, you may receive the error message: "The specified database is invalid. Enter a valid base EDI database or an empty database and one will be created for you."
To resolve this problem, delete the databases created during configuration, including the Base EDI database (named EDIdb in the default installation) and then re-run the Configuration Wizard. For more information, see "Removing BizTalk Server Configuration" in the BizTalk Server 2004 Configuration section in the Deployment node of BizTalk Server 2004 Help.
If the Analysis server is installed on a different computer than the one on which BizTalk Server 2004 resides, you must follow the instruction in the Knowledge Base article 231951, "Permissions that You Must Have to Administer an OLAP Server" located at http://go.microsoft.com/fwlink/?LinkId=22781.
If you configure the Single Sign-On (SSO) master secret server using the built-in domain administrator account, the current user and the SSO service account are not automatically added to the SSO Administrator group.
Ensure that these two accounts are members of the SSO Administrator group before you configure the SSO master secret server.
The Partner Edition of BizTalk Server is bundled with the Microsoft® Windows® Small Business Server (SBS) 2003 Premium Edition. To support SBS customers, BizTalk Server 2004 includes a predefined, custom setup script for the SBS 2003 Premium Edition. This file is named SetupforSBSPremium.vbs and is located in the root installation folder of the BizTalk Server 2004 Partner Edition. If you are installing the Partner Edition of BizTalk Server 2004 with the SBS Premium Edition, use this script to install BizTalk Server with these predefined, secure configurations.
The script runs a silent BizTalk Server installation and then automatically launches the Configuration Wizard with the predefined configuration for SBS. This script also creates the appropriate user accounts which are then used in the BizTalk Server 2004 configuration. These user accounts have secure, auto-generated passwords. These passwords are not documented, but local administrators can change them if needed.
Note The SBS scripts require Microsoft SQL Server and Analysis Services to be installed on the SBS Premium platform before running the SetupforSBSPremium.vbs script.
You can use the silent installation command-line options to install all features only. The BizTalk Server 2004 installation wizard presents several command-line options for installation. However, the only option supported is to install the entire feature list.
For example, the following command-line instructions are supported:
To perform a silent installation of subsets of features, you must save the configuration when performing an interactive installation that you would like to duplicate. To do this, click Save on the Configuration Summary page of the Configuration Wizard. The resulting file will be saved as an XML file that is passed into the file setup.exe through the command line using the /s option. For example: setup.exe /s config.xml.
It is recommended that you enable tracing in BizTalk 2004 to help diagnose and expedite the resolution of any troubleshooting issues that occur. For information about setting up tracing in BizTalk 2004, see Knowledge Base article 835451 located at http://go.microsoft.com/fwlink/?LinkId=23317.
BizTalk Server 2004 does not support Fully Qualified Domain Name (FQDN) notation for computer names.
If Network Basic Input Output System (NetBIOS) is disabled on the network, then you must use domain name system (DNS) or host files to identify computer names.
BizTalk Server 2004 configuration errors could occur due to naming restrictions for SQL Server and database properties. For SQL Server and database names, BizTalk Server 2004 supports the following character set: letters (A-Z, a-z), digits (0-9), hyphens (-), and underscores (_).
BizTalk Server 2004 supports the following naming restrictions for Messaging Engine message boxes:
BizTalk Server 2004 uses the following default ports:
| Feature | Port |
|---|---|
| Administration and deployment tools, Single Sign-On (SSO) | 135, 5000-5050 |
| FILE Adapter and OLAP Server | 445 |
| FTP | 21 |
| HTTP/SOAP | 80 |
| HTTPS/SOAP | 443 |
| MSMQ-T | 1801 |
| OLAP Server | 2725, 2393 |
| Rules Update Service | 3132 |
| SMTP | 25 |
| SQL Server and SQL Adapter | 1433 |
If these ports are not available (for example, if they are being used by another application) error messages will appear and the service attempting to use the port will not start or configure correctly.
Do not use quotation marks (") in passwords.
If you install and configure the Human Workflow Services (HWS) run time and Web service components under different user accounts, ASP.NET-related access errors may occur. This occurs in both single server and multiple server scenarios.
To resolve this issue, install and configure HWS run time and Web service components using the same account.
The section describes known issues with the BizTalk Server 2004 release.
For SQL adapters, currency parameters are not supported. You must write a stored procedure that accepts the currency value as a string parameter.
If you change the permissions of a folder designated as a receive location, and FILE adapters running under the BizTalk Server Engine service are unable to access the folder, no event error is logged to explain the failure.
HTTP GET requests do not accept any data after the characters "%00." For example, an HTTP receive location configured with the format /vdir/BTSHttpReceive.dll?aaa%00bbb will lose message data.
To avoid losing message data, use an HTTP POST request rather than an HTTP GET request.
| Back to Top |
The BizTalk Server Administration Console, which uses Windows Management Instrumentation (WMI) providers, may intermittently stop working on Windows 2000. This is a known issue in the Windows WMI Service.
If you experience this problem, it is recommended that you recycle or stop the WMI Service (winmgmt.exe). The service will restart automatically.
For additional information, see Knowledge Base Article 828756, "Deadlock When an ASP.NET Application Calls LoadLibrary() or FreeLibrary()" located at http://go.microsoft.com/fwlink/?LinkId=22697.
| Back to Top |
You use the Business Activity Monitoring (BAM) management utility, or BAM Manager, to deploy the run-time infrastructure on the server, which includes the BAM Primary Import database, Star Schema database, Analysis database, and the corresponding Data Transformation Services (DTS) packages.
If the deployment of the BAM OLAP cube update DTS package fails, check that the Microsoft® SQL Server Client Tools and Service Pack (SP) 3a or greater are installed.
The service account used for OLAP must be a member of the db_owner SQL role in the BAM Star Schema database.
If you perform a custom installation and install Development tools only, the file bm.exe.config is not installed and the file BAMconfiguration.xml is not created. An exception occurs and the following error messages are displayed:
BamConfiguration.xml is not a valid BAM Configuration XML file.
Could not find file C:\Program Files\Microsoft BizTalk Server 2004\Tracking\BamConfiguration.xml.
You must perform the following procedure to install the missing files.
To install and configure the missing files
<installation directory>\Tracking xcopy bm.exe.config.tmpl bm.exe.config xcopy BAMconfiguration.xml.tmpl BAMconfiguration.xml
Business Activity Monitoring (BAM) requires that the BAM Primary Import database and Business Activity Services (BAS) reside on the same server if the Query Web Service User is a local account.
| Back to Top |
Information about using Business Activity Monitoring (BAM) Microsoft Excel templates and the Business Activity Services (BAS) collaboration site is included in a separate Help file. You can access this file directly from the Help link on the Business Activity Services (BAS) Windows Server System (WSS) collaboration site.
However, if you did not install or do not use Business Activity Services, a copy of the Help file can be found at <root>\<installation directory>\Program Files\Microsoft BizTalk Sever 2004\Documentation\ KW_User_Guide.chm.
You cannot change the Business Activity Services (BAS) site name for an existing site using the Windows SharePoint Services Site Configuration page in SharePoint Central Administration.
| Back to Top |
Module 2 of the tutorial contains solution files that are automatically installed as part of the BizTalk Server 2004 installation. However, the tutorial does not provide instructions for setting up or using these files. If you follow the development and deployment steps in Module 2 of the tutorial included in BizTalk Server 2004 Help, you cannot use the setup script to set up and configure the B2B Solution.
A completed solution and a setup script are provided in the Solutions directory located at <installation directory>\SDK\Tutorial\Solutions. You can use this script to automatically configure the B2B Solution and test it. The setup script performs the following tasks:
To set up the complete B2B Solution
<root>\<installation directory>\Tutorial\Solutions\SupplierWebServices\Setup.bat
and
<root>\<installation directory>\Tutorial\Solutions\B2Bsolution\PaymentRules.xml.
Note If you are running Microsoft Windows Server 2003, you need to change the application pool for the exposed Web service to the TutorialAppPool created in the topic "Enabling BizTalk Web Services" of Module 2, Lesson 2, Phase 1.
| Back to Top |
If you change the Enterprise Single Sign-On(SSO) Administrators group from one group (for example, group1) to another group (group2), and, if group2 did not contain the SSO Service accounts when you started ENTSSO service, then you must restart the service to pick up the information regarding the new group. All SSO Service accounts must be a member of this group.
| Back to Top |
The Orchestration Compiler may fail if any project dependencies are not present in the global assembly cache (GAC).
For example, if you annotate .NET Framework classes with BizTalk message properties, in a managed code project, and then define a message part for which the type is the annotated .NET Framework class in an orchestration, project dependencies may be missing from the GAC. Under these conditions, the compiler may fail and the following error message will appear: "Class must be XML serializable to be a message part type."
If this occurs, place your orchestration project in a separate solution. Before you compile this solution, ensure that you have added all referenced assemblies to the GAC. Additionally, ensure that the versions you are referencing (either directly, or indirectly through other references) are all consistent with the versions present in the GAC. If all of the referenced assemblies are present in the GAC, and the versions are consistent, compile the orchestration project.
If a referenced assembly is missing, or there is an inconsistency in the versions, the compiler will fail and you must restart Visual Studio and repeat this process.
To avoid version inconsistencies, it is recommended that you edit the AssemblyInfo file in your managed code projects so that a specific version number is specified. It is recommended that you do not use the automatic version increment feature.
If one orchestration (OrchestrationA) contains a Web reference to a second orchestration (OrchestrationB) that you have already published as a Web service, when you deploy OrchestrationA, schemas associated with the port defined in OrchestrationB are deployed twice. Schemas not associated with that port are not deployed a second time.
When this situation occurs, the receive or send ports fail to receive or deliver the message, because the schema information is ambiguous. The following errors are generated in the Health Activity Tracking (HAT) tool and the Event Viewer:
For FILE adapters:
For HTTP adapter:
To resolve the duplicate schemas issue, you must reference the schema from a custom pipeline component. You cannot use default pipelines to do this.
When you use the BizTalk Message Queuing adapter (MSMQT) and set the OrderedDelivery property to TRUE in the Orchestration Designer, the OrderedDelivery property setting is not implemented at run time and, by default, messages will be delivered out-of-order.
If the corresponding port in the orchestration is physically bound to BizTalk Message Queuing, and the OrderedDelivery property is set to TRUE in the Orchestration Designer, you must set the OrderedDelivery property to TRUE on the ports created in BizTalk Explorer by the Deployment tool.
If you create a BizTalk Server Project in Visual Studio.NET that has an orchestration and associated receive port, and then you physically bind that port to a folder location (for example, C:\recv\*.xml) using the FILE transport, when the assembly is deployed, the receive location that points to C:\recv\ gets enabled by default.
Messages are then picked up and submitted to the MessageBox database. At this point, the orchestration is not yet enlisted; therefore, the subscription for any message just picked up is not created. This causes the MessageBox to suspend the message in a suspended, not resumable state.
To resolve this issue, eliminate any pre-existing messages in the receive location folder before enlisting the corresponding orchestration.
| Back to Top |
You can invoke a policy (or rule set) from an orchestration using the CallRules shape, and the policy will invoke the Rule Engine, which operates on the rules in the policy.
However, you must ensure that the DocumentType property for XML nodes used in your business rule (that you implement in the Rules Composer) is the same as the MessageType for those XML nodes defined in the orchestration it must match the MessageType of the message or message part that will be passed to the rule engine in the Call Rules shape.
For example, if you define a PO XML schema in a BizTalk project, the MessageType defined for this schema is BTSProject.PO (if BTSProject is the namespace or the project name using the default namespace).
In the case of the PO\Amount element, before you drop it into a rule definition, you must change its DocumentType property to BTSProject.PO in the properties window. You can access the properties window when any node in the schema is selected in the XML Schemas tab in the Fact Explorer. This change will be applied for all elements in the schema, but is not persisted with the schema. It must be reset when the Composer is launched or the schema is reloaded. This is required for vocabulary definitions based either on XML schema or based on XML nodes directly from XML schema. It is required for both building rules directly from the schema or building vocabulary definitions.
For a single computer BizTalk Server 2004 installation, only one central SQL Server-based rule store is installed. It is possible that multiple Rules Composer users could connect to this shared rule store at the same time to do the following:
Currently the Rules Composer and Business Rule Engine Application Programming Interfaces (APIs) do not provide mechanisms to do the following:
Any schemas passed as facts in the BizTalk Rule Engine to the Rules Set are not validated against the schema before any facts using selectors are asserted. To avoid this issue, you must validate all input passed while running a policy.
| Back to Top |
Information in this document, including URL and other Internet Web site references, is subject to change without notice. Unless otherwise noted, the example companies, organizations, products, domain names, e-mail addresses, logos, people, places, and events depicted herein are fictitious, and 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.
Microsoft, MS-DOS, Active Directory, SharePoint, Windows, Windows NT, Windows Server, BizTalk, Visual C#, and Visual Studio are either registered trademarks or trademarks of Microsoft Corporation in the United States and/or other countries.
The names of actual companies and products mentioned herein may be the trademarks of their respective owners.