Verify SharePoint 2010 Upgrade localupgradestatus


When upgrading to SharePoint 2010 from SharePoint 2007, there are lots of things you can before upgrading to resolve issues itself prior to upgrading.  And there are things you can do after upgrade to verify upgrade went okay as well.  Obviously, there needs to be involvement from the end users to check the sites and verify that things upgraded well.

As an administrator, you have things available to you after the upgrade such as the upgrade logs and the upgrade status page in Central Administration.

There is one additional method that  a lot of people don’t know about and it’s the stsadm command localupgradestatus.

Things to know:

  1. It’s going to dump out a lot of info, so it’s smart to make sure you output it into a txt file
  2. It doesn’t take any parameters
  3. It needs to be run on each server on the farm

To Run The Command:

stsadm –o localupgradestatus >upgradestatus_output.txt

 

Results

 <object>
    <name>demo2010a</name>
    <type>Microsoft.SharePoint.Administration.SPServer</type>
    <level>1</level>
    <status>OK</status>
  </object>

So what we have listed are all of the objects for upgrade (example above), as well as the summary.

  • Name: the name of the object
  • Type: the type of object
  • Level: the upgrade priority of the object
  • Status: the upgrade status.  OK means it’s upgraded.  Needs Upgrade, obviously means that it’s not.

 

The summary will detail the content dbs and their status, site collections and their status, and a object count over all.

[19] content database(s) encountered.

[0] content database(s) still need upgrade or cannot be upgraded.

[90] site collection(s) are contained in the content databases.

[0] site collection(s) still need upgrade.

[173] other objects encountered, [2] of them still need upgrade or cannot be upgraded.

Comments (5)

  1. BlueSky2010 says:

    Precise and useful info – thanks!

  2. Anonymous says:

    Nice..thanks for sharing..

  3. BlueSky2010 says:

    Have you figured what the numbers with ‘Level’ mean? I’ve seen 1 through 7 and just curious.

  4. Ravuri Theja says:

    Hi,

    I have got this when I ran psconfig command .

    [3] content database(s) encountered. [0] content database(s) still need upgrade or cannot be upgraded. [52] site collection(s) are contained in the content databases. [51] site collection(s) still need upgrade. [61] other objects encountered, [0] of them still need upgrade or cannot be upgraded.

    Is there any work around to get the list of site collections that are not upgraded?

    It seems some site collections are not upgraded successfully.When I tried to run spupgrade command,it throws this "content DB doesnot need upgrade",By then in CA the error shows like data base is up to date but some sites are not upgraded.

    Could you please help me to get rid of this error.

    Any help to determine the site collections that are not upgraded is very much helpful for me

  5. Hairsh says:

    Hi, The report is fine after that how should we fix them .

Skip to main content