Upgrading SharePoint 2007 to SharePoint 2010: Second Steps
Written By: Scott Murray -- 10/4/2011 --
(2481) comments --
Categories: Configurations, Infrastructure, MOSS 2007, SharePoint 2010, SharePoint Foundation 2010, System Administration, WSS2, WSS3
< Prev -
- Next >
| Become a paid author
the lecture on documentation is complete, we can actually run the
upgrade. If you had to make changes to your existing site,
as removing a defunct webpart, you will want to backup the existing
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.
the actual upgrade can start; you will first need to remove
existing default content database. You remove it in Central
Administration > Application Management>Manage Content
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 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.
normally you will encounter one of several errors and, as such, the
upgrade will fail. The upgrade creates two log files that we
use to troubleshoot any errors.
Upgrade Log contains all the upgrade details and is much longer than
the error log. The error log contains the first level details
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
issue pertains to the Publishing features in SharePoint, which generally results in an error similar to the follow:
[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.'
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 article Matt Takar provides an excellent
solution to address one variation of this issue in Publishing Feature Activation Error After
SharePoint 2007 to 2010 Migration .
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
Database Name> PowerShell command. The upgrade should
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.
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
working. You can see detail about this issue at the following
Although the later link is for MOSS 2007, the process and
is the same. Be sure to verify in the dbo.ImmedSubscriptions
dbo.SchedSubscriptions tables, that the server name was updated in the
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
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.
documented exactly what steps were required, including any upgrade
restart and alert fixes, when the time comes for the production
upgrade plan can be in place to have the upgrade run smoothly.
< Prev -
- Next >
- Check the first part of
- Microsoft offers full length documents to assist with your upgrade
including the following: