How to install Site Server 3.0 and Site Server 3.0 Service Pack 4 on a computer that is running Windows 2000 (892680)

SUMMARY

Introduction

Installation requirements and recommendations

• Site Server 3.0 requires a computer that is running one of the following editions of Windows 2000:
  • Windows 2000 Server
  • Windows 2000 Advanced Server
  • Windows 2000 Datacenter Server
  We do not support the installation of Site Server 3.0 on a computer that is running Windows 2000, Professional Edition.
• Do not install Site Server 3.0 on a computer that functions as a backup domain controller (BDC). For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

  184760 Error: "CreateIISPackage or DeleteIISPackage, 0x80080005"

• Do not install Microsoft Exchange on a computer that is running Site Server 3.0. Site Server 3.0 and Exchange are resource-intensive programs. Therefore, you may experience a decrease in performance if both these programs are running on the same computer. Additionally, Site Server 3.0 and Exchange use the same Transmission Control Protocol (TCP) ports: TCP port 389, and TCP port 25.
  
  Note This recommendation does not apply to a computer that is running Microsoft BackOffice Small Business Server 4.5. For additional information, click the following article numbers to view the articles in the Microsoft Knowledge Base:

  229758 Installation steps for SBS 4.5 Part 1

  230735 Installation steps for Small Business Server version 4.5 (Part 2)

• Do not install Site Server 3.0 on a computer that is a member of a server cluster. However, you can install Site Server 3.0 on a computer that is a running Windows Load Balancing Server. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

  228999 Site Server 3.0 services cannot be configured to work with Microsoft Cluster Server (MSCS)

• Do not install SQL Server 2000 on a computer that is running Windows Load Balancing Server. However, you can install SQL Server on a computer that is a member of a server cluster.
• Do not modify the default settings in Microsoft Internet Information Services (IIS) before you install Site Server 3.0. In particular, make sure of the following:
  • Do not disable Windows authentication (NTLM).
  • Do not change the IP binding option from the default value. The default value is all unassigned.
  • Do not change the default port assignment of the default Web site. The default port assignment of the default Web site is port 80.
  For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

  234519 Site Server 3.0 Setup fails when installed on an existing Internet Information Server 4.0 computer

• Make sure that the root of the drive where you want to install Site Server 3.0 has NTFS file system permissions of at least Read permissions for the Everyone group. If you must modify these security permissions, modify them after you install Site Server 3.0.
  
  Note If you later modify the permissions on the root of the drive where you install Site Server 3.0, do not replace the permissions on the subfolders of this drive.
• Do not use Microsoft Commercial Internet System with Windows 2000. They are not currently compatible.
• Do not use a hard-disk cloning program to configure a computer that is running Site Server 3.0. Some of the Site Server 3.0 components install computer-specific information. This information cannot be cloned successfully.
• You can install Site Server 3.0 on a computer that is running Microsoft Terminal Services.
• If you determine that you must run the Mcis2upd.sql script, use the copy of this script that is located in the Site Server installation folder\SP4\Scripts folder. Do not download this script from the Microsoft FTP site.

Installation instructions

Installation instructions before you install Site Server 3.0

1. Install Windows 2000.
   
   Note We recommend that you install Site Server 3.0 on a stand-alone server or on a member server. We recommend that you do not install Site Server 3.0 on a domain controller.
   
   When you install Windows 2000, make sure that you install all the following components:
   • Indexing Service
   • Internet Information Services (IIS)
   • FrontPage 2000 Server Extensions
   • SMTP Service
2. Install SQL Server 2000.
3. Install SQL Server 2000 Service Pack 3a (SP3a). To obtain this service pack, visit the following Microsoft Web site:

   http://www.microsoft.com/sql/downloads/2000/sp3.asp

4. Configure the SQL Server client default network library to use named pipes. This configuration is required when SQL Server is installed on the same computer as Site Server 3.0.
   
   To configure the default network library to use named pipes, follow these steps:
   1. Click Start, point to Programs, point to Microsoft SQL Server, and then click Client Network Utility.
   2. Click the General tab.
   3. Click Named Pipes in the Enabled protocols by order list, and then click the up arrow button to move this protocol to the top of the list.
5. Verify that the Distributed Transaction Coordinator (MSDTC) service is started and that this service is configured to automatically start. To do this, follow these steps:
   1. Click Start, click Run, type services.msc, and then click OK.
   2. In the Services dialog box, double-click Distributed Transaction Coordinator.
   3. Under Service status, click Start if the service status is reported as stopped.
   4. In the Startup type list, click Automatic.
   For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

   222000 Microsoft Site Server Commerce 3.0: Error '8004e00f'

6. Configure database connectivity.
   
   You do not have to create a database or a Data Source Name (DSN) for the Site Server 3.0 Personalization and Membership feature. If you decide to create a SQL Server-based membership instance after you install Site Server 3.0, create your database before you configure the membership instance.
   
   Additionally, you do not have to create a database or a DSN for the Site Server 3.0 Usage Analysis feature. After you install Site Server 3.0, the Usage Analysis database is created when you run the Database Setup Wizard.
7. Run the Ss3w2k.exe program. To obtain this program, visit the following Microsoft Web site:

   http://www.microsoft.com/downloads/details.aspx?FamilyID=3F12D3AB-263A-4C98-BB80-FDD5038A5CB1&displaylang=en

   Important You must run this program before you install Site Server 3.0. This program enables Site Server 3.0 to work with Microsoft FrontPage 2000 Server Extensions. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

   243564 Error message: Setup is not complete. If you quit the setup program now, the Microsoft Site Server 3.0, Commerce Edition will not be installed.

   Note This program runs quickly and does not display results to indicate that Windows was updated successfully. If you cannot determine whether this program was run successfully, you can run the program again. You can run this program as many times as you want to.
8. Optionally, install Microsoft Office XP.
   
   Note If you decide to install Office XP, you must install it before you install Site Server 3.0. The installation of Office XP removes the Microsoft FrontPage registry entry that Site Server 3.0 Commerce Edition requires to successfully run the Site Foundation Wizard.

Installation instructions for Site Server 3.0

• If you are prompted to overwrite existing files during this installation of Site Server 3.0, click No to All. Windows 2000 contains newer versions of some DLL files. The Site Server 3.0 Setup program may try to overwrite some of these newer files.
• If you install the Site Server 3.0 Analysis component, do not run the Analysis SQL Server Database Setup Wizard until after you install Site Server 3.0 Service Pack 4 (SP4). Only run this wizard if the computer that is running SQL Server is dedicated for the Site Server 3.0 Analysis component. The Analysis SQL Server Database Wizard makes changes to the global SQL Server configuration.

• Do not create new membership instances before you install Site Server 3.0 Commerce Edition. The Trey Research Web site is not installed correctly or is not configured correctly if you create new membership instances before you install Site Server 3.0 Commerce Edition.
• Create individual databases for Ad Server or for Commerce Server. You can store these databases on different database servers or on the same database server.
• Create a System DSN for the Ad Server database or for the Commerce Server database. When you create each DSN for Ad Server or for Commerce Server, configure all the following:
  • Use SQL Server standard authentication instead of Windows authentication.
  • Specify a SQL Server account with at least database ownership (DBO) rights.
  • Do not use the default master database. Instead, specify the corresponding database for each DSN.
• Ignore the following error messages that you receive when you install Site Server 3.0 Commerce Edition:
  
  Error message 1
  File(s) failed to self register.
  drive:\Microsoft Site Server\Bin\Xenroll.dll
  Error message 2
  Cannot set attribute description
  Details:
  Error: 80071392
  Site Server 3.0 Commerce Edition is installed correctly even if you receive these error messages. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

  241833 Instructions for installing Site Server 3.0 on Windows 2000

Installation instructions after you install Site Server 3.0

1. Optionally, install Microsoft Visual Studio 6.0.
   
   By default, Visual Studio 6.0 installs the Visual Studio Analyzer component. However, we strongly recommend that you do not install the Visual Studio Analyzer component on a production computer because this component severely impacts the scalability and the performance of that computer.
   
   Important Do not install Microsoft Visual Studio 97 on a computer that is running Windows 2000.
2. If you installed Visual Studio 6.0, install Visual Studio 6.0 Service Pack 5. To obtain this service pack, visit the following Microsoft Web site:

   http://msdn.microsoft.com/vstudio/downloads/updates/sp/vs6/sp5/default.aspx

3. Install Site Server 3.0 Service Pack 4 (SP4).
4. Configure the Personalization and Membership database on the computer that is running SQL Server for single-user mode. To configure a database to run in single-user mode, follow these steps:
   1. Start the SQL Server Enterprise Manager Microsoft Management Console (MMC) snap-in.
   2. Expand the following nodes:
      • Microsoft SQL Servers
      • SQL Server Group
      • Your_SQL_Server_computer_name
      • Databases
   3. Right-click the database that you want to configure, and then click Properties.
   4. Click the Options tab.
   5. Click to select the Restrict access check box, and then click Single user.
5. Run the Mcis2upd.sql script against all the existing SQL Server databases that support a Site Server 3.0 LDAP service instance. This script is located in the following folder of the Site Server 3.0 installation folder:

   SP4\Scripts

   For additional information about how to run this script, see the "Update Instructions for Personalization & Membership Databases" section of the Readme_sp4.htm file. The Readme_sp4.htm file is included with Site Server 3.0 SP4.
   
   Note You do not have to run this script against SQL Server databases that are created after you install Site Server 3.0 SP4.
6. Return the Personalization and Membership database to multi-user mode.
7. Install the latest Windows 2000 service pack. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

   260910 How to obtain the latest Windows 2000 service pack

8. Optionally, install Commerce Interchange Pipeline Manager (CIPM) for Site Server 3.0 Commerce Edition.
   
   Note If you decide to install Commerce Interchange Pipeline Manager, you must reinstall Site Server 3.0 SP4.
9. Enable the Parent Paths option in Internet Information Services 5.0. For additional information about how to enable this option, click the following article number to view the article in the Microsoft Knowledge Base:

   226474 Err Msg: Active Server Pages, ASP 0131 Disallowed Parent Path

   If you do not enable parent paths in IIS 5.0, you must modify the Site Server Web Administration pages. For information about how to modify these Web pages, see the Readme_sp4.htm file. The Readme_sp4.htm file is included with Site Server 3.0 SP4.

Post-installation recommendations

• If you installed Site Server 3.0 Commerce Edition, replace the following files as specified in the Readme_sp4.htm file:
  • Account.asp
  • Directory.asp
  • Finish.asp
  • Setup.vbs
• If you have not customized the CmSample .prf rule set files and the FpSample .prf rule set files, update these files. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

  188289 Err Msg: Server object error ASP 0177 : 800401f3

  To update these files, follow these steps:
  1. Copy all the files and folders from the Microsoft Site Server\SP4\Samples\CmSample folder to the Microsoft Site Server\Data\Publishing\CmSample folder. If you are prompted to overwrite existing files, click Yes to All.
  2. Copy all the files and folders from the Microsoft Site Server\SP4\Samples\FpSample folder to the Microsoft Site Server\Data\Publishing\FpSample folder. If you are prompted to overwrite existing files, click Yes to All.
• If you have not customized one or more of the Active Server Pages (ASP) search pages, copy all the files and folders from the Microsoft Site Server\SP4\Samples\Search folder to the Microsoft Site Server\Sites\Samples\Knowledge\Search folder. If you are prompted to overwrite existing files, click Yes to All.
• If you installed Site Server 3.0 Commerce Server, use the Site Server MMC snap-in to access the Commerce Host Administration component, and then do the following:
  • Remove ":80" from the non-secure host name field for every one of the sample stores.
  • Remove ":443" from the secure host name field for every one of the sample stores.
• Remove the SQL Server TCP/IP sockets network library file, Dbmssocn.dll, from the %WINDIR%\System32\Inetsrv folder.
  
  Note The latest version of the Dbmssocn.dll file is located in the %WINDIR%\System32 folder. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

  253272 Error message: 80004005 old net lib "dbmssocn" detected please delete it and restart the application

• Review all the following Microsoft security-related documents:
  • Microsoft Knowledge Base article 231368

    231368 Solution available for file viewers vulnerability

  • Microsoft Security Bulletin (MS99-025)

    http://www.microsoft.com/technet/security/bulletin/ms99-025.mspx

  • Microsoft Security Bulletin (MS99-058)

    http://www.microsoft.com/technet/security/bulletin/MS99-058.mspx