This document contains installation instructions and information about Microsoft® BizTalk® Server 2002 Service Pack 1 (SP1). The latest version of this document is available on the BizTalk Server 2002 Service Pack 1 documentation site.
Important It is strongly recommended that you read this entire document before you install Service Pack 1.
This document provides information about the following:
Note the following requirements:
Important Service Pack 1 setup requires the original BizTalk Server 2002 installation source (Microsoft BizTalk Server.msi) to be available.
You must have BizTalk Server 2002 installed before installing Service Pack 1. This section contains information about the operating systems supported by BizTalk Server 2002 SP1.
The following platforms are supported for BizTalk Server 2002 SP1:
This section contains information about using BizTalk Server 2002 SP1 on Windows 2000.
The following software must be installed before installing BizTalk Server 2002 SP1 on Windows 2000:
Note All servers in a BizTalk Server application farm must be using the same MDAC version.
To enable the use of the certificate revocation list (CRL) with BizTalk Server 2002 SP1 on Windows 2000 or Windows XP, you need to apply a Windows hotfix referred to in Microsoft Knowledge Base article 329433. To obtain this hotfix, contact Microsoft Product Support, as listed in the About Product Support section in this document. After the hotfix is applied, BizTalk Server SP1 can verify that a certificate is valid and has not been revoked by the certificate issuer.
The registry key used to enable or disable CRL checking is:
A value of 1 indicates that CRL checking is enabled, and a value of 0 indicates that CRL checking is disabled. If this registry key does not exist on a computer with SP1 installed, CRL checking is enabled by default.
This section contains information about using BizTalk Server 2002 SP1 on Windows XP.
Note BizTalk Server 2002 SP1 should only be installed on Windows XP as a tools installation for development purposes.
The following software must be installed before installing BizTalk Server 2002 SP1 on Windows XP:
Note All servers in a BizTalk Server application farm must be using the same MDAC version.
This section contains information about using BizTalk Server 2002 SP1 on Windows Server 2003.
The following software must be installed before installing BizTalk Server 2002 SP1 on Windows Server 2003:
Before installing BizTalk Server 2002 SP1 on Windows Server 2003, ensure that the following tasks are completed:
On Windows Server 2003, additional configuration is necessary to enable BizTalk Server 2002 to work in configurations where SQL Server is installed on a different computer. This scenario requires you to enable network Distributed Transaction Coordinator (DTC) access on both servers. For information about enabling network DTC, see Microsoft Knowledge Base article 817064.
This section includes information about configuring IIS for BizTalk Server 2002 HTTP receive functions on Windows Server 2003.
Note The HTTP receive functions support running either in native IIS 6.0 mode or in IIS 5.0 isolation mode.
To configure IIS 6.0
Note The selected user must belong to the IIS Worker Process Group (IIS_WPG).
For more information about configuring application pools, see IIS Help.
Perform the following tasks to run BizTalk Server 2002 SP1 on Windows Server 2003:
To install Message Queuing
To configure Internet Explorer
This section includes information about XLANG tasks that should be performed on Windows 2003.
If you need to create additional XLANG group managers for your deployment of BizTalk Server 2002 on Windows Server 2003, note that the COM+ application settings may need to be changed. COM+ applications enforce role-based security access by default in Windows Server 2003. Therefore, any new COM+ applications need to either disable role-based security (not recommended), or roles need to be assigned to the application. To update the COM+ settings for new COM+ group manager applications, use the following procedure:
To update the XLANG group manager settings
For additional information about these role definitions, see the section titled "Security for Applications That Host XLANG Schedule Instances" in BizTalk Server 2002 Help.
The maximum number of threads that can be created by a process on Windows Server 2003 is 500. Therefore, the number of running XLANG schedule instances at any given time should be significantly less than 500 to ensure that this limit is not exceeded. If the limit is reached, then no more threads will be spawned. This condition may cause the XLANG Scheduler process to stop responding, which affects the running XLANG schedules.
To prevent this, you should associate your XLANG schedules with XLANG schedule pools to limit the number of executing schedule instances. The maximum pool size you should set for your XLANG schedules varies based on a number of factors, including the complexity and components of your XLANG schedules. XLANG schedule pool sizes should be tested on your installation of BizTalk Server 2002 to determine the proper configuration for your environment prior to deploying it into a production environment. For more information, see "Pooling XLANG Schedules" in BizTalk Server 2002 Help.
Some of the samples shipped with the BizTalk Server 2002 Software Development Kit (SDK) use the Microsoft Visual Basic® MsgBox function to display dialog boxes to the user. Under some conditions, executing this function in a multithreaded environment, such as COM+, may cause the program to stop responding. The samples in the SDK identified with this potential problem include:
|Self-Routing||\Program Files\Microsoft BizTalk Server\SDK\Messaging Samples\Self-Routing|
|While Shape||\Program Files\Microsoft BizTalk Server\SDK\XLANG Samples\Loop|
|XLANG Schedule Pooling||\Program Files\Microsoft BizTalk Server\SDK\XLANG Samples\Schedule Throttling|
To fix this problem, download the latest Visual Basic 6.0 Service Pack update from the Product Updates for Microsoft Visual Basic site.
The files for Service Pack 1 are packaged into a single executable file, BTS2002-SP1-<language>.exe, for example, BTS2002-SP1-ENU.exe. When you open this file, the Service Pack 1 setup files are extracted to a temporary folder, and the Setup.exe file is run automatically.
Note During installation, Service Pack 1 requires that you have access to the original installation source of BizTalk Server 2002 (CD or network share).
If you need to run a silent installation, you must save the executable file when downloading it, and then extract the files to a folder. The Service Pack 1 executable contains the following files:
Important All the files listed above must reside in the same directory. If they do not, Service Pack 1 will not install correctly. Do not run any of these files separately.
If your installation is canceled or stopped for any reason, you can begin the installation again by double-clicking the Setup.exe file. If you encounter a problem during installation and no error message appears, review the log file, Setup.log. A link is provided to this file on the last page of the Microsoft BizTalk Server 2002 SP1 installation wizard.
Note After the SP1 installation completes successfully, an error may be written to the Application section of the Event Viewer as follows:
Installing the performance counter strings for BTSSvc failed. The Error code is DWORD 0 of the Record Data.
No action is required for this error during installation.
Command-Line Operations Instructions
Service Pack Security Updates
Known Issues in Service Pack 1
You can also install Service Pack 1 by using command-line switches. After you have saved the Service Pack 1 executable to your hard disk and extracted the files to a folder, you can run any of the Service Pack 1 command-line switches from a command prompt. Command-line switches are provided for users who want to use scripting to install Service Pack 1 on multiple servers.
To use command-line switches to install Service Pack 1
The installation runs with no messages or confirmation screens.
The following command-line switches are available:
|/?||Shows usage information for this command.|
|/s||Runs a silent installation. No system messages or confirmation screens appear. All informational and error messages are written to the setup log.|
|/u||Uninstalls Service Pack 1. No system messages or confirmation screens appear.|
|/w||Runs an installation without displaying the wizard screens, but does display error messages.|
Installing Service Pack 1
Service Pack 1 Fixes
Service Pack Security Updates
This section contains information about the following fix issued in Service Pack 1:
The identity element generated in SP1 is declared by using the receipt namespace:
Important This change may result in compatibility issues when exchanging receipts between two BizTalk Server systems if SP1 is not present on both systems. Individual hotfixes addressing this problem are available for BizTalk Server 2000 and BizTalk Server 2002. These hotfixes can be applied to systems experiencing this problem that have not yet upgraded to Service Pack 1. For more information about this issue, see Microsoft Knowledge Base article 811092.
If necessary, you can disable this feature on your server by modifying the following registry key:
A value of 1 indicates that the new receipt format (<rcpt:identity…>) is generated, and a value of 0 indicates that the original receipt format (<prop:identity…>) is generated. If this registry key does not exist on a computer with SP1 installed, the new receipt format is generated by default.
A default installation of BizTalk Server 2002 creates several IIS virtual directories to facilitate functionality for the BizTalk Server tools used at design time. Two of the IIS virtual directories created by a complete installation of Microsoft BizTalk Server are vulnerable to attack if these virtual directories are published in a nonsecure environment, and should be secured as described below. These folders and settings are listed in the following sections.
The http://<servername>/BizTalkServerDocs/ Web site contains the BizTalk Server documentation files and is configured as follows:
The http://<servername>/BizTalkServerRepository/ Web site houses the BizTalk Server Web Distributed Authoring and Versioning (WebDAV) repository and is configured as follows:
Configure NTFS permissions for the underlying file structures for these virtual directories to permit only those accounts that need access to the BizTalk Server documentation and/or the BizTalk Server WebDAV repository.
Note BizTalk Server running in a production environment does not need write access to the BizTalkServerRepository virtual directory or any access to the BizTalkServerDocs virtual directory. Write access to the BizTalkServerRepository virtual directory and read access to the BizTalkServerDocs virtual directory is only necessary for development purposes. The SQL Server computer that contains the BizTalk Server InterchangeBTM database does need read access to the BizTalkServerRepository virtual directory for production purposes.
For information about the security updates included with Service Pack 1, see Microsoft Knowledge Base article 824862.
Use the Add or Remove Programs utility in Control Panel to uninstall BizTalk Server 2002 SP1.
Important Before you uninstall Service Pack 1, back up all BizTalk Server 2002 databases. As with any update of your system, this step is a recommended operations procedure.
After removing Service Pack 1, you need to restore the SQL Server databases to their pre-SP1 state. This will remove any SQL Server changes done by previous QFEs before installing BizTalk Server 2002 SP1. Therefore, you will need to reapply any necessary QFE SQL scripts after removing BizTalk Server 2002 SP1.
To restore the BizTalk Server databases
After uninstalling Service Pack 1, you should use the following procedure to restore btstrace.dll to its original state:
To restore btstrace.dll
This section contains information about the following known issue:
For additional information about known issues and specific fixes, see Microsoft Knowledge Base article 824863.
Important When submitting S/MIME encrypted or signed BizTalk Framework (BTF) messages to BizTalk Server 2002 SP1, data loss may occur due to an incorrectly registered Collaboration Data Objects (CDO) library file. Follow the steps outlined below to ensure that the DLL is correctly registered.
To register the CDO System Library (cdosys.dll)
For Windows 2000:
For Windows XP or Windows Server 2003:
For more information about BizTalk Server 2002, see:
If you have technical questions about Service Pack 1 that are not answered in this document or in the Microsoft Knowledge Base articles, Microsoft offers technical support and services ranging from free, to pay-per-incident, to annual support plans. Some of these plans may be available 24 hours a day, seven days a week. Microsoft offers the following support:
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.
© 1996-2003 Microsoft Corporation. All rights reserved.
Microsoft, MS-DOS, Windows, Windows NT, Windows Server, BizTalk, MSDN, Visio, and Visual Basic 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.