locked
How to patch 12.0.0.6653 to 12.0.0.6654? (Oct 2011 CU Re-release) RRS feed

  • Question

  • I have a SP2007 farm where the Oct 2011 CU was installed before it was re-released.  The re-release of that CU was never installed.  The current version is 12.0.0.6653.

    We are migrating to a 64-bit platform, but are unable to get the first release of the Oct 2011 CU in a 64-bit flavor.  So, we decided to update the farm to the re-release (6654) of the Oct 2011 CU.  However, when I got to install the WSS and Office versions of the Oct 2011 CU re-release, it says that it is already installed.

    How can I install this CU??

    Tuesday, November 27, 2012 8:22 PM

Answers

  • Just found this!

    Known issues with this hotfix

    If you have Service Pack 3 for SharePoint Server 2007 installed and try to install this cumulative update package, under certain circumstances, you may encounter an error that states that "the expected version of the product was not found on the system." If this issue occurs, run the package executable (.exe) file at a command prompt and set the PACKAGE.BYPASS.DETECTION.CHECK=1 switch as follows: 
    • For x86: "office-kb2596540-fullfile-x86-glb.exe PACKAGE.BYPASS.DETECTION.CHECK=1"
    • For x64: "office-kb2596540-fullfile-x64-glb.exe PACKAGE.BYPASS.DETECTION.CHECK=1"

    • Marked as answer by Fubak Tuesday, November 27, 2012 8:45 PM
    • Unmarked as answer by Fubak Tuesday, November 27, 2012 9:19 PM
    • Marked as answer by Emir Liu Thursday, November 29, 2012 2:02 AM
    Tuesday, November 27, 2012 8:45 PM
  • Finally got this working.  We had a server that was missed in the patching process.  We also removed the Excel Services since it wasn't being used anymore.
    • Marked as answer by Emir Liu Thursday, November 29, 2012 2:02 AM
    Wednesday, November 28, 2012 7:58 PM

All replies

  • Just found this!

    Known issues with this hotfix

    If you have Service Pack 3 for SharePoint Server 2007 installed and try to install this cumulative update package, under certain circumstances, you may encounter an error that states that "the expected version of the product was not found on the system." If this issue occurs, run the package executable (.exe) file at a command prompt and set the PACKAGE.BYPASS.DETECTION.CHECK=1 switch as follows: 
    • For x86: "office-kb2596540-fullfile-x86-glb.exe PACKAGE.BYPASS.DETECTION.CHECK=1"
    • For x64: "office-kb2596540-fullfile-x64-glb.exe PACKAGE.BYPASS.DETECTION.CHECK=1"

    • Marked as answer by Fubak Tuesday, November 27, 2012 8:45 PM
    • Unmarked as answer by Fubak Tuesday, November 27, 2012 9:19 PM
    • Marked as answer by Emir Liu Thursday, November 29, 2012 2:02 AM
    Tuesday, November 27, 2012 8:45 PM
  • That allowed me to install the patch, but Central Admin is still reporting that I'm running version 12.0.0.53.  Any ideas?
    Tuesday, November 27, 2012 9:20 PM
  • bump
    Wednesday, November 28, 2012 2:10 AM
  • Hi fubak,

    Have you run the SharePoint Products and Technologies Configuration Wizard after the CU installation completed? Before the configuration wizard run, it will still show the previous version number in Central Administration.

    Thanks & Regards,
    Emir Liu
    TechNet Subscriber Support in forum
    If you have any feedback on our support, please click here.


    Emir Liu
    TechNet Community Support


    • Edited by Emir Liu Wednesday, November 28, 2012 6:25 AM
    Wednesday, November 28, 2012 6:25 AM
  • Hi fubak,

    Have you run the SharePoint Products and Technologies Configuration Wizard after the CU installation completed? Before the configuration wizard run, it will still show the previous version number in Central Administration.

    Thanks & Regards,
    Emir Liu
    TechNet Subscriber Support in forum
    If you have any feedback on our support, please click here.


    Emir Liu
    TechNet Community Support


    Yes, it has been run on all servers in the farm.
    Wednesday, November 28, 2012 2:29 PM
  • Finally got this working.  We had a server that was missed in the patching process.  We also removed the Excel Services since it wasn't being used anymore.
    • Marked as answer by Emir Liu Thursday, November 29, 2012 2:02 AM
    Wednesday, November 28, 2012 7:58 PM