Checklist before performing upgrade from BizTalk Server 2004.
Thought would add a checklist that you need to run through before upgrading from BizTalk 2004. Though you can find all this in the upgrade guide, I wanted to emphasize on a few things. If you follow upgrade guide religiously, the upgrade experience should be seamless.
· The user performing the upgrade must have the following rights:
· Administrator on the local machine
· SQL Server System Administrator rights on the SQL Server
· BizTalk Server Administrator
· SSO Administrator
· The Network Service account must have write access to %windir%\temp.
· Enterprise Single Sign-On Master Secret Server must be running at the time of upgrade. The SQL Server which hosts the SSO database regardless it is running locally or at remote server at the time of upgrade.
· IIS 6.0 Common Files component must be installed if you would like to publish BizTalk Web services in BizTalk Server 2006 for the following:
· IIS Common Files are needed because of the runtime machines which providing the ASP.NET Web services require them.
· IIS Common Files are needed because of when the administration machines which used to pack BizTalk applications require them to access the IIS metabase on the remote machines if the application contains or references the remote web directories.
· If you configure all BizTalk Server 2006 databases to be BizTalkMgmtDb except BizTalkEDIDb and SSODB, you will not be able to upgrade to later version. Build to build upgrade on consolidated databases is not supported.
· SQL Server 2000 Analysis Services client tools must be installed on the computer in order to perform the upgrade on Analysis Service databases.
· In SQL Server Analysis Services 2000, dimension level can reference alias called "Error" or "Name". Yet, in SQL Server 2005 Analysis Services, these words are reserved words. The upgrade may fail if custom BAM views on OLAP cubes are deployed. To work around this, modify the Alias name in Excel or the Name attribute of that Alias element in Xml before the upgrade.
· If you have BizTalk Server 2004 version of MQSeries Adapter and MSMQ Adapter installed on the machine, export the binding and then uninstall them before the upgrade.
· If you are upgrading Business Activity Services, it is recommended that you synchronize the BAS site with the TPM database before you upgrade. For more information about running the Sync command, see "How to Synchronize BAS Data" in BizTalk Server 2004 Help.
· A BAM Data Transformation Services (DTS) package must not be running when upgrade is performed, otherwise there may be loss of data or corruption of a cube.
