1. Compile the Web service proxy into a signed DLL, commonly referred to as an assembly.

2. The Business Data Catalog package should define WebServiceProxyType as:

   <Property Name="WebServiceProxyType" Type="System.String">AssemblyName</Property>

   Where AssemblyName is an assembly qualified type name for proxy class.

3. To make the functionality in the assembly available to any application that might need to use it, you must use the .NET Framework Global Assembly Cache tool (Gacutil) to register the signed assembly as a shared assembly in the global assembly cache (GAC) on each front-end Web server. You must perform this step on front-end Web servers that will use the application in both the parent server farm and child server farm. To install the assembly and overwrite the existing assembly, you should use the combined switch /if, as in:

   gacutil /if AssemblyName

   Note

   To enable Office SharePoint Server 2007 Enterprise Search scenarios, you must also register this assembly. You can register the assembly in the parent server farm by opening SharePoint 3.0 Central Administration, and on the Application Management page, in the Office SharePoint Services Shared Services section, click Create or Configure this Farm’s Shared Services. To open the administration site for the Shared Services Provider (SSP), click the name of the SSP for the search service.

4. Run the iisreset /noforce command on each Web server on which you used Gacutil to register the assembly.

5. In the parent server farm, on the administration site for the SSP, import the Business Data Catalog application XML package.

   The child server farm is now able to use the metadata from the Business Data Catalog from the parent server farm.

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.

  Note
  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.

  • Defragment all of the SQL Server database indexes. For more information, see How to defragment Windows SharePoint Services 3.0 databases and SharePoint Server 2007 databases (http://go.microsoft.com/fwlink/?LinkID=102795&clcid=0x409).

  • Make sure that there is adequate hard drive space in your database files volumes, tempdb volumes, and Windows temporary folder on the servers running SQL Server, front-end Web servers, and application servers. The upgrade operation writes the progress of various steps into an upgrade log that can take up disk space, but if you plan for extra storage you should not encounter issues due to space limitations.

• If any of your databases contain more than the number of site collections recommended in the Information Architecture Recommendations of the Planning and Deploying Service Pack 1 for Microsoft Office SharePoint Server 2007 in a Multi-server Environment (http://go.microsoft.com/fwlink/?LinkID=105623&clcid=0x409), you should load-balance your site collections across multiple databases.

• Follow the best practices for content database sizing before you perform any upgrade operations.

• Make sure that you follow the recommendations concerning SQL Server page-fill factor and other storage planning best practices before you begin the upgrade. For more information about storage best practices, see Performance recommendations for storage planning and monitoring (http://go.microsoft.com/fwlink/?LinkID=105890&clcid=0x409)

• 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:

  • Search: Use the full backup operation from SharePoint Central Administration or Stsadm to back up search. The backup operation includes both the Shared Services Provider (SSP) database and search index file. Note: Before you back up, verify that the drive that you are backing up to has enough free space to back up the entire farm. Even though you are only backing up the search SSP, if you do not have free space for the entire farm, the backup operation will fail. For more information, see Back up Office SharePoint Server 2007 by using built-in tools (http://go.microsoft.com/fwlink/?LinkId=105758).

  • 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.

    Note
    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.

    Note
    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 Office SharePoint Server 2007.

    For detailed information about protecting and recovering data, you should download the whitepaper: Data protection and recovery for Office SharePoint Server in small to medium deployments (http://go.microsoft.com/fwlink/?LinkId=104927).

• 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 steps of running the Stsadm preparetomove operation and then detach the content databases.

  For more information, see Preparetomove: Stsadm operation (Office SharePoint Server).

• 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 SharePoint Server 2007 with Service Pack 1, see Microsoft Knowledge Base article 942390 (http://go.microsoft.com/fwlink/?LinkId=105673&clcid=0x409).

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

• 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 SharePoint Server 2007 Service Pack 1 file, in U.S. English and for x86-based hardware, is officeserver2007sp1-kb936984-x86-fullfile-en-us.exe.

For more information, and to download the appropriate file, see Download details: The 2007 Microsoft Office Servers Service Pack 1 (SP1) (http://go.microsoft.com/fwlink/?LinkID=105636&clcid=0x409).

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 from one of the servers hosting the Central Administration site.

• Finish updating the remaining servers in the server farm.

Note
You must perform steps 1 though 8 from the following procedure on every server running Office SharePoint Server 2007 in the server farm before you complete the installation on any one server running Office SharePoint Server 2007.

To install a software update

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.

Note
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

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

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

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 steps of running the Stsadm preparetomove operation and then detach the content databases.

For best performance with the upgrade operations, you should use four or five front-end Web servers per database server. 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. For more information, see Plan alternate access mappings (Office SharePoint Server) (http://go.microsoft.com/fwlink/?LinkId=105997&clcid=0x409).

To prepare to move the content databases

For more information about the Stsadm preparetomove operation, see Preparetomove: Stsadm operation (Office SharePoint Server).

Note
Unless you are dealing with a very large server farm, you do not need to follow this procedure.

To detach content databases

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 SharePoint 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.

Note

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 re-crawls all content that the crawler encounters, regardless of whether that content has been previously crawled, full crawls can take significantly more time to complete than incremental crawls.

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.

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.

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 SharePoint Server 2007 version numbers are correct:

   • Release 12.0.0.4518

   • October public update 12.0.0.6035

     For more information about the software updates in the October public update, see Microsoft Knowledge Base article 937832: Description of the security update for SharePoint Server 2007: October 9, 2007 (http://go.microsoft.com/fwlink/?LinkId=102083&clcid=0x409).

   • Service Pack 1 12.0.0.6219

   • Post Service Pack 1 rollup 12.0.6300.5000

   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.

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

   The following Office SharePoint Server 2007 Microsoft.SharePoint.portal.dll version numbers are correct:

   • Release 12.0.4518.1016

   • October public update 12.0.0.6036

   • Service Pack 1 12.0.0.6219

   • Post Service Pack 1 rollup 12.0.6300.5000

2. In registry editor, verify that the value is correct in the DisplayVersion key in the following locations.

   For x86: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\ Windows\CurrentVersion\Uninstall\OSERVER

   For x64: HKEY_LOCAL_MACHINE\SOFTWARE\Wow6432Node\Microsoft\ Windows\CurrentVersion\Uninstall\OSERVER

   Note   DisplayVersion contains the value 12.0.6219.1000 when either the Service Pack 1 or Post Service Pack 1 rollup is present on the computer.

• 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.

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

1. Install the product without any software updates and do not run the SharePoint Products and Technologies Configuration Wizard.

   Note
   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.

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.

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

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.

If the Office SharePoint Server Search service does not automatically start during the update, the following message in the SharePoint Products and Technologies Configuration Wizard appears:

Failed to start service SearchServiceInstance on this server after completing upgrade. Please start it manually.

The SharePoint Products and Technologies Configuration Wizard finishes successfully, but the Office SharePoint Server Search service remains stopped.

To start the Office SharePoint Server Search service

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 an 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.

You cannot determine if the Office SharePoint Server 2007 Service Pack 1 Language Template Pack is installed by examining the Language Template Pack entry in Add or Remove Programs. This is because the Office SharePoint Server 2007 Service Pack 1 Language Template Pack installation does not update the existing entry.

Note
This issue does not apply to Windows SharePoint Services 3.0 Service Pack 1 Language Template Packs.

To determine which version of the Office SharePoint Server 2007 Language Template Pack is installed, verify that the value for the DisplayVersion key contains the build and version for the Office SharePoint Server 2007 Service Pack 1 Language Template Pack. Open the following key in a registry editor:

\HKLM\Software\Microsoft\Windows\CurrentVersion\ Uninstall\<product>\DisplayVersion\

If you are using the Content Editor Web Part on the Web server running Office SharePoint Server 2007, which offers languages other than the installed language, users will receive a script error when they use the Web Part.

You can prevent this issue from occurring on the Web servers running Office SharePoint Server 2007 by installing the Windows SharePoint Services 3.0 Service Pack 1 Language Template Pack before you install the Office SharePoint Server 2007 Service Pack 1 Language Template Pack.

If you already installed the Office SharePoint Server 2007 Service Pack 1 Language Template Pack without the Windows SharePoint Services 3.0 Service Pack 1 Language Template Pack and your users are experiencing the script error, you can resolve this problem by installing the Windows SharePoint Services 3.0 Service Pack 1 Language Template Pack on the affected Web servers running Office SharePoint Server 2007.

If you install Microsoft Office SharePoint Server 2007 with Service Pack 1 (SP 1), and you are using Least Privilege mode, Search does not work. If Search appears to be working, a crawl may launch but either no items are crawled or no items are indexed and Search returns to an idle state.

You can confirm that this is the issue you are experiencing by reviewing the Application Event log for the following events:

To resolve this issue, you must follow the “To start the search service” procedure earlier in this topic.