Logo 
Search:

MOSS Forum

Ask Question   UnAnswered
Home » Forum » MOSS       RSS Feeds

Error applying SharePoint SP1 to MOSS; SearchDatabaseSequence

  Asked By: Arielle    Date: Jul 14    Category: MOSS    Views: 1331

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

Anyone else ever delt with this?

Share: 

 

4 Answers Found

 
Answer #1    Answered By: Renee Murray     Answered On: Jul 14

Did you apply the WSS SP1 update first?

Did you run the SP1 update using the original install account for the
server?

Is this the only server in the farm?

 
Answer #2    Answered By: Harshini Raju     Answered On: Jul 14

We are still working with Microsoft...

Yep - ran WSS SP1 first - did not run config wizzard
ran Office SP1 then the config wizzard. Failed in step 8.

Was logged in as farm account - the original account.

We have a single 64 bit web server and single SQL server. We didn't
have to install 'binaries' accross a web farm...

Once they get us going I'll report back.

 
Answer #3    Answered By: Christop Mcfadden     Answered On: Jul 14

Try this procedure.

MOSS SP1 Upgrade Process:

As defined and cleansed by
technet.microsoft.com/.../cc263467.aspx#section1

Database Maintenance:
1. Run MOSS BPA and resolve any problems defined
2. Stop the WWW service and disconnect any users
3. Run DBCC CHECKDB on each database and repair any problems.
4. Remove Orphaned Items from databases using stsadm â€"o databaserepair
5. 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 database
files volumes, tempdb volumes, and Windows temporary folder on the
servers running SQL Server, front-end Web servers, and application
servers. (http://support.microsoft.com/kb/943345)
7. 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. 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 site
collections limits per content database and make sure content
databases do not exceed 100 GB as recommended.
(office.microsoft.com/.../afile.aspx)
2. Make sure that you follow the recommendations concerning SQL Server
page-fill factor and other storage planning best practices before you
begin the upgrade.
(technet.microsoft.com/en-us/library/cc287996.aspx)
3. Backup
a. Use the full backup operation from SharePoint Central
Administration or Stsadm to back up search.
(technet.microsoft.com/en-us/library/cc263298.aspx) The backup
should include both the SSP and the index file.
b. Brick level backup the configuration and central admin content
databases
c. Backup the SSO and every content database
d. Backup any Front End Customizations such as Templates, features,
resources, webparts, etc..
4. OPTIONAL - 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. You may want to pursue
this route for any content db > 20 GB as well. 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. Do not run against the CONFIG database or ADMINISTRATION
CONTENT DATABASE!
a. Run this command for each content database
stsadm -o preparetomove -contentdb <db_name>
If you do not run this operation before you detach the content
database, then the membership and profile information in the content
database 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 -databasename
c. 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.
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.
5. To deploy the upgrade you must have these memberships
a. Member of the Administrators group on the Web server computer.
b. 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.

Install Sequence
1. The files from the software update must be installed on all the
application and Web servers in the server farm by running the software
update installation on each application or 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 on the other servers now, and then return to the Central
Admin Server server and click OK to continue with PSCONFIG. Just
click cancel and do not run psconfig on any server other than central
admin.
2. Run PSconfig only on the Central Admin server after installing MOSS
SP1. Ignore and close it when it opens on WSS SP1 and run it ONLY
after MOSS SP1.
a. 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.
b. The following permissions are required to run psconfig
1. Member of the Administrators group on the local computer that
runs Office SharePoint Server 2007.
2. In SQL Server, the account must be:
a. Authorized to access all SharePoint Products and Technologies
databases.
b. Granted the Database Creators (dbcreator) fixed server role.
c. Granted the Security Administrators (securityadmin) fixed
server role.
3. OPTIONAL only If you detached content dbs use the following command
line to add them back to the farm
stsadm -o addcontentdb -url <http://backupservername:port>
-databasename <ContentDBName>
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 is 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. CPU will be maxed!
4. Verify the server install by running the following command against
the config database
SELECT * FROM Versions
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
5. Force an upgrade by running one of the following commands if you
encounter problems
a. psconfig â€"cmd upgrade â€"inplace b2b â€"wait â€"force
b. 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
6. Next Install Rollups 1 & 2 for both WSS and MOSS and reboot the server

 
Answer #4    Answered By: Gopal Jamakhandi     Answered On: Jul 14

...and did you run the config wizard only after installing both the WSS
SP1 and MOSS SP1 to all machines in the farm?