locked
WSS 3.0 issue when doing TFS 2010 disaster recovery RRS feed

  • Question

  • Hello,

    I am trying to do a DR exercise using the TFS 2010 docs. I have got as far as this Redirect SharePoint Products to Use a New Content Database 

    and on step 10, I and I am getting the error shown in the image.

    The restored-from-production WSS_Content database Versions table has a version number 3.1.11.0 but the SharePoint_AdminContent_[GUID] database Versions table has a version number 3.1.8.0

    What do I need to run on the DR server to upgrade its WSS 3.0 to version 3.1.11.0 - I have already run WSS SP2.

    Here are the SQL Server and Windows versions of the two servers:

    DR server

    Microsoft SQL Server 2008 R2 (RTM) - 10.50.1600.1 (X64)

           Apr  2 2010 15:48:46

           Copyright (c) Microsoft Corporation

           Standard Edition (64-bit) on Windows NT 6.1 <X64> (Build 7601: Service Pack 1) (Hypervisor)

     

    Prodcutin server

    Microsoft SQL Server 2008 R2 (RTM) - 10.50.1600.1 (X64)

           Apr  2 2010 15:48:46

           Copyright (c) Microsoft Corporation

           Standard Edition (64-bit) on Windows NT 6.1 <X64> (Build 7600: ) (Hypervisor)

    Wednesday, December 16, 2015 10:25 AM

Answers

  • Found the problem and here is the fix:

    OWSSVR.dll was at a wrong version. The target WSS 3.0 was at 12.0.6421.1000, whereas the source WSS 3.0 server was at 12.0.6665.5000

    1) Applied Windows SharePoint Services 2007 (KB2526305), 64-Bit Edition Service Pack 3. This increased the version to 12.0.06608.1000


    2) Applied Windows SharePoint Services 3.0 cumulative update server hotfix package (WSS server-package) August 28, 2012. This increased the version to 12.0.6665.5000


    This article helped me identify the things to check and that's where I discovered the need to check OWSSVR.dll

    • Marked as answer by amir tohidi Wednesday, February 24, 2016 11:21 AM
    Wednesday, February 24, 2016 11:21 AM

All replies

  • since the restored content database is NEWER than the environment that you're trying to restore it into, you need to UPGRADE the TARGET SharePoint environment to match the SOURCE.

    Scott Brickey
    MCTS, MCPD, MCITP
    www.sbrickey.com
    Strategic Data Systems - for all your SharePoint needs

    Wednesday, December 16, 2015 6:03 PM
  • Thanks Scott.

    Back in 2010, we installed Windows SharePoint Services 3.0 x64 with Service Pack 2. None of us recall installing anything on the source server that would have upgraded its WSS.

    Do you know where can I find the MSI (?) to upgrade the target server's WSS from 3.1.8.0 to 3.1.11.0? 

    Thursday, December 17, 2015 3:23 PM
  • check central admin -> Servers in Farm -> Version

    there's also nothing stopping the TARGET environment from being at a HIGHER version than the source... you can just upgrade the target to the latest SP/CU/etc and import.


    Scott Brickey
    MCTS, MCPD, MCITP
    www.sbrickey.com
    Strategic Data Systems - for all your SharePoint needs

    Thursday, December 17, 2015 5:56 PM
  • Found the problem and here is the fix:

    OWSSVR.dll was at a wrong version. The target WSS 3.0 was at 12.0.6421.1000, whereas the source WSS 3.0 server was at 12.0.6665.5000

    1) Applied Windows SharePoint Services 2007 (KB2526305), 64-Bit Edition Service Pack 3. This increased the version to 12.0.06608.1000


    2) Applied Windows SharePoint Services 3.0 cumulative update server hotfix package (WSS server-package) August 28, 2012. This increased the version to 12.0.6665.5000


    This article helped me identify the things to check and that's where I discovered the need to check OWSSVR.dll

    • Marked as answer by amir tohidi Wednesday, February 24, 2016 11:21 AM
    Wednesday, February 24, 2016 11:21 AM