Click here to Skip to main content
15,881,715 members
Articles / Productivity Apps and Services / Sharepoint / SharePoint 2013

Migrating Sharepoint 2010 Custom Farm Solutions to Sharepoint 2013

Rate me:
Please Sign up or sign in to vote.
4.67/5 (3 votes)
4 Oct 2013CPOL3 min read 24.1K   5   2
How to migrate SharePoint 2010 custom farm solutions to SharePoint 2013

Several months ago, I posted an article regarding Live Migration of Sharepoint 2010 to Sharepoint 2013, that’s is a real good migration guide if you use the stock standard Sharepoint Server without any custom solutions deployed on your Farm, but if you have customized solutions then it would be a different issue. While your SharePoint might have custom solutions in place, using the guide will still work apart from pages on your Sharepoint where custom solutions are used, now that will all change as this article will talk about migrating those solutions as well. I know it’s a bit late compared to my original post, it is still better late than never.

I tried a lot of strategies in doing this but the easiest one will be this one, so let's start.

First you need to back up your Farm Solutions from your old Sharepoint instance by going to your Sharepoint 2010 Central Administration -> Backup and Restore then perform a backup.

01 Backup Solutions

Choose all the solutions, it will pick all solutions from the list. If you plan on migrating several but not all, still do this method as the import on 2013 will ask you first what solution would you want to import.

02 Choose a solution

Hit next, then double-check the following items, you need to also indicate the Backup location. Then when you are ready, click Start Backup.

03 Settings for Backup

Back up now commences.

04 Backing Up

Once finished, it will tell you the result and fingers crossed, it will be all OK, it will show you what folder it created on your Backup location.

05 Backup Finished

Verify that by going to the folder, at this point, your solutions are fully backed up.

05a Backup Finished

Now let's restore it, go to your Sharepoint 2013 Central Administration -> Backup and Restore, then click “restore from a backup”.

06 Restore Process

Choose the Backup Directory Location you placed your backup click refresh, then select the solutions.  Click Next.

07 Restore Properties

Choose what you want to restore, you can click the Solutions and it will include everything or you can choose one child not multiple. Then go next.

08 Choose what to restore

Check the following details presented to you. For data to restore, we need both content and configuration, then for type of restore, we use new configuration. Click Start Restore when you are ready.

09 Restore Options

So if you are like me and forgot to add the permissions for the account Sharepoint 2013 is using on the folder, you placed your backup, then you will be presented with this error:

 ”Access to the path XXX is denied for the account XXX.  Ensure that the Sharepoint Timer service and Microsoft SQL Server service accounts have Full Control permission on both the file share and underlying folder”

10 Make sure about user security

Fix that by giving “Full Permission” on the folder, then you have to go back to the restore step one. Once all ok, then it should start restoring.

11 Error Message

Once completed, you might encounter some issues like I did on mine. You have to check it and adjust accordingly, the error on mine were the following:

Cannot locate class information for: Microsoft.SharePoint.Diagnostics.DiagnosticLog, 
Microsoft.SharePoint.Diagnostics.ExtendedDiagnosticProviders, Version=1.0.0.0, 
Culture=neutral, PublicKeyToken=425dfe2b2d249462.
Cannot locate class information for: 
Microsoft.ReportingServices.SharePoint.Common.SPRSDiagnosticsService, 
Microsoft.ReportingServices.SharePoint.Common, Version=10.0.0.0, Culture=neutral, 
PublicKeyToken=89845dcd8080cc91.

I just disregarded that as I am not using DiagnosticLog for the moment as well as Reporting Services on this new Sharepoint instance. This is not related to my solution that I just restored.

After that, you just go to the Solution Management that is in Central administration and you will see your solutions imported but not deployed.

12 Solutions Added

You can deploy them by going to each one, then clicking on “Deploy Solution”.

13 Deploy

Once done for all, it will have a Deployed Status.

14 All Deployed

You can now start testing your pages with custom solutions and it should work as normal.

Some Caveats

  1. Your page with custom code will not work if you haven’t allowed server side scripts. To do that, check this post. It still works for Sharepoint 2013 http://macaalay.com/2010/10/21/how-to-enable-code-blocks-in-sharepoint-2010-works-also-in-2007/comment-page-1/
  2. If you have added web config items manually, you have to add them again in new Sharepoint.

Filed under: CodeProject, Servers
Tagged: Sharepoint, Sharepoint 2013, Sharepoint Foundation 2013
Image 16 Image 17

License

This article, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)


Written By
Technical Lead
New Zealand New Zealand
http://nz.linkedin.com/in/macaalay
http://macaalay.com/

Comments and Discussions

 
QuestionSharePoint 2010 Project Files Pin
IrishChieftain13-Nov-13 6:44
IrishChieftain13-Nov-13 6:44 
Cool article! Two questions:

1) Does this process automatically update the 2010 project file entries for TargetFrameworkVersion and TargetOfficeVersion with values 4.5 and 15.0, respectively?

2) Is using Central Admin for the backup/restore process easier/recommended over using SQL Server Tools and PowerShell?
AnswerRe: SharePoint 2010 Project Files Pin
Raymund Macaalay13-Nov-13 8:14
Raymund Macaalay13-Nov-13 8:14 

General General    News News    Suggestion Suggestion    Question Question    Bug Bug    Answer Answer    Joke Joke    Praise Praise    Rant Rant    Admin Admin   

Use Ctrl+Left/Right to switch messages, Ctrl+Up/Down to switch threads, Ctrl+Shift+Left/Right to switch pages.