Subscribe:      
 

Upgrading SharePoint 2007 to SharePoint 2010: Second Steps

Written By: Scott Murray -- 10/4/2011 -- join -- contribute -- (2481) comments -- printer friendly version

Rating: Rate --

Categories: Configurations, Infrastructure, MOSS 2007, SharePoint 2010, SharePoint Foundation 2010, System Administration, WSS2, WSS3

< Prev - 1 | 2 | - Next > | Become a paid author

Now that the lecture on documentation is complete, we can actually run the upgrade. If you had to make changes to your existing site, such as removing a defunct webpart, you will want to backup the existing site again, and then move and restore it. You will want to perform one last check using the PowerShell test-spcontentdatabase to make sure all the changes, upgrades, deletes and such produce no warnings or errors.

Finally, the actual upgrade can start; you will first need to remove the existing default content database. You remove it in Central Administration > Application Management>Manage Content Database...

Remove Content DB


Next you mount the restored database using the PowerShell Mount-SPContentDatabase database command. An example of the command is: Mount-SPContentDatabase -Name <database name> -DatabaseServer <database server> -WebApplication <SharePoint URL>

SharePoint recognizes that the database is a SharePoint 2007 version and institutes an upgrade routine. You expect everything to run without a hitch, since you tested the upgrade multiple times using the test-spcontentdatabase command. Unfortunately, normally you will encounter one of several errors and, as such, the upgrade will fail. The upgrade creates two log files that we can use to troubleshoot any errors.

Upgrade Logs


The Upgrade Log contains all the upgrade details and is much longer than the error log. The error log contains the first level details you need to help solve any issues with the upgrade process, so this log should be the first place to start researching an upgrade failure. One common issue pertains to the Publishing features in SharePoint, which generally results in an error similar to the follow:

[PowerShell] [SPSiteWssSequence2] [ERROR] [7/16/2011 6:23:21 AM]: Feature upgrade incomplete for Feature 'PublishingSite' (Id: 'f6924d36-2fa8-4f0b-b16d-06b7250180fa') in Site 'http://xxxxxxxxxxx'. Exception: A duplicate content type name "Resource" was found.'

You will need to research your exact issue, but for this error, you can start by reviewing the data in the dbo.ContentTypes table within the Content database. In anotherMSSharePointTips articleMatt Takar provides an excellent solution to address one variation of this issue in Publishing Feature Activation Error After SharePoint 2007 to 2010 Migration .

Of course other issues could surface that you will need to address before you restart the upgrade, but when you are ready, you can restart the upgrade by issuing the Upgrade-SPContentDatabase -Identity <Content Database Name> PowerShell command. The upgrade should begin again, and hopefully no additional errors will result. Again recheck your logs.

Once the upgrade is complete you will want to navigate to your site and verify it is accessible. Additionally, you can perform the Visual Upgrade to the site and any sub sites to bring the visual aesthetics of the sites to SharePoint 2010 standards.

During our test upgrades, an additional issue was encountered; the server name changed which caused Alerts to stop working. You can see detail about this issue at the following web sites:

http://blogs.microsoft.co.il/blogs/leonide/archive/2011/04/11/sharepoint-2010-sharepoint-alerts-don-t-work-after-upgrading-from-sharepoint-2007.aspx

or

http://blogs.msdn.com/b/skelley/archive/2007/06/18/alerts.aspx.

Although the later link is for MOSS 2007, the process and issue is the same. Be sure to verify in the dbo.ImmedSubscriptions and dbo.SchedSubscriptions tables, that the server name was updated in the Properties field.

At this point, you should have a working SharePoint 2010 Test site. Any additional content databases will need to be attached, Search Services will need to be created,and the User Profile Service will need to be setup. Take a look at Database Attach method to migrate MOSS 2007 User Profile and My Site to SharePoint 2010 by Udaya Kumar for details on the User Profiles Service. Since you have documented exactly what steps were required, including any upgrade restart and alert fixes, when the time comes for the production upgrade, an upgrade plan can be in place to have the upgrade run smoothly.


Next Steps:

< Prev - 1 | 2 | - Next >



Learn more about SharePoint



Sponsor Information




Copyright (c) 2010-2017 Edgewood Solutions, LLC All rights reserved
privacy | disclaimer | copyright | advertise | contribute | feedback | about
Some names and products listed are the registered trademarks of their respective owners.


MSSharePointTips.com | MSSQLTips.com