UPDATE: 10/16/2007 5:42PM : Bill Baer has an interesting article on his blog about a new possible solution to this problem (see Option #4). I haven't had a chance to try it out yet, but as soon as I do I'll post my results.
---
Well, after about 12 hours I'm finally back up and running. I fought this stupid update ALL DAY LONG today. After about 6 hours of digging through the Event Viewer, Sharepoint Logs, MSDN, and every other conceivable resource - I finally threw in the towel. I simply couldn't afford to be down any longer.
Note: I was able to access the Admin site - but that was it. None of the other web app's/site collections would do anything except give errors.
I had no choice but to completely wipe WSS3.0, reinstall it clean, and restore the sites from backups.
I wish I had some magic fix for other sufferers (and I know from my research that there are many others out there) - but unfortunately I was unable to come up with anything but a reinstall.
For reference purposes, this is basically what happened.
Installed KB 934525 from Windows Update. The update finished successfully no problem. I read to reboot and then run the Sharepoint Config Wizard to finish the update. OK, so I reboot. Fire up the Config Wizard... runs to Step 9 and fails trying to start the SPAdmin service. I try it again and again.. even manually trying to start it.. the thing wont start.
I see posts about rerunning the KB update. So I download it, extract it, and force it to run again. It runs to completion without errors each time. It's the stupid Config Wizard that keeps crapping out on me - always at Step9 failing to start the SPAdmin service.
I dig through the Event Viewer and notice recurring patterns of these:
Unknown SQL Exception 15023 occured. Additional error information from SQL Server is included below.
User, group, or role 'WSS_Content_Application_Pools' already exists in the current database.
and these:
An exception of type System.InvalidOperationException was thrown. Additional exception information: Cannot start service SPAdmin on computer '.'.
followed by messages indicating they've been noted in the Sharepoint logs for reference.
so I dug through the Sharepoint logs but could never find anything more helpful than the SPAdmin service wouldnt start.
Also lots of these... database permission sync issues maybe???
The database WSS_Content on
I even broke down, removed Sharepoint COMPLETELY.. DELETED the DATABASES COMPLETELY... reinstalled Sharepoint.. went back to Windows Update and installed the update on a BRAND NEW CLEAN WSS3.0 Install - and it did EXACTLY the same stupid thing.
I finally got so disgusted and pissed off that I just trashed it all, reinstalled clean, and restored everything.
Which I guess proved I could recover from a catastrophic failure -but man it's a tedious job.
I had individual site collection backups for each site - so here's in a nutshell how I recovered:
Uninstall WSS3.0.
Delete the databases (the uninstall actually leaves them).
Install WSS3.0.
Set access mappings.
Set outgoing email server info.
Made web.config changes.
Restored my backups of a couple non-managed folders under wwwroot\wss\80\.
Installed and deployed wsp features.
Restored each individual site collection.
Made registry changes for PDF indexing, restarted spsearch service.
Made change to xml config file for PDF icon ICPDF.GIF.
Made sure custom files under \program files\common files\microsoft shared\web resources\12\ were still there (the WSS3.0 uninstall left them so they were good).
Restarted IIS to pickup PDF icon change.
Delete and Reupload any PDFs to be re-indexed.
I wish I'd had a full database backup to save me some time.. but with all the customizations and crap - it's still tedious.
I know one thing, I will never again install a WSS3.0 update so soon after release.
damn i know how you feel. just installed the same update, almost by accident from windows update. The site takes 3hours to do a backup and over 6-7hours for a full re-import. Its gonna be a long night
ReplyDeleteTry manually starting SPAdmin process during long run of step that shows error "Cannot start service SPAdmin..." .
ReplyDeleteIn my case, I started SPAdmin process at step 2. I also restarted SPAdmin process during step 9 (cpu usage was almost 0).
With these two interventions, setup finished successfully and my SharePoint is running. :)
matulo-
ReplyDeleteI manually tried starting the SPAdmin service many many many times at different points throughout the problem - but I dont believe I ever tried it *while* the Config Wizard was running. I'd love to know if that works for other people. I might try it on another machine.
2 kenneth:
ReplyDeleteThere was nothing to loose. I could have reinstalled whole sharepoint, or I could try everything to make the old one work. Starting process during it's configuration is normally weird, but as a last step before reinstall it's good... :)
My (and also yours) Config wizard told me what was the problem -- SPAdmin was not started. Before showing error, the Config wizard was waiting quite a long (and I think it was waiting for start of a process, which it actually didn't tell to start). So why not to try it? :)
I'd also like to know if this helped to some other crashed SP. Hope yes...
just wanted to make sure everyone saw the edit/UPDATE i made earlier referencing Bill Baer's blog and a possible alternative solution.
ReplyDelete