Export (0) Print
Expand All

Deploy software updates for Office Forms Server 2007

Office 2007

Updated: July 23, 2009

Applies To: Office Forms Server 2007

 

Topic Last Modified: 2009-05-11

In this article:

We recommend that you follow the process and procedures in this topic for most deployment scenarios, from stand-alone server deployments to very large server farms. The typical process for installing software updates consists of copying the files to a computer and then running either the SharePoint Products and Technologies Configuration Wizard or the Psconfig command-line tool to upgrade the databases.

NoteNote:
In this article, we use the term software update as a general term for all update types, including any service pack, update, update rollup, feature pack, critical update, security update, or hotfix used to improve or fix this software product.

If you chose Basic installation (single server with Microsoft SQL Server Desktop Engine) when you installed your Web server running Microsoft Office Forms Server 2007, you do not need to follow the process and procedures in this topic. In this case, if you have Automatic Updates enabled, your computers are updated automatically. If you do not have Automatic Updates enabled, you can use the Windows Update Web site to install the software updates. After the software update is installed, the SharePoint Products and Technologies Configuration Wizard runs automatically to update the databases for SharePoint Products and Technologies. In this scenario, the SharePoint Products and Technologies Configuration Wizard will not prompt for user input or display any notifications.

For any deployment other than single server, such as Web servers in a server farm, you must visit the Microsoft download center to download and then install the software update. The software update will not be installed automatically, even if Automatic Updates is enabled on your Web servers, and you cannot use the Windows Update Web site to initiate the software update installation.

The software update checks the registry and blocks automatic installation on any Web server that does not contain the value singleserver in the SERVERROLE key.

If you need to determine whether to manually download and install the software update, use a registry editor to verify the value in the following key:

HKLM\Software\Microsoft\Shared Tools\Web server extensions\12.0\WSS\SERVERROLE

In server farm deployments, you must update all the Web servers running Office Forms Server 2007 to the same software update version. If the software update versions are not the same on all of the Web servers running Office Forms Server 2007 in your server farm, when users request resources from a Web server that does not have the software update installed, they receive a Page cannot be found (404) error. If you attempt to install the software update and the installation fails, all user requests to the Web servers with a failed software update installation will return the error: Server error: http://go.microsoft.com/fwlink?LinkID=96177. Once the software update installation is successful, the Web server displays content as expected.

This section provides an overview of what you must do before you install a software update.

You must remove the Web servers running Office Forms Server 2007 from service for the duration of the software update installation. We recommend that you schedule the installation of the software update for a time that causes the least amount of disruption for your users. You should communicate the proposed schedule to the users and the key people involved with the Web sites hosted on the Web servers running Office Forms Server 2007 and, if necessary, adjust the schedule.

If you are installing on Web servers running Office Forms Server 2007 in a server farm, after the software update is installed on the first Web server in the server farm, the file versions on that Web server and the databases in that server farm are different from the file versions on the other Web servers. This mismatch prevents the server farm from working correctly, and even valid requests result in errors. When the software update has been installed on all of the Web servers in the server farm, results are returned to users as expected.

When you first installed Office Forms Server 2007 on the Web servers in your server farm, if you used an upgrade method—either in-place or gradual—and upgrade jobs are still in progress, the software update installation might fail. To ensure that none of the upgrade processes are running, you must view the Timer Job Status page on the SharePoint Central Administration Web site. If you see any upgrade jobs listed, you must allow the upgrade to finish before you install the software update.

The upgrade jobs that appear on the Timer Job Status page result from the following operations:

  • Sites that are in the process of being upgraded.

  • You selected the in-place upgrade option in the SharePoint Products and Technologies Configuration Wizard.

After you have verified that no upgrade items are listed on the Timer Job Status page, you can continue installing the software update.

Before you install a software update, we recommend the following:

  • If there are orphaned objects in the content databases—orphans are items that do not have any parent or child relationships—the software update installation will fail. To make sure that the installation can succeed, you must either fix the relationship or drop the orphans before you begin the software update installation. For more information about a resolution for when the content database contains one or more orphaned objects, see the Microsoft Knowledge Base article titled Error message when you try to upgrade Windows SharePoint Services 2.0 to Windows SharePoint Services 3.0: "Upgrade has encountered one or more lists that were not updated by Prescan.exe and must exit" (http://go.microsoft.com/fwlink/?LinkId=105755).

  • If you customized a predefined site template by directly modifying the site template files—something we do not recommend doing—the software update installation may overwrite some of the files that you modified, and your customizations in those files will be lost. You must reapply any site-template customizations after you install the software update.

  • Stop the World Wide Web publishing service (w3svc) on all front-end Web servers to disconnect all the users from the server farm. In server farms with multiple front-end Web servers, if you allow users to connect after the files and databases have been updated on one Web server, and the other Web servers have not been updated, users will not be able to browse the Web sites.

    NoteNote:
    If you manually stop the World Wide Web Publishing service, you must manually start it at the end of the installation.
  • Before you start the backup you should clean up your environment by performing the following steps.

  • Back up the server farm before you start the software update installation. You should create a backup of search and all databases. We recommend that you follow these guidelines:

    • Configuration database and Central Administration content database: Perform a full backup operation with either Stsadm or SQL Server. If you are using SQL Server, use the simple recovery model, so that your transaction log is truncated.

    • Content databases: Perform a full backup operation with either Stsadm or SQL Server to back up all content databases. If you are using SQL Server, use the simple recovery model, so that your transaction log is truncated.

    • Single sign-on (SSO) database: Perform a full backup operation with SQL Server to back up the SSO database. If you are using SQL Server, use the simple recovery model, so that your transaction log is truncated.

    • Front-end Web server: If you have customized the front-end Web server, or are unsure of the extent of the customizations to your Web applications, we recommend that you make a backup image of your front-end Web server. Make sure you have a backup of any solution packages that you have deployed on your front-end Web servers.

      NoteNote:
      Ideally, if you are customizing front-end Web computers, the customization should be managed using a robust build process or script that allows the customizations to be applied to a new computer.

      If you experience an unrecoverable failure during upgrade, you may have to restore your server from the backup image you created. You would need to manually apply any customizations to your front-end Web server.

      NoteNote:
      We recommend that you back up the server farm after you have verified that the software update installation succeeded.

      After you have backed up all of your databases, use the SQL Server DBCC shrinkfile command to free unused log space, making the logs as empty as possible. For more information, see Shrinking the Transaction Log (http://go.microsoft.com/fwlink/?LinkId=105233). It is a best practice to verify that you can restore the databases.

      For more information about how to perform backups, see Prepare to back up and restore a farm (Windows SharePoint Services 3.0).

  • In server farms that have a large number of sites, you will find that installing a software update with the content databases attached is not practical in terms of downtime. In order to minimize the downtime, we recommend that you perform the additional step of detaching the content databases.

  • To deploy software updates in a server farm you must be logged in to the Web server as a domain account that also has the following permissions:

    • Member of the Administrators group on the Web server computer.

    • Member of the Administrators group on the server running SQL Server or be granted the fixed database role db_owner to all SharePoint Products and Technologies databases.

  • If you have previously installed a hotfix, and the problem that it addresses is not fixed in this widely available software update, you must obtain the updated version of that hotfix to address specific issues in your environment by contacting Microsoft Customer Support Services (http://go.microsoft.com/fwlink/?LinkId=99201).

    For more information about the software updates in Office Forms Server 2007 with Service Pack 1, see Microsoft Knowledge Base article 942388 (http://go.microsoft.com/fwlink/?LinkId=105672&clcid=0x409).

    For more information about the software updates in Office Forms Server 2007 Post Service Pack 1 rollup, see Microsoft Knowledge Base article 941422 (http://go.microsoft.com/fwlink/?LinkId=102044&clcid=0x409).

    NoteNote:
    All Web servers running Office Forms Server 2007 in the server farm must be running Office Forms Server 2007.
  • You must download the correct software update file for your hardware and language. The pattern for the software update naming convention is productnamerrr-kby-xnn-fullfile-lang.exe, where:

    • productname is a short identifier for the name of the released product.

    • rrr is a description of the release. For example, Service Pack 1 would be sp1.

    • y is a number that corresponds to the Knowledge Base article about the software update.

    • nn is a number indicating the hardware architecture, either x86 or x64.

    • lang is the language of the software update. For example, U.S. English is en-us.

      For example, the file name for the Office Forms Server 2007 Service Pack 1 (SP1) file, in U.S. English and for x86-based hardware, is wssv3sp1-kb936988-x86-fullfile-en-us.exe.

For more information, and to download the appropriate file, see Download details: Windows SharePoint Services 3.0 Service Pack 1 (SP1) (http://go.microsoft.com/fwlink/?LinkID=91024&clcid=0x409).

The following approach updates the database from one server that hosts the Central Administration Web site, so that when you run the SharePoint Products and Technologies Configuration Wizard on the subsequent front-end Web servers, the front-end servers can simply connect to the updated database, rather than attempt to upgrade the database.

NoteNote:
This installation sequence ensures that you can avoid database locking issues.

You must update the Web servers in your server farm in the following order:

  1. The files from the software update must be installed on all the Web servers in the server farm by running the software update installation on each Web server up to the point where the dialog box with the following message is displayed:

    You must run Setup to install new binary files for every server in your server farm. If you have multiple servers in your server farm, run Setup and the configuration wizard on the other servers now, and then return to this server and click OK to continue.

    NoteNote:
    If you started the installation in silent mode, using the /q switch, the SharePoint Products and Technologies Configuration Wizard does not automatically start. To continue the upgrade, you need to force the upgrade by either manually starting the wizard or running the psconfig command with arguments to force an in-place, build-to-build upgrade. For specific information, in the Perform installation steps section, follow the "To force a software update" procedure.
  2. Complete the software update by clicking OK in the dialog box on one Web server that hosts the Central Administration Web site (front-end Web server) for the server farm.

  3. Complete the software update, one Web server at a time, for the rest of the server farm.

ImportantImportant:
Make sure you are aware of the prerequisites, as outlined earlier in this document, before you follow the procedures in this section.

You must install the software update on each Web server running Office Forms Server 2007 to the point that the files are copied to all Web servers in the server farm. You should return to one Web server to complete the installation. After the installation has been completed on the Web server that you selected, you can complete the installation on each of the other Web servers.

To ensure that you have the correct permissions to install the software update and run the SharePoint Products and Technologies Configuration Wizard, we recommend that you add the account for the SharePoint Central Administration v3 application pool identity to the Administrators group on each of the local Web servers and application servers and then log on by using that account. These changes are only required for installing the update and then running the SharePoint Products and Technologies Configuration Wizard to complete the upgrade.

If you use a different account to install the software update, it must be a domain account with the following memberships, roles, and authorization:

  • Member of the Administrators group on the Web server computer.

  • Granted the fixed database role db_owner to all SharePoint Products and Technologies databases.

In many IT environments, database administrators (DBAs) create and manage databases. Security policies and other policies in your organization might require that DBAs create the databases needed by Office Forms Server 2007.

NoteNote:
For information about how to deploy Office Forms Server 2007 in an environment in which DBAs create and manage databases, see Deploy using DBA-created databases (Windows SharePoint Services) (http://go.microsoft.com/fwlink/?LinkID=86818&clcid=0x409).

You can install the software update by logging on to the server directly or by connecting through a Terminal Services console session.

NoteNote:
For information about how to use console sessions, see Microsoft Knowledge Base article 278845: How to Connect to and Shadow the Console Session with Windows Server 2003 Terminal Services (http://go.microsoft.com/fwlink/?LinkId=98317).

This section includes all of the procedures required to install a software update successfully in any size server farm. If you are in a large server farm, you should read the "Large-farm optimization" section later in this document.

The following procedure provides the steps to:

  • Make all software update files available on all servers in your server farm.

  • Complete the update on one front-end Web server.

  • Finish updating the remaining servers in the server farm.

    NoteNote:
    You must perform steps 1 though 7 from the following procedure on every Web server in the server farm before you complete the installation on any one Web server.
To install a software update
  1. Disconnect users from the server farm by stopping the World Wide Web Publishing service (w3svc) on all Web servers.

  2. Download and install the appropriate Office Forms Server 2007 software update for all servers in your server farm.

  3. At the end of the software update installation, the SharePoint Products and Technologies Configuration Wizard starts.

    NoteNote:
    If the wizard does not start automatically, click Start, point to All Programs, point to Administrative Tools, and then click SharePoint Products and Technologies Configuration Wizard.
  4. On the SharePoint Products and Technologies Configuration Wizard Welcome page, click Next.

  5. In the dialog box that notifies you that some services might need to be restarted during configuration, click Yes.

  6. On the Completing the SharePoint Products and Technologies Configuration Wizard page, click Next.

  7. When the dialog box about installation in a server farm appears, do not click OK. Instead, leave each server with the following dialog box displayed:

    You must run Setup to install new binary files for every server in your server farm. If you have multiple servers in your server farm, run Setup and the configuration wizard on the other servers now, and then return to this server and click OK to continue.

  8. When the dialog box from the previous step is displayed on all Web servers in the server farm, use one Web server that hosts the Central Administration Web site to finalize the installation.

  9. On the server you selected in the previous step, click OK.

  10. On the Configuration Successful page, click Finish.

  11. After you have finished updating one Web server that hosts the Central Administration Web site, you should follow the procedures in the "Verify installation" section on this one Web server to ensure that the software update installation was successful.

  12. Continue updating the remaining computers in the server farm, one at a time, by clicking OK in the dialog box.

    NoteNote:
    It is important that the SharePoint Products and Technologies Configuration Wizard perform the configuration procedures on only one computer at a time.
  13. When the software update installation and configuration is complete on all the Web servers in the server farm, make the Web servers available to users by manually starting the World Wide Web Publishing service on each server on which you manually stopped the service.

If you completed the "To detach content databases" procedure, depending on if you configured additional computers to upgrade the content databases, you must use one of the following procedures to attach the content database after the software update installation is complete.

NoteNote:
If you did not follow the "To detach content databases" procedure, you can skip the "To attach the content database" procedures.

If you did not configure additional computers specifically to upgrade the content databases, you will need to follow the "To attach the content database from the command line" procedure. This procedure attaches and initiates an upgrade of the content database.

To attach the content database from the command line
  • To attach the database, enter the following command:

    stsadm -o addcontentdb -url <http://backupservername:port> -databasename <ContentDBName> -databaseserver <NewPrincipalServer>

If you did configure additional computers specifically to upgrade the content databases, you can use the following procedure to attach the content database to the updated computers.

To attach the content database
  1. Click Start, point to All Programs, point to Administrative Tools, and then click SharePoint 3.0 Central Administration.

  2. On the Central Administration site, click Application Management.

  3. On the Application Management page, in the SharePoint Web Application Management section, click Content databases.

  4. On the Manage Content Databases page, click Add a content database.

  5. Enter the information for the content database you detached earlier.

  6. Repeat steps 4 and 5 for every content database you want to attach.

You must perform the following procedure on all indexers and query servers in your server farm if either of the following conditions is true:

  • You are running in a least-privileges scenario.

  • The account that you are using for the search service is either:

    • Not an Administrator on the local computer.

    • Not a member of the server farm administrator account.

To start the search service
  1. Open a Command Prompt window.

  2. To identify the computers that are running an instance of the online Office Forms Server 2007 search service, run the following command:

    stsadm -o spsearch -action list

  3. Log on to each computer, either locally or through a remote connection, that is returned in the list from the previous step and run the following command:

    stsadm -o spsearch -action start

In very large server farms, installing a software update with the content databases attached is not practical in terms of downtime. In the scenario where you have a large number of sites or many Web servers, to minimize the downtime required to upgrade, we recommend that you perform the additional step of detaching the content databases. For the best performance with the upgrade operations, you should use four or five front-end Web servers per database server.

NoteNote:
Unless you are dealing with a very large server farm, you do not need to follow this procedure.
To detach content databases
  1. To detach a content database using Stsadm, open a command prompt and change directories to %COMMONPROGRAMFILES%\Microsoft Shared\Web server extensions\12\Bin.

  2. Run the following operation from the command line:

    stsadm -o deletecontentdb -url http://computername -databasename

    In this operation, -url specifies the Web application from which the content databases will be detached and -databasename specifies the name of content database to be detached.

    NoteNote:
    If your database server is on a separate server, you need to use the -databaseserver parameter to specify the database server name.

After you upgrade your server farm, you must attach the content databases back to the server farm. You can only attach one content database to the server farm at a time, because when you attach the databases to the upgraded server farm, the content database is upgraded automatically.

If you want to streamline the upgrade process even further, you can configure additional computers as Web servers running Office Forms Server 2007 with SP1 in a single-computer server farm; we recommend four to five Web servers. You must configure alternate access mappings on these temporary front-end Web servers to match the original servers. If the alternate access mappings are not identical, the content databases may be upgraded with the wrong URLs within their site content. This will result in certain pages not displaying correctly, and you must contact Microsoft Product Services to correct this problem. Then, to perform a parallel upgrade of the content databases, use these Web servers to upgrade the content databases while they are detached from the original server farm.

After you detach the upgraded content databases from the temporary Web server, and attach them back to the original server farm, the content databases are ready for service. At this point, you should remove any content databases from the previous version and then back up the server farm.

NoteNote:
If you detach and reattach a content database, be aware that the next time the content within that content database is crawled a full crawl will occur, even if an incremental crawl has been requested. Because a full crawl recrawls all content, regardless of whether that content has been previously crawled, full crawls can take significantly more time to complete than incremental crawls.
If you are running the Infrastructure Update for Microsoft Office Servers, the identifier (ID) of each content database is retained when you restore or reattach the database by using built-in tools. Default change log retention behavior when using built-in tools is as follows:
  • The change logs for all databases are retained when you restore a farm.

  • The change log for a content database is retained when you reattach the database.

  • The change log for a content database is NOT retained when you restore just the content database.

When a database ID and change log are retained, Search continues crawling based on the regular schedule defined by crawl rules. When a change log is not retained, Search performs a full crawl during the next scheduled crawl.
For more information, see Move all databases (Office SharePoint Server 2007) and Back up and restore an entire farm (Office SharePoint Server 2007).

The limiting factor for this method is that you cannot simultaneously update more than one content database for each Web application—even if you use multiple computers.

After you install a software update, you should verify that the installation was successful by reviewing the upgrade log file (Upgrade.log), as described in the following procedure.

To view the upgrade log file
  1. In Windows Explorer, change to the following directory:

    %COMMONPROGRAMFILES%\Microsoft Shared\Web server extensions\12\LOGS

  2. Use a text editor to open the Upgrade.log file.

  3. Scroll to the date on which you installed the software update.

  4. Search, or visually scan, for the following entries:

    Finished upgrading SPFarm Name=<Name of Configuration Database>

    In-place upgrade session finishes. Root object = SPFarm=<Name of Configuration Database>, recursive = True. 0 errors and 0 warnings encountered.

    If you find these entries, the installation was successful.

  5. If you do not find the entries from the previous step, you can identify specific issues that may have contributed to the failure by searching, or visually scanning, through the Upgrade.log file for the following terms:

    • fail

    • error

    After you identify and resolve the blocking issues, use the "To force a software update" procedure later in this section.

In some configurations, the SharePoint Timer Service (OWStimer) account—which, by default, is the same account used by the SharePoint Central Administration v3 application pool account—is configured with credentials that do not have permission to access the LOGS folder in %COMMONPROGRAMFILES%\Microsoft Shared\Web server extensions\12\. If this is the case, part of the Upgrade.log is stored in the temporary storage folder of the account that is running the SharePoint Timer service.

To write all available logging information, including verbose output and detailed debugging information, to the log files for the software update installation, run the following command:

msiexec /p <PatchPackage> /l*vx %temp%\patch.log

Where PatchPackage is the path to the software update file.

You can find the log file in the temporary file location with the file name msi*.log.

NoteNote:
You can enable Windows Installer logging before you start the software update installation again. To enable logging for Windows Installer, see Microsoft Knowledge Base article 99206: How to enable Windows Installer logging (http://go.microsoft.com/fwlink/?LinkID=99206).

In addition to the previous procedure, verify that the update was successful by using the SharePoint Central Administration Web site to view the version number on the Servers in Farm page.

To view the Servers in Farm page
  1. Use one of the following methods to open the Servers in Farm page:

    • On the Central Administration home page, click Operations. Then, on the Operations page, in the Topology and Services section, click Servers in farm.

    • From Internet Explorer, view the following Web page:

      http://ServerName:Port/_admin/FarmServers.aspx

      Where ServerName is the name of the server, and Port is the port that is configured for the Central Administration Web site.

  2. On the Servers in Farm page, next to Version, verify the version number of each server in the farm to verify that each one has been updated to the new binary version.

    The following Office Forms Server 2007 version numbers are correct:

    If the version number matches the version number for the software update, you have succeeded in updating the server. If the version number is not correct, the software update installation did not complete successfully. To identify and resolve the blocking issues, follow the "To view the upgrade log file" procedure earlier in this article.

If you need to investigate the success of the software update installation in more depth, use the following procedure to verify version numbers on certain files and verify certain keys in the registry.

To perform advanced installation verification
  1. You can examine the version number of certain files in %COMMONPROGRAMFILES%\Microsoft Shared\Web server extensions\12\ISAPI

    The following Office Forms Server 2007 owssvr.dll version numbers are correct:

    • Release 12.0.4518.1016

    • October public update 12.0.0.6039

    • Service Pack 1 12.0.0.6219

    • Post Service Pack 1 rollup 12.0.0.6300

  2. Verify that the value is correct in the Version key in the following location:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web Server Extensions\12.0

You can also verify that the software update installation was successful by using SQL Query Analyzer to examine the SQL Server schema. Although the version of the DLL files and the registry are updated during the first part of an upgrade—when the files are being copied—the SQL Server schema is only upgraded after the SharePoint Products and Technologies Configuration Wizard is run.

NoteNote:
The SSP databases could have different version numbers and the SSO databases do not have a versions table.

You should use the following procedure to determine if the SharePoint Products and Technologies Configuration Wizard was run after the software update.

To verify through direct examination of the SQL schema
  • This SQL Server query can be run on any SharePoint Products and Technologies database to track all the upgrades run on the database in the GUID 00000000-0000-0000-0000-000000000000:

    SELECT * FROM Versions

    The highest value that maps to the GUID above should equal the current version of the product. For Service Pack 1 the version should include 6211.

If the installation did not succeed, you can run the SharePoint Products and Technologies Configuration Wizard again, or you can use the following procedure to complete the configuration from the command line.

NoteNote:
You can enable Windows Installer logging before you start the software update installation again. For information, see Microsoft Knowledge Base article 99206: How to enable Windows Installer logging (http://go.microsoft.com/fwlink/?LinkID=99206).
To force a software update
  1. Open a Command Prompt window and change to the following directory:

    %COMMONPROGRAMFILES%\Microsoft shared\Web server extensions\12\Bin

  2. Type the following command:

    psconfig –cmd upgrade –inplace b2b –wait –force

If you need to build a new server to join an existing server farm, we recommend that you use an installation source that has the software update files included. When you use this installation source to add new servers to your server farm, the software update is already applied to the new server and the version of the new server matches the rest of the servers in your server farm.

You can create an installation source location that already contains the software updates that match those installed on your server farm by using the updates folder. For more information, see the topic Create an installation source that includes software updates (Office Forms Server 2007).

If you need to build a new server to join an existing server farm, but you have not created an updated installation source, you must use the following procedure.

To build a server to join an existing farm
  1. Install the product without any software updates and do not run the SharePoint Products and Technologies Configuration Wizard.

    NoteNote:
    By not running the SharePoint Products and Technologies Configuration Wizard you do not define the location for the configuration database by creating the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web server extensions\12.0\Secure\ConfigDB.
  2. Install the software update.

  3. Run the SharePoint Products and Technologies Configuration Wizard at the prompt.

If you do not follow this process and you do run the SharePoint Products and Technologies Configuration Wizard after you install the released product, the SharePoint Products and Technologies Configuration Wizard reads the ConfigDB registry key and the SharePoint Products and Technologies Configuration Wizard displays: Exception: System.InvalidOperationException: Operation is not valid due to the current state of the object. To address this problem, you must either modify the registry or use the command line to force the configuration to complete successfully.

Use registry editor to modify the contents of the ConfigDB registry key and then run the SharePoint Products and Technologies Configuration Wizard.

To force an install after a failed configuration by modifying the registry
  1. Install the software update and do not allow the SharePoint Products and Technologies Configuration Wizard to run.

  2. Use a registry editor to modify the setup type to a clean install. Change the registry key to the following:

    HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Shared Tools\Web server extensions\12.0\WSS\SETUPTYPE=CLEAN_INSTALL

  3. Run SharePoint Products and Technologies Configuration Wizard to perform a disconnect operation.

  4. Run SharePoint Products and Technologies Configuration Wizard to connect to your server farm.

Use the Psconfig command-line tool.

To force an install after a failed configuration (command line)
  1. Install the product without any software updates and do not run the SharePoint Products and Technologies Configuration Wizard.

  2. Install the software update and do not run the SharePoint Products and Technologies Configuration Wizard.

  3. Open a Command Prompt window and run the following command:

    psconfig -cmd configdb -connect -server <SQLServerName> -database SharePoint_Config_<dbname> -user <domainusername> -password <password> -cmd helpcollections -installall -cmd secureresources -cmd services -install -cmd installfeatures -cmd applicationcontent –install

For each language template pack installed on a server that renders content, you must install updated language template packs. To install the language template packs, you can download updated language template packs through the Microsoft Download Center. However, we recommend that you browse to the Microsoft Update or Windows Update Web sites to detect the language template packs installed on your front-end Web server. An updated language template pack is installed for each language template pack that is currently installed.

You must run the SharePoint Products and Technologies Configuration Wizard after updated language template packs have been installed for each currently installed language template pack.

To create an installation location that you can use to install the language template packs with software updates already applied, see the topic Create an installation source that includes software updates (Office Forms Server 2007).

This section describes common errors you might encounter and what you need to do to fix them.

If you add a new Web server to an existing server farm that does not have any Web applications, and you update the Web server and then run the SharePoint Products and Technologies Configuration Wizard, you might receive the following error message:

An exception of type Microsoft.SharePoint.PostSetupConfiguration.PostSetupConfigurationTaskException was thrown. Additional exception information: Failed to upgrade SharePoint Products and Technologies.

The Upgrade.log file found in %COMMONPROGRAMFILES%\Microsoft Shared\Web server extensions\12\Logs contains the following error:

The access control list on %COMMONPROGRAMFILES%\Microsoft Shared\Web server extensions\12\template\layouts\Web.config could not be modified because the path could not be located in the file system.

This error occurs when the SharePoint Products and Technologies Configuration Wizard cannot locate or modify the Web.config file.

To resolve the issue, you must manually copy the Web.config file from %COMMONPROGRAMFILES%\Microsoft Shared\Web server extensions\12\Config to %COMMONPROGRAMFILES%\Microsoft Shared\Web server extensions\12\Template\Layouts. After the Web.config file is in the Layouts folder, you can run the SharePoint Products and Technologies Configuration Wizard again.

The following error in the Event Viewer application log might appear after you install a software update:

Source: Windows SharePoint Services

Category: Database

Event ID: 5586

Type: Error

Description: Unknown SQL Exception 15363 occurred. Additional error information from SQL server is included below.

This error occurs when the role WSS_Content_Application_Pools already exists in the current database. This is a known issue and you can safely ignore this error message.

If you installed the Foxit PDF IFilter on your search server, the IFilter does not work after you install a software update. You must reinstall the IFilter.

When you are using the updates folder and specify an alternate location for the updates folder by modifying the SUpdateLocation parameter in the Config.xml file Setup will stop responding and a error dialog box will appear.

This is a known limitation in the product. If you want to use the updates folder, you must use the default location for the SUpdateLocation parameter.

After you install Service Pack 1 (SP1), more disk space is required for your query server or index server. If adequate disk space is not available, your query servers will slow down or stop. Queries that normally take less than 5 seconds will be very slow, return an error, or timeout, and you will see the service error The search request is unable to connect to the search service.

This issue occurs because the method used to merge indexes has been modified to significantly improve performance and reduce server downtime. However, this change increases the disk space required to perform a master merge. Previously, a maximum of 2 times the physical size of the index was required. The new maximum disk space requirement on a query server or index server is increased to 2.85 times the physical size of the index.

This topic is included in the following downloadable book for easier reading and printing:

Was this page helpful?
(1500 characters remaining)
Thank you for your feedback
Show:
© 2014 Microsoft