Dealing with service pack 3 update failures - trying to figure out what is wrong.
We are trying to update a MOSS SharePoint 2007 SP1 system - single server - to MOSS SharePoint 2007 SP3 (and if we ever get that done, to apply the latest cumulative upgrades). After the WSS update ran for a while, I got the "Configuration Failed" error message. It points me to a PSCDiagnostics file - the first appearance of the word "Error" appears at line 15304, which says 05/21/2012 08:21:07 6 INF Resource retrieved id PostSetupConfigurationFailedEventLog is Configuration of SharePoint Products and Technologies failed. Configuration must be performed in order for this product to operate properly. To diagnose the problem, review the extended error information located at {0}, fix the problem, and run this configuration wizard again. It looks to me like all the references to error relate to the process having identified a problem and shutting down the configuration. The dialog box also mentions looking at the event viewer. I do so and see quite a number of error events. The first one appears to be. Event Type: Error Event Source: Office SharePoint Server Event Category: Launcher Service Event ID: 6103 Date: 5/21/2012 Time: 7:55:27 AM User: N/A Computer: NTSRV45D Description: LoadBalancer.UnRegisterLauncher failed: Unable to connect to the remote server For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. We don't use a Load Balancer - I don't know if this error is relevant to the grand problem or not. The next event is: Event Type: Error Event Source: Office SharePoint Server Event Category: Launcher Service Event ID: 6069 Date: 5/21/2012 Time: 7:55:27 AM User: N/A Computer: NTSRV45D Description: Unable to connect to the remote server For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. I don't know if this is related to the previous one, but I am assuming so. Next up is Event Type: Error Event Source: Windows SharePoint Services 3 Search Event Category: Gatherer Event ID: 10029 Date: 5/21/2012 Time: 7:55:48 AM User: N/A Computer: NTSRV45D Description: Error backing up registry hive to the configuration database. Context: Application 'Serve search queries over help content' Details: The system cannot find the file specified. (0x80070002) For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. I don't know what is up at this point. But it looks, to me, that the events that follow that one are proceeding with the configuration. Then we get Event Type: Error Event Source: Windows SharePoint Services 3 Search Event Category: Gatherer Event ID: 10036 Date: 5/21/2012 Time: 7:57:52 AM User: N/A Computer: NTSRV45D Description: A database error occurred. Source: Microsoft OLE DB Provider for SQL Server Code: 2812 occurred 1 time(s) Description: Could not find stored procedure 'dbo.proc_MSS_BackupProperty'. Context: Application '134189c0-7ec5-46f6-abcd-9063969e07c6' For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. A number of other informational events appear, then Event Type: Error Event Source: Windows SharePoint Services 3 Search Event Category: Gatherer Event ID: 10029 Date: 5/21/2012 Time: 7:58:23 AM User: N/A Computer: NTSRV45D Description: Error backing up registry hive to the configuration database. Context: Application 'Serve search queries over help content' Details: The system cannot find the file specified. (0x80070002) For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp. which seems similar to the last one. The process then generates another of the error events about the load balancer I don't know what this all means. I am using the sa_sps login, and certainly stsadm seems to work better when I am operating like this. I can't tell if these problems are related to not enough permissions, or some other issue. As always I appreciate your help.
May 21st, 2012 8:44am

So I located the Update.log file. This is quite peculiar. As the updater took a look at each of the site collections, I would see things like: [SPManager] [DEBUG] [5/21/2012 8:20:32 AM]: Using cached [SPContentDatabase Name=SharePoint_SSP_Content Parent=SPDatabaseServiceInstance Name=D001] NeedsUpgrade value: False. [SiteSequence] [DEBUG] [5/21/2012 8:20:32 AM]: Missing Version, Id = c1b02a31-2dfd-4c76-9748-d8dbb47662cb. [SiteSequence] [DEBUG] [5/21/2012 8:20:32 AM]: Missing SchemaVersion. [SiteSequence] [DEBUG] [5/21/2012 8:20:32 AM]: Defaulting to SchemaVersion = 2.0.0.0. Then I hit 2 site collections which look like this: [SPManager] [DEBUG] [5/21/2012 8:20:32 AM]: CanUpgrade [SPSite Url=http://dev/sites/IT] returned: True. [SPHierarchyManager] [DEBUG] [5/21/2012 8:20:32 AM]: SPTree Value=SPSite Url=http://dev/sites/IT IsRoot=True. [SPHierarchyManager] [DEBUG] [5/21/2012 8:20:32 AM]: 46/58 root trees in cache. [SPManager] [DEBUG] [5/21/2012 8:20:32 AM]: SPTree Value=SPSite Url=http://dev/sites/IT IsGrown=False IsRoot=True IsLeaf=True. [SPManager] [DEBUG] [5/21/2012 8:20:32 AM]: Using cached [SPContentDatabase Name=SharePoint_SSP_Content Parent=SPDatabaseServiceInstance Name=D001] NeedsUpgrade value: False. [SPManager] [DEBUG] [5/21/2012 8:20:32 AM]: Using cached [SPContentDatabase Name=SharePoint_SSP_Content Parent=SPDatabaseServiceInstance Name=D001] NeedsUpgrade value: False. [SPManager] [DEBUG] [5/21/2012 8:20:32 AM]: Using cached [SPContentDatabase Name=SharePoint_SSP_Content Parent=SPDatabaseServiceInstance Name=D001] NeedsUpgrade value: False. [SPManager] [DEBUG] [5/21/2012 8:20:32 AM]: Using cached [SPContentDatabase Name=SharePoint_SSP_Content Parent=SPDatabaseServiceInstance Name=D001] NeedsUpgrade value: False. [SPManager] [DEBUG] [5/21/2012 8:20:32 AM]: Using cached [SPContentDatabase Name=SharePoint_SSP_Content Parent=SPDatabaseServiceInstance Name=D001] NeedsUpgrade value: False. [SPManager] [DEBUG] [5/21/2012 8:20:32 AM]: CanUpgrade [SPSite Url=http://dev/sites/IT] returned: True. [SPManager] [DEBUG] [5/21/2012 8:20:32 AM]: NeedsUpgrade [SPSite Url=http://dev/sites/IT] returned: True. [SPManager] [DEBUG] [5/21/2012 8:20:32 AM]: Disposing SPSite Url=http://dev/sites/IT. [SPManager] [DEBUG] [5/21/2012 8:20:32 AM]: Upgrading [SPSite Url=http://dev/sites/IT]. [SPSiteWssSequence] [DEBUG] [5/21/2012 8:20:32 AM]: Saving site properties [SPManager] [ERROR] [5/21/2012 8:20:32 AM]: Pre-Upgrade [SPSite Url=http://dev/sites/IT] failed. Microsoft.SharePoint.Upgrade.SPSiteWssSequence has the ContinueOnFailiure bit set. Moving on to the next object in sequence. [SPManager] [ERROR] [5/21/2012 8:20:32 AM]: The system cannot find the path specified. (Exception from HRESULT: 0x80070003) [SPManager] [ERROR] [5/21/2012 8:20:32 AM]: at Microsoft.SharePoint.Library.SPRequestInternalClass.GetSiteQuota(String bstrUrl, UInt16& pdwQuotaTemplateID, Int64& plDiskQuota, Int64& plDiskWarning, Int32& plUserQuota) at Microsoft.SharePoint.Library.SPRequest.GetSiteQuota(String bstrUrl, UInt16& pdwQuotaTemplateID, Int64& plDiskQuota, Int64& plDiskWarning, Int32& plUserQuota) at Microsoft.SharePoint.Administration.SPQuota..ctor(SPSite site) at Microsoft.SharePoint.SPSite.get_Quota() at Microsoft.SharePoint.Upgrade.SPSiteSequence.PreUpgrade() at Microsoft.SharePoint.Upgrade.SPManager.Upgrade(Object o, Boolean bRecurse) [SPManager] [DEBUG] [5/21/2012 8:20:32 AM]: Elapsed time upgrading [SPSite Url=http://dev/sites/IT]: 00:00:00. [SPManager] [DEBUG] [5/21/2012 8:20:32 AM]: Disposing SPSite Url=http://dev/sites/IT. [SPManager] [DEBUG] [5/21/2012 8:20:32 AM]: Upgrading collection of Microsoft.SharePoint.SPSite, no.23 out of 33. After this, the process then takes a look at subsequent site collectiosn and ends up with a msg saying Skip upgrading even though there were no errors generated for them.
Free Windows Admin Tool Kit Click here and download it now
May 21st, 2012 9:47am

The peculiar thing in the log is that it says that this problem occurred at GetSiteQuota. We don't have quotas set on that site collection. I just ran this command: D:\temp>stsadm -o getproperty -propertyname defaultquotatemplate -url http://dev/sites/IT <Property Exist="Yes" Value="No Quota" /> In fact, only the mysite site collections have quotas on them on this machine. So, I am still stuck here looking at an error message that seems cryptic, particularly taking into account the other things we have been able to determine.
May 21st, 2012 10:00am

I discovered this morning that this machine as 2 "site collections" which are listed in the list of site collections, but which have no details when I display them in Central Admin > Application Management > SharePoint Site Management > Site collection list. So I tried to create the site, and got an error saying the site already exists. So I have two of these - sites that half exist and half do not exist. I go into Delete site collection, choose the site collection name, click OK, and the application does NOT change to the site collection. So, how do I delete a half existing site collection, or turn it into a full collection?
Free Windows Admin Tool Kit Click here and download it now
May 22nd, 2012 9:00am

Hi lwvirden, If you cant delete the site collection by the interface, I suggest you to use STSADM command. Start->run->,input cmd .Input cd C:\Program Files\Common Files\Microsoft Shared\web server extensions\12\BINInput stsadm -o deletesite -url http://servername/sites/sitename You can refer to the following link. http://technet.microsoft.com/en-us/library/cc288016(v=office.12).aspx Thanks, Jack
May 23rd, 2012 5:29am

Thank you very much for responding. What I ended up doing late yesterday was going to my site's central adm, quiesing the farm, going to the content database section, "removing" (detaching) the content database, attempting to add the database, getting an error msg from Central Admin that I needed to use stsadm addcontentdatabase , logging onto the machine, and doing the stsadm -o addcontentdatabase ... . Then, this morning, I remembered that I needed to "un-quiese" the site. This appears to have taken care of my issue!
Free Windows Admin Tool Kit Click here and download it now
May 23rd, 2012 7:36am

Thank you very much for responding. What I ended up doing late yesterday was going to my site's central adm, quiesing the farm, going to the content database section, "removing" (detaching) the content database, attempting to add the database, getting an error msg from Central Admin that I needed to use stsadm addcontentdatabase , logging onto the machine, and doing the stsadm -o addcontentdatabase ... . Then, this morning, I remembered that I needed to "un-quiese" the site. This appears to have taken care of my issue!
May 23rd, 2012 7:40am

Hi lwvirden, Im not sure of un-quiese. I find all dictionarys, there is no a word called quiese. You said "this appears to have taken care of my issue"!, so, is your problem ok? If yes, you can mark as the answer of the reply. Then it will help other people to resolve their problem. Thanks, Jack
Free Windows Admin Tool Kit Click here and download it now
May 23rd, 2012 11:26pm

I apologize - I meant un-quiesce. The farm has run for 24 hrs now and is working well. I appreciate the recommendation to mark the reply. It was my understanding that it was considered rude for someone to mark their own posting as an answer - learning the proper social networking etiquette for a specific forum takes me a little time.
May 24th, 2012 7:45am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics