Error applying SharePoint SP1 to MOSS; SearchDatabaseSequence

Just applied SharePoint SP1 to our production MOSS 2007 server. Itfailed on the last steps of the configuration wizzard. I have a callinto Microsoft. We failedon "Microsoft.Office.Server.Search.Upgrade.SearchDatabaseSequence"

Database Maintenance:1. Run MOSS BPA and resolve any problems defined2. Stop the WWW service and disconnect any users3. Run DBCC CHECKDB on each database and repair any problems.4. Remove Orphaned Items from databases using stsadm Ã¢â¬"o databaserepair5. Defragment and update statistics of each database(http://support.microsoft.com/?id=918744)6. Make sure that there is adequate hard drive space in your databasefiles volumes, tempdb volumes, and Windows temporary folder on theservers running SQL Server, front-end Web servers, and applicationservers. (http://support.microsoft.com/kb/943345)7. After you have backed up all of your databases, use the SQL ServerDBCC shrinkfile command to free unused log space, making the logs asempty as possible. Shrinking the Transaction Log(msdn.microsoft.com/en-us/library/ms178037.aspx)

Upgrade Pre-Steps:1. Load Balance Site Collections and ensure your not exceeding sitecollections limits per content database and make sure contentdatabases do not exceed 100 GB as recommended.(office.microsoft.com/.../afile.aspx)2. Make sure that you follow the recommendations concerning SQL Serverpage-fill factor and other storage planning best practices before youbegin the upgrade.(technet.microsoft.com/en-us/library/cc287996.aspx)3. Backupa. Use the full backup operation from SharePoint CentralAdministration or Stsadm to back up search.(technet.microsoft.com/en-us/library/cc263298.aspx) The backupshould include both the SSP and the index file.b. Brick level backup the configuration and central admin contentdatabasesc. Backup the SSO and every content databased. Backup any Front End Customizations such as Templates, features,resources, webparts, etc..4. OPTIONAL - In server farms that have a large number of sites, youwill find that installing a software update with the content databasesattached is not practical in terms of downtime. You may want to pursuethis route for any content db > 20 GB as well. In order to minimizethe downtime, we recommend that you perform the additional steps ofrunning the Stsadm preparetomove operation and then detach the contentdatabases. Do not run against the CONFIG database or ADMINISTRATIONCONTENT DATABASE!a. Run this command for each content databasestsadm -o preparetomove -contentdb <db_name>If you do not run this operation before you detach the contentdatabase, then the membership and profile information in the contentdatabase is static and will not be synchronized after upgrade.b. If you have multiple Web applications you must run.stsadm -o deletecontentdb -url http://servername -databasenamec. In this operation, -url specifies the Web application from whichthe content databases will be detached and -databasename specifies thename of content database to be detached.After you upgrade your server farm, you must attach the contentdatabases back to the server farm. You can only attach one contentdatabase to the server farm at a time, because when you attach thedatabases to the upgraded server farm the content database is upgradedautomatically.5. To deploy the upgrade you must have these membershipsa. Member of the Administrators group on the Web server computer.b. Member of the Administrators group on the server running SQLServer or be granted the fixed database role db_owner to allSharePoint Products and Technologies databases.

Install Sequence1. The files from the software update must be installed on all theapplication and Web servers in the server farm by running the softwareupdate installation on each application or Web server up to the pointwhere the dialog box with the following message is displayed:You must run Setup to install new binary files for every server inyour server farm. If you have multiple servers in your server farm,run Setup on the other servers now, and then return to the CentralAdmin Server server and click OK to continue with PSCONFIG. Justclick cancel and do not run psconfig on any server other than centraladmin.2. Run PSconfig only on the Central Admin server after installing MOSSSP1. Ignore and close it when it opens on WSS SP1 and run it ONLYafter MOSS SP1.a. Add the account for the SharePoint Central Administration v3application pool identity to the Administrators group on each of thelocal Web servers and application servers and then log on by usingthat account. These changes are only required for installing theupdate and then running the SharePoint Products and TechnologiesConfiguration Wizard to complete the upgrade.b. The following permissions are required to run psconfig1. Member of the Administrators group on the local computer thatruns Office SharePoint Server 2007.2. In SQL Server, the account must be:a. Authorized to access all SharePoint Products and Technologiesdatabases.b. Granted the Database Creators (dbcreator) fixed server role.c. Granted the Security Administrators (securityadmin) fixedserver role.3. OPTIONAL only If you detached content dbs use the following commandline to add them back to the farmstsadm -o addcontentdb -url <http://backupservername:port>-databasename <ContentDBName>If you detach and reattach a content database, be aware that thenext time the content within that content database is crawled a fullcrawl will occur even if an incremental crawl is requested. Because afull crawl re-crawls all content that the crawler encounters,regardless of whether that content has been previously crawled, fullcrawls can take significantly more time to complete than incrementalcrawls. CPU will be maxed!4. Verify the server install by running the following command againstthe config databaseSELECT * FROM VersionsRelease 12.0.4518.1016October public update 12.0.0.6036Service Pack 1 12.0.0.6219Post Service Pack 1 rollup 12.0.6300.50005. Force an upgrade by running one of the following commands if youencounter problemsa. psconfig Ã¢â¬"cmd upgrade Ã¢â¬"inplace b2b Ã¢â¬"wait Ã¢â¬"forceb. psconfig -cmd configdb -connect -server <SQLServerName> -databaseSharePoint_Config_<dbname> -user <domainusername> -password <password>-cmd helpcollections -installall -cmd secureresources -cmd services-install -cmd installfeatures -cmd applicationcontent Ã¢â¬"install6. Next Install Rollups 1 & 2 for both WSS and MOSS and reboot the server

Go4Sharepoint, is a Microsoft Featured Community.
Microsoft, Windows, Sharepoint, Sharepoint logo, Windows logo, etc are trademarks of the Microsoft Corporation.
All product names, logos, copyrights, and trademarks mentioned are acknowledged as the registered intellectual property of their respective owners. This site is not in any way affiliated with, nor has it been authorized, sponsored, or otherwise approved by, Microsoft Corporation.