Tag Archives: Upgrade

Updating SharePoint 2010 Web Parts For SharePoint 2013

Following an upgrade from SharePoint 2010 to 2013 I deployed some custom web parts.  When loading the page I received the error “/_CONTROLTEMPLATES/WEBPARTNAME/VisualWebPart1/VisualWebPart1UserControl.ascx” does not exist.

2013WebPartError1

The error is caused by the web part looking in the \14\TEMPLATE\CONTROLTEMPLATES folder rather than \15\TEMPLATE\CONTROLTEMPLATES.  Open the web part solution in Visual Studio and change the _ascxPath string.  Original value below:

2013WebPartError2

 

Change the string to include the 15 folder.

2013WebPartError3

 

Rebuild and re-deploy the web part.

 

Advertisements

Upgrading SharePoint 2010 To SharePoint 2013 Part 5

These are notes from my first upgrade of SharePoint 2010 to SharePoint 2013.  The purpose of the upgrade is to carry out an initial test upgrade to find any issues etc.  I’m not replicating the environment in terms of server roles etc. everything is installed on one server with local SQL.  I followed the steps outlined here: http://technet.microsoft.com/en-us/library/cc303436.aspx

This is part 5, part 1 can be found here, part 2 here, part 3 here and part 4 here.

Upgrade a site collection to SharePoint 2013

Reference: http://technet.microsoft.com/en-us/library/jj219650.aspx

Once the databases have been upgraded you can upgrade individual site collections.  You will see the notification bar at the top of the site with the option Start now or Remind me later.

Before beginning the site collection upgrade run health checks from Site Settings -> Site Collection Administration -> Site collection health checks.

On the run site collection health checks page, click Start checks.

After reviewing the health check results begin the site collection upgrade.  From the Site Settings page, click Site collection upgrade beneath Site Collection Administration.

On the following page, click Upgrade this Site Collection.

Once the upgrade has completed verify the upgrade from the Upgrade status page.  Go to Site Settings -> Site Collection Administration -> Site collection upgrade.  On this page click Review Site Collection Upgrade Status.

Finally, review everything is working and looks as you’d expect.

Additional configuration tweaks

Grant the default content access account the  “Retrieve People Data for Search Crawlers” permission for the User Profile Service application.

Configure the object cache user accounts http://technet.microsoft.com/en-us/library/ff758656.aspx

Enable the blob cache http://technet.microsoft.com/en-us/library/ee424404.aspx

Upgrading SharePoint 2010 To SharePoint 2013 Part 4

These are notes from my first upgrade of SharePoint 2010 to SharePoint 2013.  The purpose of the upgrade is to carry out an initial test upgrade to find any issues etc.  I’m not replicating the environment in terms of server roles etc. everything is installed on one server with local SQL.  I followed the steps outlined here: http://technet.microsoft.com/en-us/library/cc303436.aspx

This is part 4, part 1 can be found here, part 2 here, part 3 here and part 5 here.

Upgrade content databases to SharePoint 2013

Reference: http://technet.microsoft.com/en-us/library/cc263299.aspx

The SharePoint 2010 web application is configured to use Windows authentication, but Claims based authentication is required to enable the advanced functionality of SharePoint 2013.  Check the authentication provider that’s in use from Central Administration -> Manage web applications.  Click on the web application, then select Authentication Providers from the ribbon.

I used the process described here to convert a SharePoint 2010 classic mode web application to SharePoint 2013 claims based authentication.  You start by creating the web application using PowerShell, then once the SharePoint 2010 databases have been mounted using the command below, you use PowerShell to convert the web application to claims based authentication.

Use SQL Server Management Studio to restore the SharePoint 2010 content and My Site databases.

Reapply customisations web parts and web.config changes.

Use Mount-SPContentDatabase to attach the restored database into the web application you just created. Repeat the process for the My Sites database.

Verify the database upgrade status in Central Administration -> Upgrade and Migration -> check upgrade status.

View database upgrade log files in %COMMONPROGRAMFILES%\Microsoft Shared\web server extensions\15\LOGS

Next Steps

Verify sites as working correctly in SharePoint 2010 mode.

Configure search and perform a full crawl.

Backup the farm.

Upgrading SharePoint 2010 To SharePoint 2013 Part 2

These are notes from my first upgrade of SharePoint 2010 to SharePoint 2013.  The purpose of the upgrade is to carry out an initial test upgrade to find any issues etc.  I’m not replicating the environment in terms of server roles etc. everything is installed on one server with local SQL.  I followed the steps outlined here: http://technet.microsoft.com/en-us/library/cc303436.aspx

This is part 2, part 1 can be found here, part 2 here, part 3 here, part 4 here and part 5 here.

Copy databases to the new farm for upgrade to SharePoint 2013

Reference: http://technet.microsoft.com/en-us/library/jj839720.aspx

As this is a test upgrade, don’t set the databases to read-only.

Backup all the SharePoint 2010 content databases and the databases for any service applications you’re going to upgrade.  See part 1 for upgradeable service applications.

Copy the SharePoint 2010 database backups to the SharePoint 2013 SQL server.

Restore the SharePoint 2010 database backups on the SharePoint 2013 SQL server.

If upgrading SQL server versions, change the database compatibility level to match the new SQL server version.

In Place Upgrade Of Windows Server 2008 R2 Standard To Enterprise Or Datacenter Edition

If you need to upgrade a server running Windows Server 2008 R2 Standard to either the Enterprise, or Datacenter editions, it’s possible to do so online, without re-installing Windows.

Open an elevated command prompt and type DISM /Online /Get-CurrentEdition.  This will return the current Windows version.

Type DISM /Online /Get-TargetEditions to list the Windows editions to which this server can be upgraded.

If you type DISM /Online /Set-Edition:ServerDataCenter you’ll get the message in the screenshot below.  This is because even if you’re using a KMS server for internal activation, you have to provide a product key.  Fortunately, Microsoft have a page that lists the KMS client setup keys http://technet.microsoft.com/en-us/library/ff793421.aspx.  On this page you can find keys for Windows Server 2008 R2 Enterprise and Datacenter.

Typing DISM /Online /Set-Edition:ServerDataCenter /ProductKey:xxxxxx will upgrade the operating system.  All that’s required to complete the upgrade is a reboot.