Installing Microsoft SharePoint Portal Server 2001
| Archived content. No warranty is made as to technical accuracy. Content may contain URLs that were valid when originally published, but now link to sites or pages that no longer exist. |
Published: January 1, 2002
On This Page
Introduction
Hardware and Software Requirements
Server Setup
Client Setup
Troubleshooting Installation
Conclusion
Appendix A – Operating System and Browser Support
Appendix B – IFS Drive and the Microsoft Web Storage System
Appendix C – Proxy Server Settings in SharePoint Portal Server
Introduction
This white paper provides information about the hardware and software required to install Microsoft® SharePoint™ Portal Server 2001 and how to install the server and client components on one or more computers in an organization.
When you insert the SharePoint Portal Server compact disc (CD) into your compact disc read-only memory (CD-ROM) drive, the Start page appears automatically. The page includes:
A shortcut to Server Installation, which starts the SharePoint Portal Server Setup Wizard.
A shortcut to Client Installation, which starts the Client Components for SharePoint Portal Server Setup Wizard.
A shortcut to the SharePoint Portal Server Tours, which are interactive introductions to SharePoint Portal Server.
A shortcut to Help, which links to the SharePoint Portal Server online Help, including the Planning and Installation and the Managing Content guides.
A shortcut to the SharePoint Portal Server Readme file.
This paper includes procedures for installing SharePoint Portal Server and the Client Components for SharePoint Portal Server. Major sections are devoted to hardware and software requirements, server setup, and client setup. In addition, the following sections are provided:
Troubleshooting Installation.?Includes information to assist you in diagnosing installation problems.
Appendix A. Includes a table showing the operating system and browser support for SharePoint Portal Server.
Appendix B. Includes information about the installable file system (IFS) and the Microsoft Web Storage System.
Appendix C. Includes instructions for changing the proxy settings for the SharePoint Portal Server computer at some time after installation.
To install the server and client components of SharePoint Portal Server, perform the following basic steps:
Review the hardware and software requirements. This section also includes information about coexistence issues, including coexistence with Microsoft SQL Server™.
Install SharePoint Portal Server on the server by running the SharePoint Portal Server Setup Wizard.
Create a workspace on the server.
Install the client components of SharePoint Portal Server on user computers. Do this by running the Client Components for SharePoint Portal Server Setup Wizard.
On client computers, add a Web folder that points to the workspace. The address of the workspace is https://server_name/workspace_name.
Hardware and Software Requirements
Before you install SharePoint Portal Server, make sure that your computer meets the following recommended hardware and software requirements.
Server Requirements
The following are the requirements for each server running SharePoint Portal Server:
Intel Pentium III–compatible processor minimum recommended.
256 megabytes (MB) of RAM minimum recommended.
550 MB minimum of available disk space. The drive must be formatted as NTFS file system.
Microsoft Windows® 2000 Server or Windows 2000 Advanced Server operating system, and Windows 2000 Service Pack 1 (SP1) or later.
Installing SharePoint Portal Server on a system that has been upgraded from Microsoft Windows NT® version 4.0 can cause install failures. It is recommended that you install SharePoint Portal Server on a clean Windows 2000 Server. If you are installing on a Windows 2000 system that was upgraded from Windows NT 4.0, manually register the oledb32.dll file before installation to avoid installation failure. To register the file, go to the Program Files\Common Files\System\Ole DB folder and type regsvr32 oledb32.dll.
Internet Information Services (IIS) 5.0.
Simple Mail Transfer Protocol (SMTP) Service. This is a Windows 2000 Server component.
In addition to the requirements listed previously, install the following Windows 2000 updates before installing SharePoint Portal Server. These updates are available on https://support.microsoft.com/. These issues will be addressed in subsequent Windows 2000 service packs.
If you are installing on Windows 2000 Server with Service Pack 1, install the following updates:
Windows 2000 Patch: Token Handle Leak in LSASS. Note that this new version of the hot fix replaces the previous hot fix (288861) release.
See 291340: Token Handle Leak in LSASS Using Basic Authentication.
Windows 2000 Patch: GetEffectiveRightsFromAcl Causes ERROR_NO_SUCH_DOMAIN - Addresses a problem that can cause subscription notifications to fail when the ACL on a document contains a Domain global group.
See 286360: GetEffectiveRightsFromAcl() Function Causes "ERROR_NO_SUCH_DOMAIN" Error Message.
If you are installing on Windows 2000 Server with Service Pack 2, install the following update:
The following prerequisites must be met before installing SharePoint Portal Server:
Windows 2000 Hot fix (Pre-SP2) 269862 cannot be installed on the computer. If it is installed, remove it before installing SharePoint Portal Server.
The Windows Remote Registry service must be running. This service is started by default. To start the service manually:
On the taskbar, click Start, point to Programs, point to Administrative Tools, and then click Services.
Right-click Remote Registry Service, and then click Start.
IIS configuration: Ensure that W3SVC/1 (Default Web Site in IIS) is started. SharePoint Portal Server setup performs a simple test to warn of potentially invalid IIS settings. This test checks the configuration of W3SVC/1 (the Default Web Site) to ensure that the Web Site Identification TCP Port is "80" with IP Address "(All unassigned)". If multiple entries were configured in Advanced Settings, setup checks only the first entry. Other configurations may be acceptable, as long as "localhost" on port "80" is a valid way to connect to W3SVC/1 (the Default Web Site) on the computer. If necessary, you can alter the configuration by opening Internet Services Manager under Administrative Tools and selecting Properties on the Default Web Site.
SharePoint Portal Server requires the Default Web Site in IIS to use port 80 as the TCP port for localhost. Before installing SharePoint Portal Server, ensure that 80 is specified as the TCP port. In addition, do not change the port to an alternative HTTP port (such as 8000 or 8080) after installation. Ensure that port 80 is specified and remains as the primary port for the server.
Coexistence Issues
The following software does not coexist with SharePoint Portal Server:
Microsoft Exchange 2000 Server
Exchange 2000 Enterprise Server
Exchange Server version 5.5 and earlier
Microsoft Site Server (any version)
Microsoft Office Server Extensions
SharePoint Portal Server setup checks for the existence of this software and fails if this software is already installed. If you install this software after installing SharePoint Portal Server, SharePoint Portal Server will stop functioning properly.
SharePoint Portal Server and Exchange 2000 Server
Based on interviews with customers, Microsoft has learned that customers plan to install Exchange 2000 Server and SharePoint Portal Server on separate computers. Typically, customers do not run other server applications on their mailbox servers because of the mission-critical nature of corporate messaging systems.
As a result, Microsoft does not recommend or support using both Exchange 2000 Server and SharePoint Portal Server on a single computer. The coexistence of Exchange 2000 Server and SharePoint Portal Server on a single computer can have a negative effect on your mission-critical messaging infrastructure. However, Microsoft does encourage customers to use the services and data from Exchange 2000 Server and SharePoint Portal Server together in their collaborative solutions and to run the server applications on separate computers.
Some of the potential issues with running Exchange 2000 Server and SharePoint Portal Server on the same computer include the following:
During installation, SharePoint Portal Server stops the Microsoft Exchange Information Store (MSExchangeIS) service for a short time period. This results in a disruption of mail services.
Exchange 2000 Server and SharePoint Portal Server share several services. If you install Exchange 2000 Server followed by SharePoint Portal Server, and then try to remove Exchange 2000 Server, SharePoint Portal Server no longer works because services formerly shared with Exchange 2000 Server are modified. Even if you attempt to uninstall Exchange 2000 Server and then cancel the removal, SharePoint Portal Server may no longer work.
During installation, SharePoint Portal Server creates its own instance of the Web Storage System (a database technology shared with Exchange 2000 Server). If you then install Exchange 2000 Server on the same computer, the Exchange 2000 Server installation stops when it detects that SharePoint Portal Server is already on the computer.
Because SharePoint Portal Server upgrades the Microsoft Search (MSSearch) service and full-text indexes, do not install SharePoint Portal Server on a server that participates in an Exchange 2000 Server clustering environment or add a computer running SharePoint Portal Server to a clustered environment.
SharePoint Portal Server and SharePoint Team Services from Microsoft
Microsoft does not support using SharePoint Portal Server and SharePoint Team Services on the same computer. If you want to use both SharePoint Portal Server and SharePoint Team Services, install each on a separate computer.
SharePoint Portal Server and Microsoft SQL Server
If you install SharePoint Portal Server on a computer running Microsoft SQL Server 7.0 or Microsoft SQL Server 2000, SharePoint Portal Server will upgrade the existing MSSearch. In addition, SharePoint Portal Server upgrades the full-text index format of all the existing indexes on that computer the next time that MSSearch starts. For the upgrade to succeed, there must be enough disk space on the computer to accommodate 120 percent of the size of the largest full-text index on the drive. Upgrading the full-text index format can take several hours, depending on the number and size of the existing indexes. During the SharePoint Portal Server setup, a message informs you that the service will be upgraded.
Because SharePoint Portal Server upgrades MSSearch and full-text indexes, do not install SharePoint Portal Server on a server that participates in a SQL Server clustering environment or add a computer running SharePoint Portal Server to a clustered environment.
You can install SQL Server on a computer already running SharePoint Portal Server. In this instance, SQL Server uses MSSearch installed by SharePoint Portal Server. If you remove SharePoint Portal Server from a computer that has SQL Server installed, SharePoint Portal Server will not remove the upgraded MSSearch because it is a shared service with SQL Server.
Installing SharePoint Portal Server in a Clustered Environment
SharePoint Portal Server is not supported in a clustered environment. You cannot install SharePoint Portal Server in a clustered environment, and you must not add the server to a clustered environment.
Installing SharePoint Portal Server on a Domain Controller
If you install SharePoint Portal Server on a domain controller:
There is no local Administrators group. Consequently, only users assigned to the coordinator role can specify security on folders. If a coordinator makes an error, there is no possibility for a local administrator to resolve security issues.
You may need to restart the domain controller after installing SharePoint Portal Server.
Renaming a SharePoint Portal Server Computer
You can rename a SharePoint Portal Server computer at any time. After renaming the server, you must restart it. In addition, SharePoint Portal Server Administration installed by setup prompts for authentication and displays an error before opening after you rename the server. To remedy this situation, manually add the SharePoint Portal Server snap-in to Microsoft Management Console (MMC).
Client Requirements
The following are the requirements for each computer running the client components of SharePoint Portal Server:
Intel Pentium-compatible 200 megahertz (MHz) or higher processor recommended.
64 MB of RAM minimum recommended.
30 MB of available disk space on Windows 2000 systems; 50 MB of available disk space on all other systems.
Windows 98, Windows Millennium Edition, Windows NT 4.0 with SP6A, or Windows 2000 Professional, Server, or Advanced Server. Coordinator functions require Windows 2000 Professional, Server, or Advanced Server.
Internet Explorer 5 or later. Microsoft Visual Basic® Scripting support is required. This is included in the default installation of Internet Explorer 5.
Microsoft Outlook® Express 5.01 or later.
SharePoint Portal Server Office extensions require Office 2000 or later.
Dashboard Site Requirements
Accessing SharePoint Portal Server through the dashboard site does not require the user to install the client components. For the Windows operating system, you can use the following browsers:
Internet Explorer 4.01 or later
Netscape Navigator 4.51 or later (for Italian and Spanish versions of SharePoint Portal Server)
Netscape Navigator 4.75 or later (for English, French, German, and Japanese versions of SharePoint Portal Server)
Macintosh and Solaris operating systems are not supported.
In addition, you must enable Microsoft JScript® or Netscape JavaScript support in your browser for the dashboard site to function.
To use the dashboard site with Netscape Navigator, you must use Internet Services Manager to enable Basic authentication for the workspace node on the Default Web Site. To enable discussions to work when the browser is Netscape Navigator, you must also enable Basic authentication for the MSOffice node on the Default Web Site.
Server Setup
You can install SharePoint Portal Server by running the SharePoint Portal Server Setup Wizard. The wizard guides you through the installation process. Before running the setup wizard on your server, plan how you will use SharePoint Portal Server in your organization. For more information, see Planning and Installation and Managing Content.
Install SharePoint Portal Server on the server by completing the following steps:
Review the server hardware and software requirements, including coexistence issues, outlined earlier in this paper.
Install SharePoint Portal Server on the server by running the SharePoint Portal Server Setup Wizard.
Create a workspace on the server.
If you have Terminal Services, you can use it in remote administration mode to install SharePoint Portal Server. If you are running in Terminal Services in application mode, run chgusr /install in Command Prompt before attempting to install SharePoint Portal Server.
You can also use group policy to install the server in attended or unattended mode by using ZAP files. For more information about using ZAP files, see the following resources:
Knowledge Base Article 231747: How to Publish non-MSI Programs with .zap Files (https://support.microsoft.com/default.aspx?scid=kb;en-us;231747&sd=tech)
Microsoft Windows 2000 Server Resource Kit (https://www.microsoft.com/mspress/books/1394.asp)
"Step-by-Step Guide to Software Installation and Maintenance" on Microsoft TechNet (https://www.microsoft.com/technet/prodtechnol/windows2000serv/howto/instmain.mspx)
For more information about installing the server in unattended mode, see "Using Unattended Server Installation."
If you want to install SharePoint Portal Server on the server in unattended mode, see "Using Unattended Server Installation" later in this section. If you want to uninstall or repair a SharePoint Portal Server computer, see "Uninstalling or Repairing SharePoint Portal Server" later in this section.
Installing SharePoint Portal Server
To install SharePoint Portal Server
Log on to the computer running Windows 2000 Server or Advanced Server as a local or domain administrator.
Stop all anti-virus software. If anti-virus software is running during SharePoint Portal Server installation, the workspace creation step at the end of the setup process fails.
Ensure that there is at least one free network drive letter on the computer. The setup process requires at least one free network drive letter on the computer.
Configure the proxy server settings for Internet access:
On the taskbar, click Start, point to Settings, and then click Control Panel.
Double-click Internet Options. The Internet Properties dialog box appears.
Click the Connections tab, and then click LAN Settings.
Clear both check boxes under Automatic configuration.
If you use a proxy server, select the Use a proxy server check box, type a valid proxy server address and port number, and then select the Bypass proxy server for local addresses check box. If you do not use a proxy server, clear all check boxes.
Click OK to apply the changes, and then click OK to close Internet Properties.
Insert the SharePoint Portal Server CD into your CD-ROM drive.
Click Server Installation. The SharePoint Portal Server Setup Wizard appears. You can also go to the Server folder on the CD, and then double-click Setup.exe.
Follow the instructions that appear in the setup wizard.
On the Product Identification page, type the CD Key in the spaces provided. The CD Key uniquely identifies your copy of SharePoint Portal Server and enables you to receive technical support. The CD Key is located on the back of your SharePoint Portal Server CD case. If the number that you type is not accepted, check the following:
If you are using the keypad to the right of your keyboard, ensure that NUM LOCK is on.
Ensure that you are not using the letter I for the number one.
Ensure that you are not using the letter O for the number zero.
On the SharePoint Portal Server Installation Folders page, specify the location on the server's disk where you want to install the SharePoint Portal Server program files and data files. You can change the installation location for these files by clicking Change Folder. SharePoint Portal Server also installs additional required files on the operating system drive. Click Disk Information for information about the amount of disk space required and the amount remaining. If there are existing files in the installation paths, setup removes these files. Note the following restrictions for the path:
The path name can have a maximum length of 100 characters.
The path name can contain only characters in the lower ASCII range.
The path cannot point to a root directory. For example, E:\ is not allowed, but E:\Installation is allowed.
On the SharePoint Portal Server Indexing Settings page, specify the default content access account and the gatherer e-mail address. The default content access account is used to crawl content sources. The gatherer e-mail address is an e-mail address that an external site administrator can contact if problems occur when SharePoint Portal Server crawls the external site. These settings are necessary for SharePoint Portal Server to crawl content stored outside the workspace and include it in an index. If you choose not to specify these settings during installation, you can specify them later by using the Properties page of the server in SharePoint Portal Server Administration.
Administrators can manage servers and workspaces from SharePoint Portal Server Administration. To open SharePoint Portal Server Administration, click Start, point to Programs, point to Administrative Tools, and then click SharePoint Portal Server Administration.
Creating a Workspace on the Server
After you run SharePoint Portal Server setup, the New Workspace Wizard appears. This wizard helps you create a workspace. If you click Cancel to close the New Workspace Wizard, you can create a workspace later by using SharePoint Portal Server Administration.
To create a workspace by using the New Workspace Wizard
Stop all anti-virus software. If anti-virus software is running during workspace creation, the process may fail.
On the first page of the wizard, click Next.
On the Workspace Definition page:
In Workspace name, type the name of the workspace that you are creating. Workspace names can consist of characters from lower ASCII except for the following:
# : \ ? * < > % / | " { } ~ [ ] Space ! ( ) = ; . , @ & +
The lower ASCII code set includes the characters with codes 32–127. The workspace name cannot exceed 25 characters in length.
The wizard verifies that the workspace name is unique and does not conflict with any other workspace names or propagated index names on the server. If the name is already in use, the wizard prompts you to enter a unique name. You cannot edit a workspace name after you create the workspace. If you are creating an index workspace, the name of the workspace that you are creating must be different from that of the destination workspace.
In Description, type an optional description of the workspace.
If you are not creating an index workspace, omit this step. If you are creating an index workspace, click Advanced. Select the Configure as an index workspace check box. In Specify the destination workspace address, type the destination workspace for the propagated index. The name of the destination workspace is https://server_name/workspace_name. Click OK. The wizard prompts you to provide the name of a propagation access account, which is required before you can propagate an index. This account must have local administrator permissions on the destination server.
The destination workspace must exist before you create the index workspace. The wizard ensures that a workspace with the same name as the index workspace does not already exist on the destination. You cannot change the destination workspace after you have created the index workspace. If the destination server is not a SharePoint Portal Server computer, the wizard logs an error in the Application Log in Windows 2000 Event Viewer (commonly referred to as the Windows 2000 event log).
You can create index workspaces with the same name (and propagating to the same destination) on multiple servers dedicated to creating and updating indexes. The last index to propagate has its index active on the destination. You can use this setup to continually update the destination by appropriately scheduling the crawls for each index workspace.
It is recommended that you maintain a list of index workspace names, the servers on which they are stored, and the servers and workspaces to which they are propagated.
Note that to use fully qualified domain names and index workspace propagation together, both the server dedicated to indexing and the destination server must be in Windows 2000 domains.
Click Next.
On the Workspace Contact page:
In Workspace contact name, type the name of the user or group that you are assigning as the workspace contact. The workspace contact is the individual user or group with overall responsibility for the workspace.
In Workspace contact e-mail address, type the e-mail address for the workspace contact. The contact e-mail address can be that of an individual user or a group.
Click Next.
Click Finish to complete the wizard and create the new workspace. After SharePoint Portal Server creates the workspace, it displays a message stating that the wizard will open the workspace and create a link to it in My Network Places.
Click OK. The link is created, the Configure Your Workspace page opens, and the dashboard site opens. For index workspaces, an introduction page opens and the link points to the Content Sources folder within the workspace.
After you create the workspace, you must configure security on the workspace node by using SharePoint Portal Server Administration or Web folders. The Windows 2000 local Administrators group has permission to read documents and configure security on any folder or document in a workspace.
The SharePoint Portal Server Setup Wizard automatically installs the client components. After installing the client, you must add a Web folder that points to the workspace. The address of the workspace is https://server_name/workspace_name.
Using Unattended Server Installation
If you are installing a large number of servers or want to customize your installation, you can run SharePoint Portal Server setup in unattended mode by using an .ini file. When you install SharePoint Portal Server by using an .ini file (also called silent install), no dialog boxes or error messages that require user intervention are displayed unless prerequisites are missing. This setup lets you install identical configurations of SharePoint Portal Server on multiple computers.
Before running this unattended setup, you must create an .ini file that contains the default installation settings that you want to use, such as the installation directory. After you create the .ini file, you can edit it by using a text editor. By editing the .ini file, you specify additional options and gain more control over your installation.
To create the .ini file used for unattended setup, you must run the SharePoint Portal Server Setup Wizard. However, instead of installing SharePoint Portal Server, the wizard stores the settings that you specify in the .ini file.
Double-byte character set (DBCS) or high-ASCII characters cannot be used in installation paths when performing an unattended installation. Using these characters results in a failed installation. In addition, no path in the .ini file should be longer than 140 characters.
To install SharePoint Portal Server by using an .ini file
Create an .ini file:
On the taskbar, click Start, and then click Run.
In Open, type path_to_server_setup_file setup /CreateUnattend path filename .ini where filename is the name of the .ini file that you want to create. For example, if the setup file is in the Setup directory on drive D and you want to create sample.ini on the E drive, type D:\Setup\setup /CreateUnattend E:\sample.ini
Click OK.
Follow the instructions that appear in the SharePoint Portal Server Setup Wizard. All settings that you choose are included in the .ini file that you create.
One additional parameter is available for use with /CreateUnattend: /EncryptedMode. This parameter enables you to create an .ini file with the password for the default content access account hidden. To do this, type path_to_server_setup_file setup /CreateUnattend path file_name .ini /EncryptedMode
Edit the .ini file:
In a text editor, such as Microsoft WordPad, open filename .ini where filename is the name of the .ini file that you created.
Modify parameters in the file for the settings that you want SharePoint Portal Server setup to use.
If you plan to use an unattended installation file on servers with varying storage configurations, ensure that hard-coded paths are valid for each server configuration before starting the installation. An example of a hard-coded path reference is "C:\." You can force the installer to automatically choose the correct default path by removing an entry line completely.
You can modify only the following paths:
InstallDirectory. You can specify the installation location for SharePoint Portal Server program files. By default, the program files are stored on the operating system drive in Program Files\SharePoint Portal Server.
There are two other InstallDirectory paths. One path is for the Web Storage System and the other is for MSSearch. Altering these paths is not recommended. This is the recommended option for the MSSearch and Web Storage System installation directories:
InstallDirectory=operating_system_drive\Program Files\Common Files\Microsoft Shared\Web Storage System
InstallDirectory=operating_system_drive\Program Files\Common Files\Microsoft Shared\MSSearch
By default, the Web Storage System files are stored on the operating system drive in Program Files\Common Files\Microsoft Shared\Web Storage System. However, if you are running unattended server installation and you delete all lines containing a hard-coded path reference, the location defaults to Program Files\Exchsrvr on the operating system drive.
Search Gatherer Log Directory. Each time that SharePoint Portal Server creates an index, it creates a log file for that workspace. This log file contains data about crawling content sources and records access errors. After installation, you can use SharePoint Portal Server Administration to change this path. By default, the log is stored on the operating system drive in Program Files\SharePoint Portal Server\Data\FTData\SharePointPortalServer\GatherLogs.
The gatherer log contains data about URLs that SharePoint Portal Server accesses while it creates an index. The file records successful accesses, access errors, and accesses disallowed by rules (in case the user needs to debug the index restrictions). Coordinators can view this log from a user-friendly Active Server Pages (ASP) page in the workspace.
Search Index Directory. When creating a workspace, SharePoint Portal Server creates an index under this root node. SharePoint Portal Server also creates all indexes propagated to the server under this root node. After installation, you can use SharePoint Portal Server Administration to change this path. By default, the indexes are stored on the operating system drive in Program Files\SharePoint Portal Server\Data\FTData\SharePointPortalServer\Projects. If you want to move existing indexes to a new location, see ToolsHowTo.txt in the Support\Tools directory on the SharePoint Portal Server CD.
Search Property Store Database Directory. You can specify the location of the property store file. The property store file contains the metadata from documents. After installation, you cannot modify the file location by using SharePoint Portal Server Administration. By default, the property store file is stored on the operating system drive in Program Files\SharePoint Portal Server\Data\FTData\SharePointPortalServer. To modify the file location, see ToolsHowTo.txt in the Support\Tools directory on the SharePoint Portal Server CD. For optimal performance, the property store and property store log files should be on dedicated physical volumes. SharePoint Portal Server shares this file across all workspaces.
Search Property Store Log Directory. You can specify the location of the property store log files. The property store log files are the log files for the property store. After installation, you cannot modify the location of these files by using SharePoint Portal Server Administration. By default, the property store log files are stored on the operating system drive in Program Files\SharePoint Portal Server\Data\FTData\SharePointPortalServer. To modify the file location, see ToolsHowTo.txt in the Support\Tools directory on the SharePoint Portal Server CD. For optimal performance, the property store and property store log files should be on separate dedicated physical volumes. SharePoint Portal Server shares these files across all workspaces.
Web Storage System Database Directory. You can specify the location of the Web Storage System Database file. Every SharePoint Portal Server computer contains one public store (wss.mdb). All workspaces hosted on the server reside on the Web Storage System. After installation, you can use SharePoint Portal Server Administration to change this path. If this location changes, the existing file moves to the new location. By default, the database file is stored on the operating system drive in Program Files\SharePoint Portal Server\Data\Web Storage System.
Web Storage System Streaming Database Directory. You can specify the location of the WSS-Streaming Database file. Used for streaming files, the WSS-Streaming Database file (wss.stm) contains data and is a companion to the WSS-Database file (wss.mdb). Together, these two files form the database. SharePoint Portal Server document streams make up a sizable part of the total amount of data. You might want to move this file to a larger drive (ideally a dynamic disk that you can easily resize) because it can increase substantially over time. After installation, you can use SharePoint Portal Server Administration to change this path. If this location changes, the existing file moves to the new location. By default, the streaming database file is stored on the operating system drive in Program Files\SharePoint Portal Server\Data\Web Storage System.
Web Storage System Database Log Directory. You can specify the location of the WSS-Database Log files. These are the log files for the Web Storage System. For optimal performance, place the log files on a dedicated physical volume. After installation, you can use SharePoint Portal Server Administration to change this path. If this location changes, the existing files move to the new location. By default, the log files are stored on the operating system drive in Program Files\SharePoint Portal Server\Data\Web Storage System.
Caution Do not modify other paths.
You can modify the parameter "apply indexing settings" in the .ini file to set the default content access account and gatherer e-mail address during the unattended installation. The default content access account is the user name and password used when crawling content outside the workspace. SharePoint Portal Server provides the gatherer e-mail address to each Web site it crawls when creating an index. If a problem occurs while crawling (for example, the crawler is hitting the site too much), the Web site's administrator can contact this address.
If apply indexing settings equals 0, the default content access account and gatherer e-mail address are not set when you run the unattended installation. You can set these options after installation by using SharePoint Portal Server Administration.
To specify the account and e-mail address, do the following:
Set apply indexing settings=1
Set Default Content Access Account= user_name , domain , password
Set gatherer e-mail address= someone@microsoft.com
Run setup:
On the taskbar, from the server on which you want to run setup, click Start, and then click Run.
In Open, type path_to_server_setup_file setup /UnattendFile path filename .ini where filename is the name of the .ini file that you created.
Click OK. You do not see the finish page or the New Workspace Wizard page.
Uninstalling or Repairing SharePoint Portal Server
The SharePoint Portal Server Setup Wizard automatically installs the client components of SharePoint Portal Server. If you uninstall SharePoint Portal Server, it automatically removes the client components. If you repair SharePoint Portal Server, it automatically repairs the client components as well.
If you remove SharePoint Portal Server from a computer that has SQL Server installed, SharePoint Portal Server does not remove the upgraded MSSearch because it is a shared service with SQL Server.
During the uninstall process, SharePoint Portal Server requires access to the original installation point to uninstall the Microsoft Embedded Exchange files. If the original installation point has moved, you can insert the SharePoint Portal Server CD into the CD-ROM drive to continue uninstalling. You can also point to the Server\Web Storage System directory at the installation point.
Before uninstalling SharePoint Portal Server, you must:
Verify that all command prompts are closed.
Remove any additional virtual roots mapped to the Web Storage System drive. The Web Storage System is mapped to network drive M by default.
If network drive M is already in use when you install SharePoint Portal Server, the Web Storage System is mapped to another network drive.
By default, this drive is disabled (it is not visible in My Computer). For more information about enabling this drive, see "Appendix B – IFS Drive and the Microsoft Web Storage System."
When you uninstall SharePoint Portal Server, all files and folders located in the installation directories are removed, including any user-created or modified files. The uninstall process also removes all workspaces. It is highly recommended that you restart the server after you uninstall SharePoint Portal Server.
The repair process requires at least one free network drive letter on the computer. If no drive is available, repair fails.
You can uninstall or repair a server by running SharePoint Portal Server setup. Alternatively, you can use Add/Remove Programs in Control Panel.
Client Setup
After you run SharePoint Portal Server setup, you can install the client components of SharePoint Portal Server on client computers across your network. The client functionality of SharePoint Portal Server is automatically included with Office XP.
The client components are extensions to Windows Explorer and Office applications. There is no individual client application. These extensions integrate SharePoint Portal Server commands with Windows Explorer and Office applications. Note that to take advantage of the Microsoft Office integration features of SharePoint Portal Server, Office 2000 or later is required. You can use other applications to create documents, but you cannot access SharePoint Portal Server commands from the menus within those applications. You must use Windows Explorer or a Web browser to perform SharePoint Portal Server document management tasks on documents created by using those applications.
You can install the client components by running setup either from the server or from the SharePoint Portal Server CD. By default, the SharePoint Portal Server Setup Wizard installs client installation files to the following location on the server: Program Files\SharePoint Portal Server\ClientDrop\Languages\Lang, where Lang corresponds to the language of the client. For information about installing additional languages, see "Installing the Client Components in Additional Languages."
Install the client components of SharePoint Portal Server by completing the following steps:
Review client hardware and software requirements outlined earlier in this paper.
Install the client components by running the Client Components for SharePoint Portal Server Setup Wizard.
Add a Web folder that points to the workspace.
There is a setup.ini file for the client components in Program Files\SharePoint Portal Server\ClientDrop\Languages\Lang. You can edit this file to specify the location of the SPSClient.msi file. You can also edit this file to specify the path and file name for the log file.
If you want to install the client components of SharePoint Portal Server in unattended mode, see "Using Unattended Installation Options for the Client" later in this section. If you want to uninstall or repair the client components, see "Uninstalling or Repairing Client Components" later in this section.
Installing the Client Components of SharePoint Portal Server
The following steps describe how to install the client components.
To install the client components
Log on to the client computer as a user with administrator privileges.
Connect to the location on the server where the client installation files are located. These files must be shared or otherwise available. By default, these files are located at Program Files\SharePoint Portal Server\ClientDrop\Languages\Lang, where Lang corresponds to the language of the client. If you want to install the client components from the CD, see below.
Double-click Setup.exe. The Client Components for SharePoint Portal Server Setup Wizard appears.
Follow the instructions that appear in the wizard.
If you want to install the client components from the SharePoint Portal Server CD, insert the SharePoint Portal Server CD into your CD-ROM drive, and then click Client Installation. The Client Components for SharePoint Portal Server Setup Wizard appears. You can also go to the Client folder on the CD, and then double-click Setup.exe.
The client components require Microsoft Data Access Components (MDAC) 2.5 or later. If this is not already present on the computer, the client installation process installs MDAC 2.5 SP1.
Adding a Web Folder
After you install the client components, you must add a Web folder that points to the workspace. The address of the workspace is https://server_name/workspace_name.
The procedure for adding a Web folder varies depending on your operating system. See your operating system Help for detailed instructions. For example, in Windows 2000 Professional, go to My Network Places and use the Add Network Place Wizard to add a Web folder that points to https://server_name/workspace_name. In Windows 98, go to Web Folders in My Computer, and use Add Web Folder to add a Web folder that points to https://server_name/workspace_name.
Using Unattended Installation Options for the Client
By default, you can install the client components by running the Client Components for SharePoint Portal Server Setup Wizard, which guides you through the installation process. You can also use Systems Management Server to install a client remotely on multiple computers in your organization. In addition, you can use Windows Installer directly to conduct an unattended installation of the client components.
If your server and client computers are both running Windows 2000 and are on a Windows 2000 domain, you can use Microsoft Active Directory® directory service to make the SharePoint Portal Server client setup program available to your users automatically.
Using Systems Management Server
SharePoint Portal Server provides a .pdf file that can be used with Systems Management Server to install the client components on multiple computers. The file SPSClient.pdf is located in the Client directory on the SharePoint Portal Server CD. SharePoint Portal Server also installs it on the server by default in Program Files\SharePoint Portal Server\ClientDrop\Languages\Lang, where Lang corresponds to the language of the client.
For more information, see the Systems Management Server product documentation.
After you install the client components, you must add a Web folder that points to the workspace. The address of the workspace is https://server_name/workspace_name.
Using Windows Installer
You can use Windows Installer to conduct an unattended installation of the client components if you are running Windows 2000 or Windows Millennium Edition, or if Windows Installer is present. By default, Windows Installer is installed with Office 2000 or later. Windows Installer is also installed by some other applications.
To install the client by using Windows Installer
On the taskbar, click Start, and then click Run.
In Open, type msiexec /qn /I " path \SPSClient.msi"
The quotation marks are required only if the path contains spaces. For example, if SPSClient.msi is on a file share called \\ServerName\SharePoint Portal Server Client Setup, quotation marks are required because of the spaces in "SharePoint Portal Server Client Setup." You would type msiexec /qn /I "\\ServerName\SharePoint Portal Server Client Setup\SPSClient.msi"
If your operating system is Windows 98 and Windows Installer is present, include the path to msiexec.exe. For example, if msiexec.exe is located in C:\Windows\System, type C:\Windows\System\msiexec /qn /I "C:\SharePoint Portal Server Client\SPSClient.msi"
You can also add the directory that contains msiexec.exe to the system path.
Click OK. SharePoint Portal Server installs the client without displaying user interface messages. Note that if the computer must be restarted, it is restarted automatically.
After you install the client components, you must add a Web folder that points to the workspace. The address of the workspace is https://server_name/workspace_name.
For more information about Windows Installer, including options other than unattended installations, see Windows Help on any computer on which Windows Installer is present.
Supported Command Line Parameters
The following table documents additional parameters available for both attended and unattended installation.
The command line parameters in the following table are supported for installing the client components of SharePoint Portal Server setup. No other parameters are supported.
Note: Specifying path_to_SPSclient.msi is optional if setup.exe, setup.ini, and SPSclient.msi are all in the same directory, and you execute the setup command from within that directory.
To do this |
Type this at the command prompt |
|---|---|
Install from the setup.ini file, which you have modified. User interaction is required. |
" path_to_client_setup.exe " /settings " |
Install the client components. User interaction is required. |
" path_to_client_setup.exe " /i " |
Repair the installation of the client components. For this option to work properly you must specify the path_to_SPSclient.msi or you receive an error. |
" path_to_client_setup.exe " /f " |
Uninstall the client components. User interaction is required. |
" path_to_client_setup.exe " /x " |
Display no user interface. Optionally display completion notice. No user interaction is required unless you choose to display the completion notice. |
With any of the above, insert /qn[+]. For example, " path_to_client_setup.exe " /qn+ /i " |
Display basic user interface. Optionally display completion notice. No user interaction is required unless you choose to display the completion notice. You see a status bar as the process progresses. |
With any of the above, insert /qb[+]. For example, " path_to_client_setup.exe " /qb /f " |
Display reduced user interface. No user interaction is required. You see the user interface, but it automatically progresses through the steps. |
With any of the above, insert /qr. For example, " path_to_client_setup.exe " /qr /x " |
Specify logging modes. |
With any of the above, insert /L[logging_modes|*] path_to_the_log_file to specify logging modes. For more information about logging modes, see Windows Help. Use * to log all information except for the v option. Using /Lv* path_to_the_log_file creates the most verbose logging available. For example, " path_to_client_setup.exe " /qr /i " |
Access help for using the parameters. |
" path_to_client_setup.exe " /? |
Using Group Policy and Active Directory
If you are a domain administrator on a Windows 2000 domain, you can use Group Policy and Active Directory to make the Client Components for SharePoint Portal Server setup program available to users. The program appears in Control Panel under Add/Remove Programs. Both the server and the client computers must be running Windows 2000.
Group Policy settings define the various components of the user's desktop environment that a system administrator can manage. To create a specific desktop configuration for a particular group of users, you use the Group Policy snap-in. Group Policy settings that you specify are contained in a Group Policy object, which is in turn associated with selected Active Directory objects—sites, domains, or organizational units.
Group Policy includes settings for User Configuration, which affects users, and Computer Configuration, which affects computers.
User policy settings are located under User Configuration and are obtained when a user logs on.
Computer policy settings are located under Computer Configuration and are obtained when a computer starts up.
You can use Group Policy to publish the client under User Configuration or Computer Configuration.
Publishing the Client Under User Configuration
When you publish the client under User Configuration, the user can then install the client components by using Add/Remove Programs in Control Panel.
Read the following known issues before publishing the client under User Configuration:
After one user on a particular computer adds the client by using Add/Remove Programs in Control Panel, the client files are present on the computer. However, another user cannot access Web folders until she adds the client also; the user receives an error stating that the folder entered does not appear to be valid even for valid folders.
If one user on a particular computer adds the client, and a new user attempts to add the client on that computer, the new user may see a screen prompting for uninstall or repair. The user sees this screen if you select Maximum for the Installation user interface options on the Deployment tab of the Properties page of the client package. Choosing repair activates client functionality for the new user. If you select Basic for the user interface option, the user sees only a progress bar when the client repairs. Each user of the computer must perform this action once. By default, only members of the local Administrators group can add the client.
If any user on the computer uninstalls the client, each user experiences automatic client repair upon the next access of the client components by opening a Web folder pointing to the workspace. If the user examines Add/Remove Programs in Control Panel prior to this automatic repair, the client is present, but the Change button is disabled (therefore preventing manual repair). The user corrects this by triggering the automatic repair, which is triggered by opening a Web folder. The user who uninstalled the client will still be unable to access client functionality unless he installs the client components again.
To see the client entry in Add/Remove Programs, the user may need to log off and then log on to the computer.
You can exclude specific users by denying them read access to the client package. The procedure to do this is provided below. The excluded users will not see the client components package in the Add Programs portion of Add/Remove Programs. Excluding computers in this way, for this type of deployment, has no effect (users on that computer can see and add the client). For computer exclusion, see the procedure under "Assigning the Client Under Computer Configuration."
If the client is manually installed on a computer (for example, from the SharePoint Portal Server CD) prior to the client being published, the client functionality is accessible to all users on the computer. If any user adds the program, they are prompted for repair or uninstall.
To use Active Directory (User Configuration) to make the client setup program available to users
Read the preceding known issues.
Copy the folder containing the client files to the domain controller computer.
You can copy the Client directory from the SharePoint Portal Server CD.
You can also find the folder containing the client files on the SharePoint Portal Server computer. SharePoint Portal Server installs this folder by default on the operating system drive under Program Files\SharePoint Portal Server\ClientDrop\Languages\Lang, where Lang corresponds to the language of the client. For example, on an English version of SharePoint Portal Server, you would copy the "enu" directory to the domain controller.
Share the folder containing the client files. When sharing, specify that anyone installing from the share has read access to it. You can use standard Windows 2000 security groups, or you can create your own specific groups. You can optionally enable or disable the other privileges, depending on the policy of your organization.
Add the Group Policy snap-in:
On the taskbar, click Start, and then click Run.
Type MMC and then click OK. The MMC console opens.
On the Console menu, click Add/Remove Snap-in. The Add/Remove Snap-in dialog box appears.
On the Standalone tab, click Add. The Add Standalone Snap-in dialog box appears.
In Available Standalone Snap-ins, click Group Policy, and then click Add. The Select Group Policy Object dialog box appears.
Click Browse. The Browse for a Group Policy Object dialog box appears.
On the Domains/OUs tab, click Default Domain Policy, and then click OK.
Click Finish to close the Select Group Policy Object dialog box. The Group Policy Object (Default Domain Policy) appears on the Standalone tab in the Add/Remove Snap-in dialog box.
Click Close to close the Add Standalone Snap-in dialog box.
Click OK.
Add the SharePoint Portal Server client package by using the Group Policy snap-in.
Expand the Default Domain Policy node.
Expand the User Configuration node.
Expand the Software Settings node.
Right-click Software installation, point to New, and then click Package.
Type the path to the folder that you copied in step 2, and then click Open.
Do not use local references such as c:\share. Type a share location, such as \\server\share. Otherwise, some users may not be able to access the deployed application.
Do not browse to this path.
Double-click SPSClient.msi. The Deploy Software dialog box appears.
Click Published, and then click OK.
Caution Do not choose the Assign option for the package. This option causes a program to be automatically installed when a shortcut to its application, or an associated file type, is accessed. The client components of SharePoint Portal Server do not have associated file types, nor is there any shortcut to activate the installation. Therefore, the installation would never be triggered. If you want to automatically install the client for all users, see the next section, "Assigning the Client Under Computer Configuration."
If you want to exclude specific users, do the following:
Expand the Default Domain Policy node.
Expand the User Configuration node.
Expand the Software Settings node.
Click Software installation.
In the details pane, right-click Client Components for Microsoft SharePoint Portal Server 2001, and then click Properties.
Click the Security tab, and then click Add.
Click the user to exclude, click Add, and then click OK.
On the Security tab, click the excluded user, select the Deny check box for the Read permission, and then click Apply.
Click Yes to continue when the caution message appears.
Click OK to close the Properties page.
To install the client components, the user simply uses Add/Remove Programs in Control Panel.
After installing the client components, the user must add a Web folder that points to the workspace. The address of the workspace is https://server_name/workspace_name.
Assigning the Client Under Computer Configuration
When you assign the client under Computer Configuration, the client software installs the next time that any computer managed by this group policy is restarted.
Read the following known issues before assigning the client under Computer Configuration:
If the client is deployed in this way, it is not installed on any computer affected by the deployment until that computer is restarted. It is recommended that only one application be assigned per restart in this way. Therefore, to deploy three applications, you would deploy one, restart the computer, deploy another, restart, deploy the third, and restart. This minimizes any interactions between the deployments.
You must exclude the following from the deployment by creating an excluded group.
Computers with SharePoint Portal Server installed.
Computers on which you want to install SharePoint Portal Server.
Other computers on which you do not want to install the client components.
After creating the group, you must deny access to it from the client package. These procedures are provided below.
If you do not add current SharePoint Portal Server computers to the excluded group and you deploy the client, the server functions properly until the next restart. After restarting, you cannot access properties on workspaces while working on the server. In addition, the Web folders on the server will lack SharePoint functionality. To correct this situation, add the server to the excluded group. Repair the server that was impaired, and then restart it. The server should now function properly.
If you add a SharePoint Portal Server computer to the domain without adding it to the excluded group, the server will not function properly when you restart it. You must add the server to the excluded group, repair the server, and then restart the server.
If you want to install SharePoint Portal Server on a computer that already has the client installed, you must add the computer to the excluded group, ensure that the excluded group is denied access to the client package, and then restart the computer before installing SharePoint Portal Server.
To use Active Directory (Computer Configuration) to make the client setup program available to users
Read the preceding known issues.
Copy the folder containing the client files to the domain controller computer.
You can copy the Client directory from the SharePoint Portal Server CD.
You can also find the folder containing the client files on the SharePoint Portal Server computer. SharePoint Portal Server installs this folder by default on the operating system drive under Program Files\SharePoint Portal Server\ClientDrop\Languages\Lang, where Lang corresponds to the language of the client. For example, on an English version of SharePoint Portal Server, you would copy the "enu" directory to the domain controller.
Create the excluded group.
On the taskbar, click Start, point to Programs, point to Administrative Tools, and then click Active Directory Users and Computers. If the Active Directory Users and Computers is not available on Administrative Tools, you can add it manually.
Expand the Active Directory Users and Computers node.
Right-click the domain name, point to New, and then click Group.
Type a name for the group in Group name.
Do not change the default Group scope and Group type.
Click OK.
Click the domain name node. The new group appears in the details pane.
Add members to the excluded group.
Right-click the group that you created in the previous step, and then click Properties.
Click the Members tab, and then click Add.
Select the computer to add, and then click Add. Add any servers on which you intend to install SharePoint Portal Server. In addition, add any servers on which you have already installed SharePoint Portal Server. You can also add other computers on which you do not want the client to install.
Click OK.
Click OK to close the Properties page.
Close Active Directory Users and Computers.
Add the Group Policy snap-in.
On the taskbar, click Start, and then click Run.
Type MMC and then click OK. The MMC console opens.
On the Console menu, click Add/Remove Snap-in. The Add/Remove Snap-in dialog box appears.
On the Standalone tab, click Add. The Add Standalone Snap-in dialog box appears.
In Available Standalone Snap-ins, click Group Policy, and then click Add. The Select Group Policy Object dialog box appears.
Click Browse. The Browse for a Group Policy Object dialog box appears.
On the Domains/OUs tab, click Default Domain Policy, and then click OK.
Click Finish to close the Select Group Policy Object dialog box. The Group Policy Object (Default Domain Policy) appears on the Standalone tab in the Add/Remove Snap-in dialog box.
Click Close to close the Add Standalone Snap-in dialog box.
Click OK.
Add the SharePoint Portal Server client package by using the Group Policy snap-in.
Expand the Default Domain Policy node.
Expand the Computer Configuration node.
Expand the Software Settings node.
Right-click Software installation, point to New, and then click Package.
Type the path to the folder that you copied in step 2, and then click Open.
Do not use local references such as c:\share. Type a share location, such as \\server\share. Otherwise, some users may not be able to access the deployed application.
Do not browse to this path.
Double-click SPSClient.msi. The Deploy Software dialog box appears.
Click Advanced published or assigned, and then click OK. The Properties page for the new package appears.
Note that if you close the Properties page at this point, you can later configure the settings in the steps below by reopening the Properties page.
On the Properties page, click the Deployment tab, and then click Advanced.
Clear both check boxes under Advanced deployment options, and then click OK.
Click the Security tab, and then click Add.
Click the excluded group that you created in step 3, click Add, and then click OK.
On the Security tab, click the excluded group, select the Deny check box for all permissions, and then click Apply.
Click Yes to continue when the caution message appears.
Click OK to close the Properties page.
The client software is installed the next time the computer is restarted.
After installing the client components, you must add a Web folder that points to the workspace. The address of the workspace is https://server_name/workspace_name.
Uninstalling or Repairing Client Components
You can uninstall or repair client components of SharePoint Portal Server by using Add/Remove Programs in Control Panel. You can also use the command line to remove or repair client components.
To remove or repair the client components by using the command line
On the taskbar, click Start, point to Programs, point to Accessories, and then click Command Prompt.
Type " path \setup" switch " path \SPSClient.msi"
where path is the path to the setup.exe and SPSClient.msi files. Use the /x switch to uninstall the client components. Use the /f switch to repair the client components.
For example, to remove the client components, where setup.exe and SPSClient.msi are in E:\Client Files, you would type
"E:\Client Files\setup" /x "E:\Client Files\SPSClient.msi"
To repair the components in the preceding example, you would type
"E:\Client Files\setup" /f "E:\Client Files\SPSClient.msi"
When you uninstall the client components, the User's Help (webfoldr.chm) file remains. It replaces the original Web folders Help file.
Note that if you remove one or more of the installation prerequisites, you cannot uninstall or repair the client components unless you disable the prerequisite check.
You disable the prerequisite check by adding DISABLEPREREQ=1 to the command line. To disable the prerequisite check in the preceding examples:
When removing the client components, you would type
"E:\Client Files\setup" /x "E:\Client Files\SPSClient.msi" DISABLEPREREQ=1
When repairing the client components, you would type
"E:\Client Files\setup" /f "E:\Client Files\SPSClient.msi" DISABLEPREREQ=1
Installing the Client Components in Additional Languages
SharePoint Portal Server ships with a client install for a single language. Users can install any language of the client to operate against a server. Client installs for additional languages can be downloaded from the Web site for SharePoint Portal Server, https://www.microsoft.com/sharepoint/default.mspx.
Note that if you install Office XP in one language and the client components of SharePoint Portal Server in another language, the user interface may display in either of the two languages.
Troubleshooting Installation
Troubleshoot Server Installation Problems
This section addresses problems and possible solutions associated with installing SharePoint Portal Server on a server computer.
Gather Information from the Server Installation Logs
You can examine the following logs for information about server installation:
Errorlog.txt file.?This file is located in Program Files\Microsoft Integration\SharePoint Portal Server\Logs. For failed installations, this file may be located in the %temp% directory instead, depending on the stage of the installation process when the failure occurred. The error "VAIFY Failed" tells you that the portion of setup that configures default SharePoint Portal Server settings in the Web Storage System failed.
Setup may experience a nonfatal error that documents an ordering problem. The errors in the log may report one or more lines of the following:
[Date, Time] Dependency Manager: [2] Ordering problem: Microsoft SharePoint Portal Server Microsoft Search
The ordering problem could originate from MSSearch, SharePoint Portal Server, or a combination of these. The installation program is simply informing you that the order in which things are installing is different from the order SharePoint Portal Server requested. This error message is benign and is safe to ignore.
If you are running unattended server installation, the log reports the following two errors, which are benign and safe to ignore:
[Date, Time] setup.exe: [2] ISetupManager::AddGlobalCustomProperty() called with an existing custom property (GUID)
[Date, Time] setup.exe: [2] ISetupManager::AddGlobalCustomProperty failed in ISetupManager::LoadPersistantData()
Eventlog.txt file.?This file is located in Program Files\Microsoft Integration\SharePoint Portal Server\Logs. For failed installations, this file may be located in the %temp% directory instead, depending on the stage of the installation process when the failure occurred. This file contains a detailed list of the actions performed during the installation. Lines that contain errors are copied to Errorlog.txt.
Some of the events in this log appear in English even on non-English systems. The events are useful to Microsoft Support for diagnosis of reported problems. In most cases, users can safely ignore these events.
Setup.log file.?This file is located in Program Files\Microsoft Integration\SharePoint Portal Server\Logs.
Spsclisrv.Log file.?This file is located in Program Files\Microsoft Integration\SharePoint Portal Server\Logs for successful server installations.
Exchange Server Setup Progress.log file.?This file is located at the root of the operating system drive. This log tells you if the Web Storage System installed correctly. It can help you identify issues such as:
A server name has an illegal character.
IIS 5.0 is not installed, so the Web Storage System cannot be installed.
SMTP service is not installed. This is a Windows 2000 Server component.
Note that when you install SharePoint Portal Server on a Japanese operating system, the Exchange Server Setup Progress log is unreadable when opened with Notepad, which is the typical association for .log files. To view the log, open it as a Unicode file in Microsoft Word.
You can find information about VAIfy errors in the Application Log in Windows 2000 Event Viewer (commonly referred to as the Windows 2000 event log).
If SharePoint Portal Server does not install on your computer:
SharePoint Portal Server does not install if any of the following are on the computer:
An unsupported operating system. Only Windows 2000 Server and Advanced Server, SP1 or later, are supported.
Windows 2000 Hot fix (Pre-SP2) 269862. This hot fix cannot be installed on the computer. If it is installed, remove it before installing SharePoint Portal Server.
Exchange 2000 Server.
Exchange 2000 Enterprise Server.
Exchange Server version 5.5 and earlier.
Site Server (any version).
Office Server Extensions.
SharePoint Portal Server is not supported in a clustered environment. You cannot install SharePoint Portal Server in a clustered environment, and you must not join the SharePoint Portal Server computer to a clustered environment.
For information about the server requirements, see "Hardware and Software Requirements" earlier in this paper.
The setup process (for both installation and repair) requires at least one free network drive letter on the computer. If no drive is available, setup fails. The Exchange Server Setup Progress.log file notes that no free drive was available.
If server installation fails:
SharePoint Portal Server requires the Default Web Site in IIS to use port 80 as the TCP port for localhost. Before installing SharePoint Portal Server, ensure that 80 is specified as the TCP port. Additionally, do not change the port to an alternative HTTP port (such as 8000 or 8080) after installation. Ensure that port 80 is specified and remains as the primary port for the server. To do this:
On the taskbar, click Start, point to Programs, point to Administrative Tools, and then click Internet Services Manager.
Expand the node for the computer on which you want to install SharePoint Portal Server.
Right-click Default Web Site, and then click Properties.
On the Web Site tab, click Advanced.
Ensure that under Multiple identities for this Web Site, (All Unassigned) is specified as TCP port 80. If it is specified as port 80, click Cancel and go to step 7. If it is not specified as port 80 or is not listed, do one of the following:
If (All Unassigned) is not set to port 80, select (All Unassigned), and then click Edit. In TCP Port, type 80 and then click OK.
If (All Unassigned) is not is not listed, click Add. In IP Address, select (All Unassigned). In TCP Port, type 80 and then click OK.
Click OK.
Click OK to close the Properties page.
Restart the server before installation. You do not need to restart the server if you did not change any settings in step 5.
Important: Other configurations may be acceptable, as long as "localhost" on port "80" is a valid way to connect to W3SVC/1 (the Default Web Site) on the computer.
If setup is very slow or fails after long periods of inactivity:
Are you installing from CD with a slow CD drive?
Setup may slow due to insufficient memory or excessive network traffic. Consider the following possibilities:
Does your system meet the recommended processor and RAM requirements?
If you are installing over a network, is your network experiencing slow or impaired operations?
If setup fails when installing on a system upgraded from Windows NT 4.0:
Installing SharePoint Portal Server on a system that has been upgraded from Windows NT 4.0 can cause install failures. You should install SharePoint Portal Server on a clean Windows 2000 Server. If you are installing on a Windows 2000 system that was upgraded from Windows NT 4.0, manually register the oledb32.dll file before installation to avoid installation failure. To do this:
On the taskbar, click Start, point to Programs, point to Accessories, and then click Command Prompt.
Go to Program Files\Common Files\System\Ole DB on the operating system drive.
Type regsvr32 oledb32.dll
If setup fails with a VAIfy error:
If SharePoint Portal Server installation fails with a "VAIfy failed" error in errorlog.txt:
Verify that MDAC is installed correctly by running the Component Checker tool (ComCheck.exe) available at https://msdn.microsoft.com/library/default.asp?url=/nhp/default.asp?contentid=28001169. Use this tool to verify that the MDAC version is 2.5 or later and the MDAC dynamic-link libraries (DLLs) are correct.
If you find an error and need to reinstall MDAC 2.5 on your Windows 2000 server, do the following:
Display hidden files.
On the operating system drive, right-click winnt\inf\mdac.inf, and then click Install. You may be prompted for your Windows 2000 installation disc or service pack files location.
If you are running MDAC 2.6 and need to reinstall it, install it from the original source or download it from the Microsoft Web site.
Ensure that W3SVC/1 (Default Web Site in IIS) is started:
On the taskbar, click Start, point to Programs, point to Administrative Tools, and then click Internet Services Manager.
Expand the node for the SharePoint Portal Server computer.
Right-click the Web site located at W3SVC/1. By default, this site is named Default Web Site.
Click Start. If Start appears dimmed, W3SVC/1 is already started.
You can also find information about VAIfy errors in the Application Log in Windows 2000 Event Viewer (commonly referred to as the Windows 2000 event log).
If workspace virtual directories show the error "stop sign" symbol in the IIS snap-in:
This is a benign error. If World Wide Web Publishing Service (W3SVC) starts before MSExchangeIS, "stop sign" symbols appear under the Default Web Site folder of the Internet Information Services console in MMC.
There is a dependency between the local paths of the SharePoint Portal Server virtual directories and MSExchangeIS. You must start MSExchangeIS first, followed by W3SVC.
Complete the following steps to prevent the stop signs from appearing each time you restart:
Change the Startup type for W3SVC to Manual.
Restart the server. The MSExchangeIS service starts automatically.
Start W3SVC.
If the server no longer functions:
Did you uninstall any of the server prerequisites after installing SharePoint Portal Server? SharePoint Portal Server requires:
Windows 2000 Server or Advanced Server SP1 or later operating system.
IIS 5.0.
SMTP service. This is a Windows 2000 Server component.
Did you install software that does not coexist with SharePoint Portal Server after installing SharePoint Portal Server?
Are all required services running?
Did you attempt to configure security by using the IFS drive?
For more information about server requirements, see "Hardware and Software Requirements" earlier in this paper.
Troubleshoot Client Installation Problems
This section addresses problems and possible solutions associated with installing the client components for SharePoint Portal Server.
If client installation fails:
The client installation can fail if the computer does not meet the basic installation requirements. Consider the following possibilities:
Do you have Internet Explorer 5 or later installed on the client computer? Internet Explorer 5 or later is required.
Do you have Outlook Express 5 or later installed on the client computer? Outlook Express 5 or later is required.
Are you attempting to install the client components of SharePoint Portal Server on Windows 95? The client components do not install on Windows 95.
If you are attempting to install the client components on Windows NT 4.0, do you have SP6A or later installed?
Are you an administrator on the client computer?
For more information about client requirements, see "Hardware and Software Requirements" earlier in this paper.
If you experience recurring installation errors:
If you experience recurring errors, a detailed log file can help you diagnose the problem. To run setup with a detailed log file:
Go to the directory containing setup.exe for the client components.
On the taskbar, click Start, point to Programs, point to Accessories, and then click Command Prompt.
Type setup /L*v " path_and_file_name_for_the_log_file "
For example, if you want to store the log file named clientsetup.log in the Client Setup directory on drive C, type setup /L*v "C:\Client Setup\clientsetup.log"
If you require assistance interpreting the information in the log file, you can call Microsoft Product Support Services.
If you do not see the SharePoint Portal Server client in the Programs menu:
This is by design. The client components of SharePoint Portal Server are extensions to Windows Explorer and Microsoft Office applications. There is no individual client application. Instead, SharePoint Portal Server commands are integrated into the menus of Windows Explorer, Microsoft Word, Microsoft Excel, and Microsoft PowerPoint®.
Important: You can use other applications to create documents, but you cannot access SharePoint Portal Server commands from the menus within those applications.
You must use Windows Explorer or a browser to perform SharePoint Portal Server document management tasks on documents created from within other applications.
Conclusion
The previous sections provide installation procedures and troubleshooting information. The appendixes provide information about the operating system and browser support, the IFS drive and the Web Storage System, and proxy server settings used by SharePoint Portal Server.
Appendix A – Operating System and Browser Support
The following table shows the operating system and browser support for SharePoint Portal Server.
Operating system |
Server support |
Client support |
Browser support (for dashboard site/Web access only) |
|---|---|---|---|
Microsoft Windows 95 |
No |
No |
Yes |
Windows 98 |
No |
Yes (Note 1) |
Yes |
Windows NT 4.0 (SP6a) |
No |
Yes (Note 1) |
Yes |
Windows 2000 Professional |
No |
Yes |
Yes |
Windows 2000 Server |
Yes (Note 2) |
Yes |
Yes |
Windows 2000 Advanced Server |
Yes (Note 2) |
Yes |
Yes |
Windows 2000 Datacenter Server |
No |
No |
Yes |
Windows Millennium Edition |
No |
Yes (Note 1) |
Yes |
Windows XP Home Edition |
No |
Yes |
Yes |
Windows XP Professional |
No |
Yes |
Yes |
Systems with Internet Explorer 5 or later |
Yes |
Yes |
Yes |
Systems with Office XP |
Yes |
Yes |
Yes |
Supported Browsers (dashboard site/Web access only):
Internet Explorer 4.x and later running on the Windows operating system
Netscape Communicator 4.7x running on the Windows operating system
Note 1 Windows 98, Windows Millennium Edition, and Windows NT 4.x computers do not support coordinator functions such as scheduling updates and configuring content sources, tasks performed by using MMC, or Web views. In addition, on computers running Windows 98 or Windows NT 4.x, you cannot access User's Help from the workspace by using F1 or the Help menu. To access User's Help when using these operating systems, click the User's Help page in the workspace, and then click the User's Help link on that page.
Note 2 Before you install SharePoint Portal Server on Windows 2000 Server or Windows 2000 Advanced Server, install Windows 2000 Service Pack 1 or later.
Appendix B – IFS Drive and the Microsoft Web Storage System
The IFS provides access to the Web Storage System that SharePoint Portal Server uses. By default, IFS is not mounted during the installation of SharePoint Portal Server.
You can use IFS access for the following tasks:
Read-only access to the document library
Microsoft FrontPage® Server Extensions
Web Storage System development through IFS
Server administrators can access the IFS by using Windows Explorer on the SharePoint Portal Server computer. SharePoint Portal Server typically maps IFS to network drive M, unless there is already a mapping that uses that drive. Although you can use IFS to view the contents of the Web Storage System that SharePoint Portal Server uses, this access is read-only.
Note: It is strongly recommended that you do not use IFS (network drive M) to create SharePoint Portal Server folders or documents, assign security to folders or documents, or edit properties for folders or documents. SharePoint Portal Server roles and configuration options are available through the supported Web folders interface. Manipulating the IFS security attributes may interfere with the roles information associated with SharePoint Portal Server, which results in data loss. Workspace management functions, such as creating document profiles, are also available through the Web folders interface only. In addition, do not use Microsoft ActiveX® Data Objects (ADO) or OLE DB to configure security on SharePoint Portal Server folders or documents.
SharePoint Portal Server setup uses drive M during setup and repair. This has the following issues:
Drive M is added to the backup exclusion list for NT backup. You will not see any drives mounted as M: under the NT backup utility. You can reset this by using the backup utility for NT.
If there are no free drive letters, the repair option of setup fails. For the repair option to succeed, you must disconnect another drive.
You can mount drive M temporarily by doing the following:
On the taskbar, click Start, point to Programs, point to Accessories, and then click Command Prompt.
Type subst M: \\.\backofficestorage and then press ENTER.
If drive M is already mapped, you can use any available drive letter.
If the drive does not appear after running the command above, restart the server and run the command again.
You can access the drive until you restart the server.
To permanently mount drive M, you must edit the registry. To do this:
On the taskbar, click Start, and then click Run.
Type regedit, and then click OK.
Caution Incorrectly editing the registry may severely damage your system. Before making changes to the registry, you should back up any valued data on the computer.
In Registry Editor, go to HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\EXIFS\ Parameters.
Click Parameters.
In the details pane, right-click DriveLetter, and then click Modify.
In Value data, type M and then click OK. If drive M is already mapped, you can use any available drive letter.
Close Registry Editor.
Restart the server.
Appendix C – Proxy Server Settings in SharePoint Portal Server
Changing Proxy Server Settings in SharePoint Portal Server
If you want to change your proxy settings for the SharePoint Portal Server computer at some time after installation, perform the following steps:
Configure the proxy server settings for your SharePoint Portal Server computer.
On the taskbar of the computer on which you are installing SharePoint Portal Server, click Start, point to Settings, and then click Control Panel.
Double-click Internet Options. The Internet Properties dialog box appears.
Click the Connections tab, and then click LAN Settings.
Clear both check boxes under Automatic configuration.
Do one of the following:
If you use a proxy server, select the Use a proxy server check box, type a valid proxy server address and port number, and then select the Bypass proxy server for local addresses check box.
If you do not use a proxy server, clear all check boxes. For important information regarding the use of SharePoint Portal Server without a proxy server, see step 3.
Click OK to apply the changes, and then click OK to close Internet Properties.
Configure the proxy server settings used by the gatherer. SharePoint Portal Server uses this setting when it creates indexes of external Web sites.
Use SharePoint Portal Server Administration to configure this setting on the Proxy Server tab of the Properties page for the server. For more information about configuring the proxy server settings used by the gatherer, see "Specify Proxy Server Options" under "Managing Servers" in Administrator's Help.
Configure the proxy server settings for the dashboard site.
To enable SharePoint Portal Server to import Web Parts to the dashboard site, the server administrator must use a tool called proxycfg.exe, located under the SharePoint Portal Server \Bin directory. The location of this directory depends on the location of the SharePoint Portal Server installation directory.
Important: You must run proxycfg.exe even if you are not using a proxy server.
Using SharePoint Portal Server with a Proxy Server
If you are using a proxy server, run the following command, which uses the settings specified in step 1: proxycfg –u
For more information about proxycfg.exe, see "Configure the Dashboard Site to Work with a Proxy Server" under "Advanced Topics" in Administrator's Help.
Using SharePoint Portal Server Without a Proxy Server
Out of the box, SharePoint Portal Server is not configured to run with direct Internet connectivity. SharePoint Portal Server is initially configured for use with a proxy server. If you are not using a proxy server, see https://www.microsoft.com/sharepoint/default.mspx for the white paper titled "Deploying Microsoft SharePoint Portal Server across an Extranet" for important information about the proxy settings.
When using Fully Qualified Domain Names (FQDNs) on an intranet (this does not apply to the extranet):
Users must configure browser proxy server settings on client computers to bypass the proxy server for local addresses on each client computer accessing the dashboard site if:
Your network does not natively support FQDN.
You are running Windows Internet Naming Service (WINS).
Users experience errors navigating to the dashboard site by using FQDN.
In addition, server administrators must configure the Internet Explorer proxy settings on the SharePoint Portal Server computer to include the domain of the local computer on the bypass list.
Each user and the server administrator can configure the proxy server settings by using the procedure below. This procedure applies when your browser is Internet Explorer 5. To do this on other browsers, consult the browser documentation.
To configure the proxy server settings when using Internet Explorer:
On the Tools menu, click Internet Options.
On the Connections tab, click LAN Settings.
Select the Use a proxy server and Bypass proxy server for local addresses check boxes.
Specify the address and port number of the proxy server, and then click Advanced.
In Do not use proxy server for addresses beginning with, type * domain
where domain is the domain of your SharePoint Portal Server. For example, if the domain is adventure-works.com, type *adventure-works.com.
Click OK, and then close the remaining dialog boxes.
Restart the server after configuring the proxy settings.
Undoing Proxy Settings Modified by the Setup Process
During the installation of SharePoint Portal Server, the setup process changes the proxy settings for the server from per-user to per-computer.
If you later uninstall SharePoint Portal Server, you can change the proxy settings back to per-user on the computer. This allows each individual user on the server to configure specific proxy settings.
The server administrator change proxy settings to per-user by doing the following:
Open Group Policy as a stand-alone MMC snap-in:
On the taskbar, click Start, and then click Run.
Type MMC and then click OK. The MMC console opens.
On the Console menu, click Add/Remove Snap-in. The Add/Remove Snap-in dialog box appears.
On the Standalone tab, click Add. The Add Standalone Snap-in dialog box appears.
In Available Standalone Snap-ins, click Group Policy, and then click Add. The Select Group Policy Object dialog box appears. By default, the Group Policy Object is specified as Local Computer.
Click Finish to close the Select Group Policy Object dialog box. The Group Policy Object (Local Computer Policy) appears on the Standalone tab in the Add/Remove Snap-in dialog box.
Click Close to close the Add Standalone Snap-in dialog box.
Click OK.
Use the Group Policy snap-in to change the proxy settings per-user:
Expand the Local Computer Policy node.
Expand the Computer Configuration node.
Expand the Administrative Templates node.
Expand the Windows Components node.
Click Internet Explorer.
In the details pane, right-click Make proxy settings per-computer (rather than per-user), and then click Properties.
On the Policy tab, click Not Configured.
Click OK to close the Properties page.
Each individual user on the server must reconfigure his proxy settings.