locked
Upgrade to sharepoint foundation from 2007 32bit to 64bit RRS feed

  • Question

  • Dear All,

    Am trying to migrate sharepoint 2007 32bit to another server sharepoint foundation 2007 64bit so that i can upgrade to sharepoint 2010 & later to 2013.

    SharePoint 2007 32bit --> Migrate to new server --> SharePoint 2007 64bit

    First Am building an identical lab setup same as 32bit on a new server where i have installed SharePoint 2007 64bit 

    After attaching the content database, when run the preupgrade check 

    ran into some warnings " Missing Assembly "

    Have installed all the templates on the new server, but still getting the warring.

    where dose the Assembly are stored in SharePoint 2007. 



    sharath

    Monday, July 11, 2016 6:42 AM

Answers

All replies

  • Hi

    If you have some custom assemblies (for example, Web Parts and event receivers and so on) in SharePoint 2003 32 bit, you must recompile existing 32-bit applications and custom assemblies to run on the 64-bit architecture because the 64-bit edition of SharePoint cannot load a 32-bit assembly. Before you recompile existing applications or custom assemblies, verify that they are compiled to run on both architectures. If this is the case, do not compile them for a single architecture. (In Microsoft Visual Studio this build option is AnyCPU.)

    If the existing applications are third-party applications, check with the third-party vendor regarding 64-bit versions and compatibility. In the case of custom contracted solutions for which you do not have the source, verify the solutions in a test 64-bit environment to ensure compatibility.

    More details please refer to this article:

    Migrate an existing server farm to a 64-bit environment (Office SharePoint Server 2007)

    Monday, July 11, 2016 6:59 AM
  • For SharePoint 2007 Assembly, you can go to "C:\WINDOWS\assembly\GAC_MSIL" and find it.
    Monday, July 11, 2016 7:04 AM
  • Thanks for the fast replay.

    • Assembly = DocumentReviewEventHandler, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c, Count = 2, Status = Installed
    • Assembly = KnowledgeBaseEventHandler, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c, Count = 16, Status = Installed
    • Assembly = Microsoft.SharePoint, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c, Count = 57, Status = Installed
    • Assembly = ReservationEventHandler, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c, Count = 3, Status = Installed
    • Assembly = ResourceEventHandler, Version=12.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c, Count = 3, Status = Installed

    These are the warnings am getting. but as u can see all the assembly (features) are installed.

    Have checked both the assembly folders in 64 bit server, it contains all the assembly files. 

    Even after doing an in-place upgrade to 2010. when i test the content database am getting the same warnings.

    Are these features 64bit  compatible. 


    sharath

    Monday, July 11, 2016 7:25 AM
  • Looks like you installed the features and not removed features before you migrated from SharePoint 2007 32 bit to 64 bit or upgraded from 2007 to 2010, right?

    See the steps here to uninstall features:

    https://blogs.msdn.microsoft.com/kaevans/2011/02/02/sharepoint-dont-forget-to-uninstall-the-feature/

    And below is the method about how to diagnose Missing Assembly issues from the SharePoint Health Analyzer using PowerShell and try to solve it.

    Diagnose Missing Webparts and Missing AssemblyIssues

    Monday, July 11, 2016 7:49 AM
  • Means i have to deactivate & uninstall the features before doing an in-place upgrade. 

    if so After uninstalling the features. 

    Run the preupgrade check in SP2007 

    am getting the error upgrade block (missing features) 


    sharath

    Monday, July 11, 2016 12:59 PM
  • Hi Sharath,

    You also need to find out missing features of SharePoint sites or site collections and then remove them, for the method please refer to below thread:

    http://mroffice365.com/2011/08/how-to-find-out-sharepoint-server-missing-features-and-remove-those/

    Tuesday, July 12, 2016 5:45 AM
  • Helped a lot,

    After retracting & uninstalling the solution which were not being used. the errors were less.

    Now their is a legacy template which is being used as a template for site.

    Just want to know if i use  SharePoint Feature Administration and Clean Up Tool  to remove the template.

    will the site still work with default template...??


    sharath

    Wednesday, July 13, 2016 11:53 AM
  • Hi Sharath,

    Seems the Clean Up Tool you said is only can uninstall features. For the legacy template, is that means you want to delete this site template? If yes, you maybe can refer to this link's methods:

    https://social.msdn.microsoft.com/Forums/en-US/04e0bb50-2319-44fb-8f59-63a801086ed5/how-to-delete-a-site-template

    Thursday, July 14, 2016 12:53 AM