locked
Solving issues in preupgradecheck reports RRS feed

  • Question

  • When i came to know that we cant go ahead without solving the the issues of preupgradecheck reports, i started working to solve the following issues:

    1. Sitedefinition information failed.

    2. Feature information Failed.

    3. OSPrerequisite Failed

    4. Invalid Dataschema Failed

    5. Pending Upgrade Failed.

    To solve this i deleted all the custom definitions, i deactivated and uninstalled all the features which i got from preupgradecheck reports. Even i deleted the web apllications (In order to delete the content databases for which it was showing invaliddatabaseschema Failed error). Then I run STSADM.EXE -o preupgradecheck again. but still i  am facing same error. Can anyone help me to solve this problem along with other two(3rd and 5th) errors mentioned above.

    Thanks in advance.

    Monday, January 9, 2012 6:37 AM

Answers

  • Although you may have deactivated, retracted, or otherwise deleted features and solutions, remnants may still exist in SharePoint databases. This is common, for example, in the Fab 40 Site Templates.

    You'll have to use the object model (i.e., PowerShell or Visual Studio) to remove those items, "clean up the databases," until preupgradecheck reports no errors (or warnings).

    I don't have pre-made scripts to send you unfortunately, this kind of remediation is usually specific to your environment. HTH.


    Wahid Saleemi Sr. Consultant, Avanade http://www.wahidsaleemi.com
    Monday, January 9, 2012 10:40 PM

All replies

  • Although you may have deactivated, retracted, or otherwise deleted features and solutions, remnants may still exist in SharePoint databases. This is common, for example, in the Fab 40 Site Templates.

    You'll have to use the object model (i.e., PowerShell or Visual Studio) to remove those items, "clean up the databases," until preupgradecheck reports no errors (or warnings).

    I don't have pre-made scripts to send you unfortunately, this kind of remediation is usually specific to your environment. HTH.


    Wahid Saleemi Sr. Consultant, Avanade http://www.wahidsaleemi.com
    Monday, January 9, 2012 10:40 PM
  • Although you may have deactivated, retracted, or otherwise deleted features and solutions, remnants may still exist in SharePoint databases. This is common, for example, in the Fab 40 Site Templates.

    You'll have to use the object model (i.e., PowerShell or Visual Studio) to remove those items, "clean up the databases," until preupgradecheck reports no errors (or warnings).

    I don't have pre-made scripts to send you unfortunately, this kind of remediation is usually specific to your environment. HTH.


    Wahid Saleemi Sr. Consultant, Avanade http://www.wahidsaleemi.com
    Monday, January 9, 2012 10:40 PM
  • Hi Wahid,

    Thanks for the reply. As you told I deleted databases from the sql server management studio. Then again I run the preupgradecheck. Now I am getting Aborted due to internal error for most of the part, and Failed for OSPrerequisite. And error as follows in  \LOGS\PreUpgradeCheck-20120110-155745-788.htm file.

    Failed : This server machine in the farm does not have Windows Server 2008 or higher 64 bit edition installed.

    Upgrading to Windows SharePoint Services 4.0 requires Windows Server 2008 or higher 64 bit edition.
    Please upgrade the server machines in your farm to Windows Server 2008 64 bit edition, or create a new farm and attach the content from this farm. For more information about this rule, see KB article 954770 in the rule article list at http://go.microsoft.com/fwlink/?LinkID=120257.

    Can you please tell me what can I do for that. Actually I installed Microsoft office server SP2 to upgrade the version from 12.0.0.4518 to 12.0.0.6421. Still i need to install any software?

    Thanks.

     

    Tuesday, January 10, 2012 1:08 PM
  • That error can't be fixed with software. You'll need to move your MOSS farm to a Windows 2008 64-bit server first.
    Wahid Saleemi Sr. Consultant, Avanade http://www.wahidsaleemi.com
    Friday, January 13, 2012 12:13 AM
  • Hi

     But how can I replace moss with windows 2008 64 bit. It will effect all other web applications which are there in that server. Sorry but to migrate only one web application we cant follow this step. Is there any other way so that no other web application should get effected.

    Monday, January 16, 2012 5:00 AM
  • Hi

     But how can I replace moss with windows 2008 64 bit. It will effect all other web applications which are there in that server. Sorry but to migrate only one web application we cant follow this step. Is there any other way so that no other web application should get effected.

    You need to have a new server to move to.
    http://sharepoint.nauplius.net
    Monday, January 16, 2012 5:04 AM
  • Hi Trevor,

         Thanks for the reply. But I dont have other than these two servers to move to. I heard there is another way to migrate, can you please tell me if you know about it.

    Thanks in advance.

    Wednesday, January 18, 2012 4:06 AM
  • Well, you're in a bit of a pickle.  You'll have to reinstall Windows to migrate from your current environment to Windows 2008 x64.  I think the best you can do is thoroughly test the database attach upgrade migration in a virtual test environment or similar, then back all of the databases up, reinstall Windows, restore the databases, and do the database attach upgrade.
    http://sharepoint.nauplius.net
    Wednesday, January 18, 2012 4:18 AM