Troubleshooting

The following sections address problems and possible solutions associated with installing SharePoint Portal Server. The first section reviews problems and possible solutions for server installations. The second section presents problems and possible solutions for client component installations.

Troubleshooting Server Installations

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 Microsoft 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 is not installed, so the Web Storage System cannot be installed.
    • SMTP service is not installed. This is a Windows 2000 Server component.

    When you install SharePoint Portal Server on a Japanese operating system, the Exchange Server Setup Progress log is unreadable when opened with Microsoft Notepad, which is the typical association for .log files. To view the log, open it as a Unicode file in Microsoft Word.

For more information about VAIfy errors, see Appendix B.

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) Q269862. This hotfix cannot be installed on the computer. If it is installed, remove it before installing SharePoint Portal Server.
  • Exchange 2000 Server or Exchange 2000 Enterprise Server.
  • Exchange Server version 5.5 and earlier.
  • Microsoft Site Server (any version).
  • Microsoft 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 chapter.

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 you specify 80 as the TCP port. Additionally, do not change the port to an alternative HTTP port (such as 8000 or 8080) after installation.

To ensure that port 80 is specified and remains as the primary port for the server:

  1. On the taskbar, click Start, point to Programs, point to Administrative Tools, and then click Internet Services Manager.
  2. Expand the node for the computer on which you want to install SharePoint Portal Server.
  3. Right-click Default Web Site, and then click Properties.
  4. On the Web Site tab, click Advanced.
  5. 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 the TCP Port box, type 80 and then click OK.
    • If (All Unassigned) is not listed, click Add. In IP Address, select (All Unassigned). In the TCP Port box, type 80 and then click OK.
  6. Click OK.
  7. Click OK to close the Properties page.
  8. Restart the server before installation. You do not need to restart the server if you did not change any settings in step 5.

    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

Setup may slow due to insufficient memory or excessive network traffic. Consider the following possibilities:

  • Are you installing from a CD with a slow CD-ROM drive?
  • 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

Installing SharePoint Portal Server on a system that has been upgraded from Windows NT 4 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, you must manually register the Oledb32.dll file before installation to avoid installation failure.

To manually register the Oledb.32.dll file:

  1. On the taskbar, click Start, point to Programs, point to Accessories, and then click Command Prompt.
  2. Go to Program Files\Common Files\System\Ole DB on the operating system drive.
  3. Type regsvr32 oledb32.dll

If Setup Fails with a VAIfy Error

Installing SharePoint Portal Server may result in VAIfy errors in Errorlog.txt. There are several troubleshooting steps that you can take to investigate this problem.

To troubleshoot a "VAIfy failed" error in Errorlog.txt:

  1. Verify that MDAC is installed correctly by running the Component Checker tool (ComCheck.exe) available at http://www.microsoft.com/data/download.htm - ccinfo. 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 http://www.Microsoft.com.

  2. Ensure that W3SVC/1 (the 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 W3SVC starts before Microsoft Exchange Information Store (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.

To prevent the stop signs from appearing each time you restart, complete the following steps:

  1. Change the Startup type for W3SVC to Manual.
  2. Restart the server. The MSExchangeIS service starts automatically.
  3. 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.
    • 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 chapter.

Troubleshooting Client Installations

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, 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 chapter.

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:

  1. Go to the directory containing Setup.exe for the client components.
  2. On the taskbar, click Start, point to Programs, point to Accessories, and then click Command Prompt.
  3. 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 Office applications. There is no individual client application. Instead, SharePoint Portal Server commands are integrated into the menus of Windows Explorer, Word, Microsoft Excel, and Microsoft PowerPoint®.

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.



Microsoft Sharepoint Portal Server 2001 Resource Kit
Microsoft SharePoint(TM) Portal Server 2001 Resource Kit (Examples & Explanations Series)
ISBN: 0735615624
EAN: 2147483647
Year: 2001
Pages: 231

flylib.com © 2008-2017.
If you may any questions please contact us: flylib@qtcs.net