Note: This post is based on Beta 2 and is subject to change in future releases.
I highly recommend to review the Services upgrade model and User Profile Service overview on SP 2010 TechNet site before trying the following steps to upgrade a MOSS 2007 SSP database and My Site content to SharePoint Server 2010.
1. Under Services on Server in Central Admin, make sure both the User Profile Service and the Managed Metadata service are running.
2. Use the “New-SPProfileServiceApplication” cmdlet to create the new user profile service, make sure to use the MOSS 2007 SSP database name you want to upgrade for “ProfileDbName” parameter.
3. At this point SSP database should be upgraded along with two new databases for “Sync” and “Social”.
4. Check the “Upgrade Status” Page and confirm that SSP database upgrade finished successfully.
5. Create a Service Proxy using “New-SPProfileServiceApplicationProxy” cmdlet and pass the ID for the new Profile Service Application provisioned in step 2.
6. Confirm that all user profiles and other settings are imported.
7. From “Manage service application” page, select the upgraded User Profile service application and click “Administrators” icon on the ribbon.
8. Give Search default crawler account “Retrieve People Data for Search Crawlers” permission.
1. Run “Test-SPContentDataBase” cmdlet against the 2007 My Site Host content database and resolve the issues as needed.
2. After resolving the issues and installing missing DLLs and Features, run the command again to verify there are no further issues with the content database.
3. Make sure to remove the default content database when you provisioned the web application for My Site host. 4. Run the following stsadm command: stsadm -o addcontentdb -url http://<yourwebappsURL> -databasename <2007 MySite content database> [-databaseserver <the database server from above>]
5. Make sure Upgrade completed successfully by checking the “Upgrade Status” page.
6. After upgrading the content database, go to Manage Service Applications in Central Administration site and click on the upgraded User Profile Service you want to associate with the My Sites and click on “Setup My Sites” link.
7. Enter “My Site Host” URL and “Personal Site Location”, click on “OK” to save the setting and run the IISRESET.
Make sure that all existing content such as documents are accessible in the upgraded Personal site.
Thank you very much for your post, there are not many of those on MySites!
I try db attach upgrade of an uncustomized test envorinment, and get error while using New-SPProfileServiceApplication : The specified database is not a valid profile database.
I have created a new app pool for Shared Services with New-SPServiceApplication. As for database, I took a backup of "old" SSP database, created a new one, restored my backup onto it with Overwrite and used this database with New-SPProfileServiceApplication. Do you have any idea on what I do wrong here?
Great post. What if the db that will be migrated contain mysite content for users on a different domain. How can we associate the new domain users with the imported mysites?
We have upgraded SSP db to SharePoint 2010 successfully.
We got all user profiles including custom properties however the problem is only properties which have choice list that data is missed. What we can do in this case. Please help..
Source domain is different from destination domain.
Didnt work Same as Maria Skolota same error did you ever get it to work Maria Skolota?
Same problem this dosent work any one plese help
SPProfileServiceApplication : The specified database is not a valid profile database.
When i reach step 2, i get the following error msg in powershell:
New-SPProfileServiceApplication : An invalid application pool was specified.
what can be the possible reason
If you are getting the error "The specified database is not a valid profile database", check whether the language pack has been installed for MOSS2010.
Many people have asked about the error "The specified database is not a valid profile database". I came across the same problem but in my case I found that actually I was using the wrong database. In SharePoint 2007, I had two databases for the SSP, one to store profile information and another database for the SSP web application. Initially, I was trying to restore using the web application database and I got the above error. I then I went to SSP properties and notes that a different database is used to store profile info. Then I tried to restore using that database and it all worked fine.
I have manage to upgrade MySite, however the content is not migrated.
Its great article, i just went through it before trying my migration from MOSS2007 to SP 2010, and when i reach Mysite migration i had an errors when running "Mount-SPContentDatabase" command and the result was showing erros due to missing features not available in the new farm 2010, after cleaning some of it and running the test command again errors were still showing !!
so i decide to run "Mount-SPContentDatabase", and test the end result that has shown failed but still i got the Mysite migrated successfully but not working properly with the new interface .. and the visual upgrade option was deemed , so any Idea how to upgrade the interface to the new V4.master of SharePoint 2010.