Contents of Site Server 3.0 SP3 Readme

• Microsoft Site Server version 3.0
• Microsoft Site Server version 3.0, Commerce Edition

SUMMARY

The "More Information" section of this article contains a copy of the Readme file included with Site Server 3.0 Service Pack 3 (SP3). It is included here so that the topics it covers are searchable in the Microsoft Knowledge Base.

The file containing this Readme is located at \Microsoft Site Server\Sp3\Docs\Readme_sp3.htm.

Note: Knowledge Base articles can be viewed in either ASCII-text or HTML format. If you are viewing the ASCII-text version of this article, some formatting may have been lost when it was converted from the original HTML form of Readme_sp3.htm. Following are the contents of the Readme file as it shipped with the products listed above. It has not been edited by the Microsoft Developer Support Knowledge Base editing team.

MORE INFORMATION

Following are the contents of the Readme file as it shipped with the products listed above. It has not been edited by the Microsoft Developer Support Knowledge Base editing team. bgcolor=white lang=EN-US link=blue vlink=blue style="tab-interval: .5in" topmargin=0>

Site Server 3.0 Service Pack 3 Readme

IMPORTANT: Due to the integrated nature of the Site Server components, it is recommended that you print this document and read each section to ensure a successful setup.

CONTENTS

• What's in Site Server Service Pack 3?
• Installing Service Pack 3 Updates
• Installing Symbol Files
• Known Issues
• Additional Information
• Product Support

WHAT'S IN SITE SERVER SERVICE PACK 3?

SS3SP3 includes hot fixes and other information important to successful implementations of Site Server 3.0, specifically.

• SP3 updates (hot fixes) for Site Server 3.0 components
• Updates allowing Site Server 3.0 to run on Windows 2000
• Content Deployment for Unix updates
• Sample Site updates
• Updated Site Server Debug Files

Service Packs are cumulative and this Service Pack contains all changes to the Site Server 3.0 product since release.  For a list of hot fixes in this release and their related Knowledge Base articles, see Microsoft Knowledge Base article Q243533 .

When installed SS3SP3 will create the following subdirectories in the installation directory of Site Server 3.0.

INSTALLING SERVICE PACK 3 UPDATES

• General Information and Instructions
• Platform Requirements
• Command Line Operation Instructions
• Update Instructions for Personalization & Membership Databases
• Content Deployment for Unix Update Instructions
• Site Foundation Wizard Configuration Instructions

General Information and Instructions

Before you install SS3SP3, make sure you carefully review each section of this readme for order of install information.  SS3SP3 updates can only be installed on computers already running at least one Site Server 3.0 product.

SS3SP3 contains all the updates since the release of Site Server 3.0. When you install the SS3SP3 updates, only those files that are not typically modified by customers or those that do not require manual steps are applied to the existing Site Server components.  Sample Site code, SQL Scripts, Unix fixes and Commerce updates are not applied.  Instructions for applying the above files are listed in latter sections of this Readme file.

Not all install scenarios are displaying visible error messages.  If a problem occurs where no error message appeared during the installation of the Service Pack, check the ss3sp3.log setup log file in the User profiles\temp directory for additional information.

Platform Requirements

Windows 2000

To install Microsoft Site Server 3.0 on Windows 2000, follow the instructions below.  For more information see Microsoft Knowledge Base article Q241833.

To install Microsoft Site Server 3.0 Commerce Edition on Windows 2000 follow the instructions below.  For more information see Microsoft Knowledge Base article Q241833.

3.  Install Site Server 3.0 Commerce Edition.  During the Installation of Site Server 3.0 Commerce Edition, the following two errors will be displayed.  They can be safely ignored.

File(s) failed to self-register.
D:\Microsoft Site Server\Bin\xenroll.dll

Cannot set attribute description
Details:
Error:80071392

4.  Install Site Server 3.0 SP3

ADSI and MDAC

Site Server 3.0 Service Pack 3 requires the installation of ADSI 2.5 and MDAC 2.1.2.4202.3 (SP2) in the following instances:

• Using Site Server 3.0 Membership authentication to a SQL Server database (not needed for NT authentication)

           or

• Using Site Server 3.0 Commerce Edition

For additional information and instructions for ADSI 2.5 and MDAC 2.1 SP2, see Microsoft Knowledge Base article Q216709

Platform Compatibility Requirements

Site Server 3.0 has been tested on all subsequent releases of service packs and version upgrades to the SS3 Release Platform Requirements.  Below is a matrix outlining the compatible Site Server 3.0 service packs for each individual update or version upgrade to the SS3 Release Platform Requirements.

*Please see the Introduction to Site Server Service Packs article in the Microsoft Knowledge Base for additional information related to compatibility issues between these two products.

Command Line Operation Instructions

SS3SP3.exe is an executable file that decompresses the SS3SP3 files into a temporary directory, and then runs the SetupSP.exe command to install SS3SP3.  SS3SP3.exe supports the following command line switches.

Update Instructions for Personalization & Membership Databases

Updates to the P&M Databases will not be implemented until the LDAP service is stopped and restarted, post SS3SP3 install.  Since the SP installer does this task automatically, it is more expedient to do this step before installing SS3SP3 on your LDAP servers.

The following, benign event sequence in an Event Log of an LDAP Server NT Application indicates that you have not run mcis2upd.sql against one or more of your Membership Directory databases. If this event sequence appears, make sure that you have run mcis2upd.sql against all of your target databases. To verify that all supporting databases have been updated, monitor the event log for further occurrences of this sequence.

Note:  SS3SP3 contains fixes that will automatically update subsequent Membership Databases during creation.  Once SS3SP3 is installed, this step will not be required for new databases. 

Note:  If you are using a Microsoft® Access database, this step is not necessary.

Updating your existing P&M Databases:

1. 1.  Run the script mcis2upd.sql located in the <Site Server Install Dir>\SP3\Scripts directory against every SQL Server database supporting an SS3SP3 LDAP service instance that was created prior to the installation of SS3SP3.  The MCIS2UPD.SQL script can also be downloaded from the Microsoft Site Server Webpage.

·         Instructions for SQL Server 6.5:

1.      Copy mcis2upd.sql from <Site Server Install Dir>\SP3\Scripts to a location accessible from your SQL Server computer.

2.      On the Start menu of the SQL Server computer, point to Programs, point to Microsoft SQL Server 6.5, and then click SQL Enterprise Manager.

3.      Click the plus sign (+) next to the name of the SQL Server computer that is hosting the Membership directory, click the plus sign (+) next to Databases, and then click the Membership Directory database.

4.      On the Tools menu, click SQL Query Tool.

5.      In the Query window, click the Load SQL Script icon, and then in the Open File dialog box, open mcis2upd.sql from the location to which it was previously copied. The mcis2upd.sql script is loaded into the Query window.

6.      Click the Execute Query icon.

·         Instructions for SQL Server 7.0:

1.      Copy mcis2upd.sql from <Site Server Install Dir>\SP3\Scripts to a location accessible from your SQL Server computer.

2.      On the Start menu of the SQL Server computer, point to Programs, point to Microsoft SQL Server 7.0, and then click Query Analyzer.

3.      Type the name of the SQL Server containing the LDAP Membership directory to modify. Click OK.

4.      Choose File, Open from the toolbar menu. Open mcis2upd.sql from the location to which it was previously copied. The mcis2upd.sql script is loaded into the Query window.  Click Open.

5.      In the DB field in the toolbar, choose the database for the LDAP Membership directory and click the green arrow to run the script.

2.      Install Site Server 3.0 SP3 on all LDAP Servers.

Content Deployment for Unix Update Instructions

1. 1.  After installing SS3SP3, copy install.sun from the <Site Server Install Dir>\SP3\Unix directory to the Unix server.
2. 2.  From the directory where the install script is located, change the file permissions on install.sun to allow execution by the root user by typing the command chmod 744 install.sun.
3. 3.  Run the script by typing the command ./install.sun at the command line. The install script will guide you through the installation process.

Site Foundation Wizard Configuration Instructions

When creating a new site using the Site Foundation Wizard, if a Universal Naming Convention (UNC) directory location is specified rather than a local or mapped directory, the site foundation is not created correctly. A new feature added to the Site Foundation Wizard allows customers to create configurations that contain multiple web servers and a single file server. For more information on both the configuration of the hot fix and the known issues associated with it refer to the Knowledge Base article referenced by Q199099.

To install the updated files:

1. Copy account.asp, directory.asp, finish.asp and setup.vbs from the <Site Server Install Dir>\SP3\Commerce subdirectory to <Site Server Install Dir>\SiteServer\Admin\Commerce\Foundation, where <Site Server Install Dir> is the base installation directory for Site Server. This is defaulted to <SystemDrive>:\Microsoft Site Server.
2. Stop and restart the WWW Service.

Updates to Search ASP Files

ADO Version Problems

Some asp files for Site Server 3.0 Search were hardcoded to use ADO 1.5.  These files have been changed, to be ADO version independant and have been included in the <Site Server Install Dir>\SP3\samples\search\sql and <Site Server Install Dir>\SP3\samples\search\sqlmulti directories.  If the versions of these files have not been modified since being installed by Site Server Setup, you can safely copy them over the existing files.  If you have modified these files, you can manually make the changes to your existing asp files.  For additional information on the changes made to these files, see Microsoft Knowledge Base article Q243207 .

Outlook not being launched in Internet Explorer Environments

When returning Exchange results some asp files would fail to launch the Outlook client when used with Internet Explorer 5.0.  This was because it was looking for Internet Explorer version 4.x or less.  Updated versions have been included in the <Site Server Install Dir>\SP3\samples\search\exchange directory.  If the versions of these files have not been modified since being installed by Site Server Setup, you can safely copy them over the existing files.  If you have modified these files, you can manually make the changes to your existing asp files.  For additional information on the changes made to these files, see Microsoft Knowledge Base article Q243206.

AV being caused by calling util.getarrayelement

The way that the util.getarrayelement function was being called sometimes caused a AV.  Updated versions of the asp files containing this call have been included in the <Site Server Install Dir>\SP3\samples\search\language and <Site Server Install Dir>\SP3\samples\search\table directories.  If the versions of these files have not been modified since being installed by Site Server Setup, you can safely copy them over the existing files.  If you have modified these files, you can manually make the changes to your existing asp files.  For additional information on the changes made to these files, see Microsoft Knowledge Base article Q243203.

INSTALLING SYMBOL FILES

Each program file in Site Server has a corresponding symbol file that is used to find the cause of Site Server component program faults. The symbol files are available in a separate download package.  The symbol files package with installation instructions can be obtained from Microsoft’s Web Site.

KNOWN ISSUES

The following are the known issues for this release:

The Indexing Service needs to be restarted after reboot

Site Server 3.0 Content Mangement will not function correctly on Windows 2000 systems that do not have the Indexing Service running.  This service is not started by default on new installs of Windows 2000.  Set the Indexing Service to start automatically on boot, or manually start the service after each reboot.  On Windows 2000 upgrades from Windows NT 4.0, on which the Indexing Service is installed, this service will start automatically. 

SS3SP3 version of mcis2upd.sql must be re-applied on the LDAP DS after 7.0 uninstall

If you installed SQL 7.0 prior to running the SS3SP3 version of mcis2upd.sql, and you want to uninstall SQL 7.0 to return to a SQL 6.5 production environment, you must first re-run the SS3SP3 version of mcis2upd.sql on all SQL LDAP Membership databases. If you do not do this, the SS3SP3 LDAP Server will be unable to connect to the DS.

Site Server client certificate mapper may not function correctly on Windows 2000

When using Windows 2000, and enabling client certificates, the Site Server client certificate mapper may not function. This behavior may only occur with a web-site mapped to a Site Server Membership Instance and client certificates are enabled as an authentication method. Authentication between the client’s certificate and the user’s account in the membership directory could fail. See Microsoft Knowledge Base article Q244274 for more information.

Syntax error noted in Commerce Server 3.0 MS Market Starter Site

The configuration for Site Server Commerce Edition sample site, MS Market, fails with an ASP error after upgrading to IE 5.0. The ASP script engine has made changes in its handling of white space, which results in a syntax error. The workaround for this issue is to remove the space before the "value" on line 58 of the config.asp file. The revised line should read as follows:

mscsPage.URL("manager/databaseid_edit.asp")%> <% =
mscsPage.HTMLEncode(databaseid ("lastusedid").value) %> </A> </TD>

For more information, refer to the Microsoft Knowledge Base article Q214435.

Active Server Pages, ASP 0131 errors

If Site Server 3.0 is installed on a Windows 2000 installation the following error will occur on some sample and Web administration pages:

Active Server Pages, ASP 0131
Disallowed Parent Path
The Include file '../<filename.ext>' cannot contain '..' to indicate the
parent directory.
/<path>/<filename.ext>, line <number>

If this error occurs it my be because the EnableParentPaths setting is set to "off".
For production servers we recommend leaving this setting off.

Please review the following Microsoft Knowledge Base articles on this subject:

• Q226474 Err Msg: Active Server Pages, ASP 0131 Disallowed Parent Path
• Q184717 AspEnableParentPaths MetaBase Property Should Be Set To False

Also see the "Microsoft Internet Information Server 4.0 Security Checklist"

A simple change can be made to the sample and Web administration pages to resolve this issue.

1. In the pages generating the above error search for the word "#include".
2. Change the relative parent paths in the include statements from: <!--#include file="../<filename.ext>"-->
to the following: <!--#include virtual= "/<virtual path>/<filename.ext>"-->

Additional query words: README_SP3.HTM README_SP3 readme kbreadme read me release notes

Keywords :
Version : winnt:3.0
Platform : winnt
Issue type : kbhowto