locked
SharePoint failing with events 369, 33002 and 5586 RRS feed

  • Question

  • Hello there

    We have come across a SBS 2008 server that that can cannot run the SharePoint website (Companyweb) though it can run Central Administration. Event viewer throws the following errors in order:

    Event 369 Timer
    Event 33002 (2)
    Event  5586 Database

    On close inspection we have observed that the Hotfix for WSS KB2687331 has been run in attempt to fix the problem giving the version as 12.0.6500.5000. We are not sure whether this hotfix was the right move or not. Reading up on the hotfix, we attempted to complete the upgrade via the GUI and eventually the command line psconfig -cmd upgrade -inplace b2b -wait –force.

    The upgrade fails on step 2 with the following error listed in the command window:

    We are of the opinion if that we can run the upgrade process we can fix the problem, but despite several attempted suggestions we can’t get past this error. Any ideas?   

    Many Thanks


    MIS5000

    Monday, October 15, 2012 3:22 PM

All replies

  • Have a look in the Timer job overview and look for a Upgrade Job - whats the status of that one?
    Tuesday, October 16, 2012 7:17 AM
  • Hi there

    There are Status two faluires:

    • CEIP Data Collection and
    • Upgrade

    Both with progress at 100%

    All others are Status sucessfull with progress 100%


    MIS5000

    Tuesday, October 16, 2012 7:29 AM
  • Try and delete the Upgrade job and re-run your psconfig cmd line.

    • Edited by Jesper Arnecke Wednesday, October 17, 2012 5:57 AM changed stsadm to psconfig
    Tuesday, October 16, 2012 7:57 AM
  • Job deleted

    Should we run this command again?:

    psconfig -cmd upgrade -inplace b2b -wait –force


    MIS5000

    Tuesday, October 16, 2012 8:27 AM
  • Yes :)

    If its fails, find the log and find the line that describes the failure.

    Tuesday, October 16, 2012 11:21 AM
  • Hello again

    Ok, which log and I looking at, PSCDiagnostics? There is an awful lot of information there - can I send it to you by chance? This is starting to get frustrating.


    MIS5000

    Tuesday, October 16, 2012 11:25 PM
  • Yeah that is the right one - search in the document for error indicated in the prompt. There should be some additional information about why its failing.Secondly, try clearing the built cache and see if that would help you:

    http://support.microsoft.com/kb/939308

    After clearing the cache, rerun the psconfig command.

    Wednesday, October 17, 2012 5:57 AM
  • Hi again

    Ok we found something. In attempting to delete the cache following the article you gave

    (http://support.microsoft.com/kb/939308) we found that there is no GUID folder. The instructions refer to the recreation of this folder ect. Note that the data files for this has been moved to another location previously, though I cant see how this impacts this operation.

    What we have is a folder named the following: f0ec19d1-589f-4f8b-a165-c36a7cf7ae02

    In there is the Cache file and a heap of XML files. Remember this is an SBS 2008 machine if that’s relevant

    Thoughts?


    MIS5000


    • Edited by MIS5000 Wednesday, October 17, 2012 10:48 AM Spelling
    Wednesday, October 17, 2012 10:47 AM
  • Hiya ,

    The SBS shouldn't have any impact on what you describe here.

    The "f0ec19d1-589f-4f8b-a165-c36a7cf7ae02" is a GUID folder :) - so that's the one. If clearing the cache doesn't change it, I would clear timerjob and cache again and apply SP3 for the WSS.

    I've had these problem a few times before were people didn't update properly, so ending up in these limbo states.

    http://social.technet.microsoft.com/Forums/en-US/sharepointsearch/thread/e6e89839-87f2-4191-ab3c-f49273db7edd#6353202e-44ef-4160-8ad7-50d0f6f12bd3

    This one here should properly be last resort:

    stsadm -o upgrade -forceupgrade

    Wednesday, October 17, 2012 11:44 AM
  • Hello again
    Sorry about the GUID mix up - it was the end of a long night,  I was looking for a folder called GUID.
    The upgrade job hasn’t reappeared in the timer status. I have cleared the cache twice with no results
    This command stsadm -o upgrade –forceupgrade
    returns the following You must specify either the inplace parameter or the sidebyside parameter

    SP3 has already been applied to the system and declares when I re-ran it that the expected version was not found on this system, which is kind of what I  expected. What do you beleive should have occured?

    Should I be looking at rebuilding SharePoint?


    MIS5000

    Wednesday, October 17, 2012 11:53 PM
  • Hiya,

    Didnt expect the SP3 was installed from the version number given. SP3 lists build number: 12.0.6606.1000.

    Run the following command for your site:

    stsadm -o upgrade -inplace -url http://<sitename>

    That will, as it command implies, attempt to upgrade the content database associated with that site. If Central Administration is running, it might be a mismatch between site content and farm config, that throws off the exception.

    What is the latest Cum or SP you have applied?

    Thursday, October 18, 2012 5:59 AM
  • Hi again

    As in the original post, a Hotfix for WSS KB2687331 has been run in attempt to fix the problem (by another party) giving the version as 12.0.0.6665. We are not sure whether this hotfix was the right move or not. Service pack 3 is listed in Windows update some time back.

    Does this change your prognosis?


    MIS5000

    Thursday, October 18, 2012 10:46 AM
  • Ran the command above and received the following:

    Seer the post below as well

    Cheers


    MIS5000


    • Edited by MIS5000 Thursday, October 18, 2012 10:57 AM addition
    Thursday, October 18, 2012 10:56 AM
  • Hiya,

    Just be to be sure, have you tried rebooting between the different attempts? :)

    Thursday, October 18, 2012 1:12 PM
  • You my friend, are a steely eyed SharePoint man! Site is up and running

    Im not sure if I should run any other checks considering all the tinkering - what are your thoughts?

    Many thanks sir!


    MIS5000

    Thursday, October 18, 2012 2:06 PM
  • I would run the psconfig still, just to be sure there are no hanging upgrade attempts. - Only problem you might run into is your site being down again. On the other hand, if that will happend - it will happend sometime soon without your control anyway :)
    Thursday, October 18, 2012 4:43 PM