Troubleshooting Installation Issues (Windows SharePoint Services 2.0)

  • Article

Cannot Connect to the Configuration Database Message

  • I get a "cannot connect to the configuration database" message when I try to set the configuration database for Microsoft Windows SharePoint Services.

    If the password associated with the account used to connect to Microsoft SQL Server has expired or changed, you will see a "cannot connect to the configuration database" message until you reset the password in SQL Server. For more information about changing passwords in SQL Server, see Help in SQL Server Enterprise Manager.

    Note

    You may also see a "service unavailable" message if the password for an Internet Information Services(IIS) application pool identity has changed or expired. For more information about changing passwords for application pool identities, see "Service Unavailable Message" in Troubleshooting Other Issues (Windows SharePoint Services 2.0).

    This message may also appear if Internet Information Services (IIS) is running in IIS 5.0 compatibility mode. Windows SharePoint Services requires IIS 6.0 to be running in IIS 6.0 worker process isolation mode. To change to IIS 6.0 worker process isolation mode, in IIS Manager, right-click Web Sites and then click Properties. On the Service tab, clear the Run WWW service in IIS 5.0 isolation mode check box.

Extending a Virtual Server

  • I installed Windows SharePoint Services, but I can't extend a virtual server.

    Is your file system formatted with FAT instead of NTFS? If you installed Windows SharePoint Services to a disk drive formatted with the FAT file system, your default virtual server might not be extended. On the Microsoft Windows platform, the security features of Windows SharePoint Services require the NTFS file system. For more information, see Hardware and Software Requirements (Windows SharePoint Services 2.0).Does the virtual server exist in Internet Information Services? Before you can extend a new virtual server with Windows SharePoint Services, you must create the virtual server by using the IIS Manager. For more information, see Extending Virtual Servers (Windows SharePoint Services 2.0).

  • When I extended a virtual server, I created a new application pool, but entered an account that is used for an existing application pool. I got a message that I need to restart IIS, or I cannot access my virtual server.

    If you attempt to reuse an existing IIS application pool account (that is not currently used for a virtual server running Windows SharePoint Services), you must restart IIS before you can access the virtual server.

    Warning

    Reusing an account from a non-Windows SharePoint Services application pool is not secure, and is not recommended. You can reuse an application pool account that is already being used for Windows SharePoint Services or that was previously used for Windows SharePoint Services.

    To restart IIS, on the command line, type iisreset.

  • When I try to extend a virtual server, I get an error message that FrontPage Server Extensions or SharePoint Team Services 1.0 from Microsoft is installed on the default virtual server.

    You must remove FrontPage Server Extensions or SharePoint Team Services 1.0 before you can extend the default virtual server. You can extend a different virtual server if you want to continue running FrontPage Server Extensions or SharePoint Team Services 1.0. For more information about upgrading to Windows SharePoint Services, see Upgrade Considerations (Windows SharePoint Services 2.0). For information about migrating site content from FrontPage Server Extensions or SharePoint Team Services 1.0 to Windows SharePoint Services, see Migrating and Upgrading Web Sites (Windows SharePoint Services 2.0).

    Remove FrontPage 2002 Server Extensions from a virtual server

    1. Click Start, point to All Programs, point to Administrative Tools, and then click Microsoft SharePoint Administrator.

    2. In the list of virtual servers, next to the virtual server name, click Administration.

    3. On the Virtual Server Administration page, click Uninstall FrontPage 2002 Server Extensions.

    4. On the Uninstall FrontPage 2002 Server Extensions page, next to Full Uninstall, click Yes.

    5. Click Uninstall.

    After you remove FrontPage 2002 Server Extensions, you must restart IIS by running iisreset on the command line before you can try extending the virtual server again.

    Note

    If you have already uninstalled FrontPage Server Extensions or SharePoint Team Services 1.0 from the default virtual server, but you still see this message, you may need to delete the _vti_pvt\service.cnf file manually. This file is in the content folder for the virtual server (usually c:\inetpub\wwwroot). _vti_pvt is a hidden folder, so you must unhide it before you can locate and delete the service.cnf file.

  • When I try to extend a virtual server, I get a message that the request timed out.

    If the request to extend a virtual server times out, you can try the following workarounds:

    1. Check to see whether full-text searching is enabled for your server or server farm. If it is enabled, turn it off, and then extend the virtual server. After the virtual server is extended, you can enable full-text searching again. For more information about configuring full-text searching, see Managing and Customizing Search (Windows SharePoint Services 2.0).

    2. Change the timeout length for the process. To change the timeout length, you must edit the web.config file for the administration virtual server. This file is in the Windows SharePoint Services installation folder, at \Program Files\Common Files\Microsoft Shared\Web Server Extensions\60\template\admin\LCID, where LCID is the locale ID, such as 1033 for U.S. English. Add the following to the web.config file in the <system.web> section: <httpRuntime executionTimeout="999999"/>. After you edit the web.config file, you must reset IIS by running iisreset on the command line.

  • I extended a new virtual server, and the usage analysis processing is not working for the new virtual server. If usage analysis processing was configured before you extended the virtual server, it must be enabled manually for the new virtual server. For more information, see Usage Analysis in Troubleshooting Other Issues (Windows SharePoint Services 2.0).

Installing on Windows Server 2003, Web Edition

  • I am installing on Microsoft, Web Edition, and the installation ends without installing Windows SharePoint Services or extending a virtual server.

    You must use the remotesql=yes property to install Windows SharePoint Services on, Web Edition. For more information about installing Windows SharePoint Services to work with Microsoft SQL Server 2000, see Remote SQL Server Deployment (Windows SharePoint Services 2.0).

Page Cannot Be Found Message

  • After I have installed Windows SharePoint Services, I get a "page cannot be found" message when the SharePoint Central Administration page tries to open.

    Windows SharePoint Services requires ASP.NET to run. If you already had an instance of ASP.NET running when you installed Windows SharePoint Services, it is possible that you now have two ASP.NET installations on the same server. In this case, the new installation of ASP.NET may be prohibited in IIS. You must enable the new instance of ASP.NET before the SharePoint Central Administration pages can run. To enable the new instance of ASP.NET, in IIS Manager, click Web Service Extensions. In the list of Web Service Extensions, select the new instance of ASP.NET, and then click Allow.

Reusing Application Pools

  • I have an existing application pool that I want to use for a virtual server that I am extending with Windows SharePoint Services.

    If you reuse an existing application pool when you extend a virtual server, the application pool account will not be automatically added to the local IIS_WPG and STS_WPG groups (the application pool groups for Internet Information Services(IIS) and Windows SharePoint Services), and any new sites that you create will not be accessible.

    If the application pool was created when you extended a different virtual server with Windows SharePoint Services, the application pool may already be part of these groups. If, however, the application pool was used for another purpose, and you want to use it with Windows SharePoint Services, you must manually add the application pool account to these groups. For more information about adding an account to a local group, see Help in.

Running on a Domain Controller

  • I installed Windows SharePoint Services to a computer, and then made the computer a domain controller. Now when I go to SharePoint Central Administration or to a page in my SharePoint site, I see a "file not found" error, or an "access denied" error.

    In order for the permissions for Windows SharePoint Services to be configured correctly, IIS and Windows SharePoint Services must be installed to the domain controller after it is promoted to domain controller. If you have already installed IIS and Windows SharePoint Services to a computer, and you now need to make that computer a domain controller, you must uninstall IIS and Windows SharePoint Services, promote the computer to domain controller, and then reinstall IIS and Windows SharePoint Services. For more information about running IIS on a domain controller, see the IIS documentation.

Site Migration Error When Migrating a Site from

  • I am migrating a site from SharePoint Team Services 1.0 and I get the following message: 1376258 The server administration programs and the server extensions on the Web server are not compatible. The server is too old to use with this administration program.

    Before you can use the Microsoft SharePoint Migration Tool (smigrate.exe) to migrate sites from SharePoint Team Services 1.0 to Windows SharePoint Services, you must verify that you are running the update to Windows SharePoint Services that updates it to function better with the SharePoint Migration Tool. To download this update, go to Office XP Web Services Security Patch: KB812708 (https://go.microsoft.com/fwlink/?LinkId=104236\&clcid=0x409).

Typical Installation Ends Without Creating a Site

  • I am installing Windows SharePoint Services on a single server, using the Typical Installation option. When Setup ends, I get an error that the server instance specified was not found.

    If the Default Web Site in IIS is set to a port other than port 80, the Typical Installation for Windows SharePoint Services may end without creating a site. Use the SharePoint Central Administration pages to extend the Default Web Site virtual server and create a Web site manually. For more information, see Extending Virtual Servers (Windows SharePoint Services 2.0).