Comments on Dirty Words: SharePoint SP2 Upgrade Fails: The B2B upgrader tim...

I found [ERROR] [xxx]: Could not upgrade virtual ...

2012-01-26T18:37:53.847+08:00

I found

[ERROR] [xxx]: Could not upgrade virtual server XXXX (XXX). You cannot use Local System or Local Service as the application pool identity for Windows SharePoint Services.

in upgrade.log. I have to simply change identity of one of the applicaiton pool from local system to network service.

For me the "-wait" was the key: psconfig...

2011-06-03T05:30:14.692+08:00

For me the "-wait" was the key:
psconfig -cmd upgrade -inplace b2b -force -wait

If you stop your IIS before applying the service p...

2011-04-24T01:31:20.691+08:00

If you stop your IIS before applying the service pack, make sure you turn it back on before running the PSConfig

PLZ CHECK ITS URGENT I M GETTING THIS WHILE WSS SP...

2011-04-23T14:20:13.054+08:00

PLZ CHECK ITS URGENT I M GETTING THIS WHILE WSS SP2 POST UPGRADE

04/23/2011 10:25:31 9 ERR The B2B upgrader timer job failed.

[SPManager] [INFO] [4/23/2011 10:48:19 AM]: Resetting the status of PersistedUpgradableObject: SPWebService Parent=SPFarm Name=WSS_Config to Online.
[SPManager] [DEBUG] [4/23/2011 10:48:20 AM]: SyncUpgradeTimerJob: sleeping for 10 seconds
[SPManager] [ERROR] [4/23/2011 10:48:21 AM]: ReflexiveUpgrade [SPWebService Parent=SPFarm Name=WSS_Config] failed.
[SPManager] [ERROR] [4/23/2011 10:48:21 AM]: Could not continue scan with NOLOCK due to data movement.
[SPManager] [ERROR] [4/23/2011 10:48:21 AM]: at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection)

In my case I was trying to install search center 2...

2011-02-28T11:54:19.478+08:00

In my case I was trying to install search center 2008 onto WSS3.0 and getting the same sort of errors, I end up discovering this was due to a pre-existing search database. I probably could have deleted the existing database but instead I granted temporary permissions to the Annon account on the required DB then once the install completed successfully I removed them again.

Hi, My issue turned out to be an old IIS site and...

2010-10-21T04:57:12.466+08:00

Hi,

My issue turned out to be an old IIS site and its directory located here. C:\inetpub\wwwroot\
The upgrade.log file showed the error.

Application Web Config for this IIS site (1078976354) could not be found at....

It could not find a web.config in that directory. I suppose I could have added a web.config but since I did not need the site I deleted it.I was then able to successfully run

psconfig -cmd upgrade -inplace b2b -force -wait.

This article describes problems and issues including the solution I used above.
http://support.microsoft.com/kb/944267

Similar issue while ungrading to SP2. We finally ...

2010-09-28T21:08:41.882+08:00

Similar issue while ungrading to SP2.

We finally identified the problem by looking at the log. Our problem was that there was a Content database referenced by one of the web application, but somehow the database did not exist on (or probably was deleted from) the SQLServer, thus SP2 kept on failing updating.

Once this error was corrected, PS installed with no further problems.

I did the same as bungle and it worked, however, I...

2010-08-30T22:18:08.217+08:00

I did the same as bungle and it worked, however, I was required to re-copy the original template/layouts/web.config file back as the page editing toolbar was not functioning properly.

I had the same issue. At Step 8 of the upgrade it ...

2010-08-22T07:24:29.827+08:00

I had the same issue. At Step 8 of the upgrade it failed with an exception. My problem was the service account passwords. We had changed the password from services mmc. So doing an upgrade and config wizard was trying to match the passwords stored in the config db, and it was failing. Followed KB article http://support.microsoft.com/kb/934838
That fixed it.

Strange but it worked for us too. Thank you

2010-05-22T00:52:51.666+08:00

Strange but it worked for us too. Thank you

I did what Bungle posted and it resolved my proble...

2009-12-10T02:22:57.844+11:00

I did what Bungle posted and it resolved my problem as well.

I also had to delete web.config from layouts direc...

2009-05-12T16:28:00.000+08:00

I also had to delete web.config from layouts directory afterwards as I was causing other problems.

I had the exactly same problem on one of my web fr...

2009-05-12T16:15:00.000+08:00

I had the exactly same problem on one of my web frontends. I managed to fix this with a help of my colleague.

Here is what I did:

I copied web.config file from 12\CONFIG to 12\TEMPLATE\LAYOUTS.

The I did run:
psconfig -cmd upgrade -inplace b2b -force -wait

That's it.

Hi Michael, My experience was identical to yours. ...

2009-05-07T01:55:00.000+08:00

Hi Michael,
My experience was identical to yours. Finally figured out it was a problem with the SSP database when I found this line in the upgrade.log file -

[SSPDatabaseSequence] [ERROR] [5/6/2009 9:03:15 AM]: Action 12.1.500.0 of Microsoft.Office.Server.Search.Upgrade.SSPDatabaseSequence failed.

The only thing running on SSP was Search, so I created a new SSP and associated the site collections with it. Re-ran psconfig & this time it completed successfully(!).

So far, so good - SharePoint seems to be functioning normally. I think I've got the nerve to apply SP2 in production now (AMEN to those very important lessons).