locked
Site Version not changing after successful CU applied RRS feed

  • Question

  • So I am deploying a new MOSS install and trying to import my site but its complaining about the version not being up the old site.  I applied MOSS SP2 and my site is at 12.0.0.6421, I have applied the February 2011 CU and the Sharepoint Wizard reported it to be successful. Ran psconfig -cmd upgrade -inplace b2b -force -wait. Reported all 4 configuration changes succssful.

     

    But the site version is still stuck at 12.0.0.6421. Note This is build 12.0.6554.5000 of the cumulative update package for February 2011. I only have the WFE and a seperate SQL server. 


    • Moved by Mike Walsh FIN Wednesday, March 23, 2011 7:05 PM admin q (From:SharePoint - General Question and Answers and Discussion (pre-SharePoint 2010))
    • Edited by Mike Walsh FIN Thursday, March 24, 2011 2:02 PM swearing removed
    Wednesday, March 23, 2011 6:58 PM

Answers

  • I may have not been clear in my first post.  The configuration wizard ran successfully after updating to SP2. What wasnt very clear was that I had to apply both the WSS and MOSS updates inorder for the site version to update.  Of coarse I had to run the wizard after each update, that was a little time consuming.
    • Marked as answer by Jeremy Cejka Thursday, March 24, 2011 1:18 PM
    Thursday, March 24, 2011 1:17 PM

All replies

  • Hi Jeremy,

     

    This problem may occur if you have applied some service packs related to MOSS/WSS3.0 and you forgot to run SharePoint technology and configuration wizard. You must complete that wizard after applying service pack and that too successfully.

     

    Please refer to these two articles to get more detailed information about this problem:

    http://www.myriadtech.com.au/blog/James/Lists/Posts/Post.aspx?ID=24;

    http://www.sharepointkings.com/2010/03/version-difference-in-site-settings-and.html.

     

    Thanks & Regards,

    Peng Lei

    Thursday, March 24, 2011 3:15 AM
  • I may have not been clear in my first post.  The configuration wizard ran successfully after updating to SP2. What wasnt very clear was that I had to apply both the WSS and MOSS updates inorder for the site version to update.  Of coarse I had to run the wizard after each update, that was a little time consuming.
    • Marked as answer by Jeremy Cejka Thursday, March 24, 2011 1:18 PM
    Thursday, March 24, 2011 1:17 PM