Saturday, April 03, 2010

SharePoint 2010 Beta Migration Gotcha – SSP Errors

One of the big changes to SharePoint 2010 is the replacement of the Shared Service Provider concept with a series of application services.

Essentially instead of a central managed “pool” or bundle of application services such as Excel, User Profile, Search, and BDC, the new model allows farm administrators to turn on or off (and separately configure) an infinite variety of services that can add extra functionality to their farm.

This is a much more flexible model.

This new model does cause one problem if you are doing “in-place” migrations of existing 2007 portals to 2010 using the beta bits. For some reason, the Shared Service Provider database does get upgraded to 2010 but it causes a number of portal errors while it does so.

You’ll find these in your upgrade log file, in the 14 hive. These vary from User Profile errors to “certificate” errors. One common error looks like this:

[OWSTIMER] [UserProfileSharedResourceProvider12Sequence] [ERROR] [1/8/2010 9:23:42 AM]: Action of Microsoft.Office.Server.Upgrade.UserProfileSharedResourceProvider12Sequence failed.

[OWSTIMER] [UserProfileSharedResourceProvider12Sequence] [ERROR] [1/8/2010 9:23:42 AM]: Inner Exception: There are no online service instances for this application.

The “fix” is to delete all Shared Service Providers from your 2007 farm BEFORE doing the in place upgrade. The sts command to do this is:

stsadm -o deletessp -title SSP -force

This isn’t a big deal - this is only a beta problem.I very much doubt this will be the case in RTM which is due next month.

Hope that helps.


  1. If you delete your ssp, how do you upgrade My Links? Many of our users have setup My Links and we do not want to lose this data during the migration.

  2. Hi anonymous, the 2010 migration process does try to update the Shared Service Provider for you. This is only a beta bug as far as I know - you should be ok doing the upgrade without deleting your SSPs, when the final release is available. I always advise doing multiple migration tests to see what might go wrong.
    Hope that helps


Note: only a member of this blog may post a comment.