A client this morning applied the WSS SP1 and the MOSS SP1 to a medium sized farm (2 WFEs, 1 App, Clustered SQL)and failed, so I gotta call. First Ensure the binaries and registry settings were correct on all servers. Ensure which Dbs were upgraded (SELECT * FROM Versions).

 

After receiving the upgrade.log it appeared that SQL was timing out, looking at SQL we found the login had failed. (search the upgrade.log for Warn, Error, Fail) 

 

In Studio Manager go to security/logins/ click on the user and view usermapping in this instance the account appeared to have the dbo role for the user mapping when reviewing the permissions on the specific DBs. When reviewing the properties of the specific Dbs the account wasnt listed and neither was anyone else and we were not able to add them, the error "user not found" until we Detached / Attached the dbs, added the user rights mapping via SQL Studio Manager security/logins/ click on user and view user mapping, checked off the the dbs and roles, checked the individual dbs, and performed full backup of the dbs. Note there are other SQL configuration issues with the cluster that are now partially resolved and still need work.

 

The gist of the story is to say thank you Joel for the following..... An easy method of performing the upgrade of the DBs without having to use a more complex method of ststadm -o deletecontentdb, addcontentdb and editssp. Specifically due to the number of SharedServices Dbs involved and proves once again SQL is the soul of SharePoint.

___

 

This problem can occur for a number of reasons:

 

·         The web front end administrator does not have permissions to the SQL server and psconfig cannot update the databases

·         SQL database engine is temporarily unavailable for any reason and psconfig cannot complete the upgrade

·         Permissions on the file system or registry are incorrect and upgrade cannot get past permissions problem to do the upgrade

·         Customer restored a WSS content database in place rather than going through Manage Content Databases to add the database

·         Customer has a server farm and forgot to run psconfig on one or more of the servers

 

Correct any problems detected and then force the upgrade to run:

 

To force a software update

1.    Force a software update operation by opening a command prompt, and changing to the directory: %programfiles%\common files\Microsoft shared\web server extensions\12\bin\ 1.    Type the command: psconfig –cmd upgrade –inplace b2b –wait –force

"

If that doesn't work try it via STSADM, this will upgrade the binaries first, then look at the databases and update them per the software on the server.  Be sure to do the psconfig first.

stsadm -o upgrade -inplace -forceupgrade

(b2b as in build to build)

More can be found @ http://blogs.msdn.com/joelo/archive/2007/09/26/hotfixes-service-packs-and-password-resets.aspx

 

 

-Ivan

 

A few more references...