Tag Archives: User Profile Service

Using the SharePoint 2010 Administration Tool Kit Replication Engine

Requirement

Migrate user profiles from one farm to another farm using the Replication Engine tool provided in the SharePoint 2010 Administration Tool Kit. Note that this tool is used to migrate from one Mysite Host site to another. If you do not know what a Mysite Host site is, you should do more research before trying this.

Solution

This tool basically copies all user data from one site to another, including pictures, tags, comments, etc. It also populates the User Profile Service Application Profiles database. You cannot however, use this tool to replicate the sync connections in the User Profile Service Application. To configure your sync connections, you will still need to do it from Central Administration.

I encountered a few errors when using this tool. Making sure that check the following will increase your chances of success.

  • You must run the tool under an account with sufficient rights on both farms.
  • Give the account you are running the tool under local administrator rights temporarily on the server.
  • Run the tool from one of the SharePoint servers, NOT your client machine.
Once all the above conditions are checked, use the following instructions to begin replication
  • To start the tool, run PowerShell.exe with the ‘Run as Administrator’ command (using an account with the correct permissions to both farms).
  • Under powershell, browse to the folder C:\Program Files\Microsoft\SharePoint 2010 Administration Toolkit\Replication Engine
  • Type: .\ReplicationEngine.psc1c and press Enter.
  • A new PowerShell window will pop up.
  • In the new PowerShell window, type: get-help Start-SPProfileServiceFullReplication
  • This is the command you will need to type to replicate User Profile properties from one site / farm to another.
  • For a simple replication, I used the command: Start-SPProfileServiceFullReplication -destination <http://newfarm.com/mysite> -source <http://oldfarm.com/mysite> and it worked perfectly. I was able to transfer all the DEFAULT user properties using this command. If you have any custom properties, things are a little bit more complicated.

Hope this helps!

Comments ( 0 )

Error in PortalCrawl Web Service

Problem

We recently had to re-create the user profile service application. All went fine until we ran the first search crawl, SharePoint Search reported the following error:

Error in PortalCrawl Web Service.

We have the following URLs configured under the content source:

http://mysite
sps3://sharepoint

The errors being generated were related to crawling user profiles under http://mysite.

 

Solution

Some things to check:

  1. Ensure that the default content access account configured under search administration has access to the User Profile Service Application. Go to Manage Service Applications -> User Profile Service Application -> Administrators. Ensure that your content access account has “Retrieve People Data for Search Crawlers” permissions.
  2. If you have re-created your user profile service application, ensure that it is re-associated with the relevant web applications. In my case, I had to re-add the service connection not only to Mysite but the main SharePoint site. The reason for this is because my enterprise search portal resided on my main SharePoint site.

 

Comments ( 0 )

Audience targeted webpart not working for AD Group

Problem

You configure audience targeting for a webpart using AD groups. A newly added user is unable to see the webpart even though you have confirmed that the account has the correct AD group memberships.

Cause

SharePoint updates AD user group memberships only after the User Profile Synchronisation service is run.

Solution

Open Central Administration -> Manage Service Applications -> User Profile Service Application

Start an Incremental synchronisation.

The user should now be able to see the audience targeted webpart.

 

Comments ( 0 )

User Profile Service Stuck on Starting

Problem

You have followed Harbar’s Rational Guide to setting up the User Profile Service Application in SharePoint 2010 but the User Profile Service is still stuck on starting.

Solution

Ensure that the account you are running the UPS service is a local administrator for the provisioning process.

This is normally the farm account which also runs the SharePoint Timer service. You can remove admin rights later. If it is not a local admin, you will need to restart the Timer service after you grant the correct permissions.

Log on as the account that will run the User Profile Synchronization service.

If the User Profile Service Synchronisation Service is stuck on ‘Starting’:

  1. Run SharePoint Management Shell as a farm administrator.
  2. Type: stop-spserviceinstance | where { $_.typename -eq “user profile synchronization service” }
  3. The User Profile Synchronization service status should now be ‘Stopped’ or ‘Disabled’.

Check the Certificates store on the server that runs the User Profile Synchronisation Service and delete all the ForefrontIdentityManager certificates.

  1. Start -> Run -> mmc
  2. File -> Add / Remove Snap-in
  3. Select Certificates -> Computer Account -> Finish -> Local Computer -> Finish -> OK
  4. Expand Certificates -> Personal -> Certificates
  5. Delete all ForefrontIdentityManager certificates (if you have tried to provision the UPS unsuccessfully several times, you will see more than one certificate).
  6. Expand Certificates -> Trusted Root Certification Authorities -> Certificates
  7. Delete all ForefrontIdentityManager certificates (if you have tried to provision the UPS unsuccessfully several times, you will see more than one certificate).

Set the FIM Services to run as Local System

  1. Start -> Run -> services.msc
  2. Locate the two FIM Services: Forefront Identity Manager Service, Forefront Identity Manager Synchronization Service.
  3. Edit properties and set it to run as Local System account.

Check Central Administration for the ProfileSynchronizationSetupJob and delete any running jobs.

  1. Go to Central Administration -> Monitoring
  2. Delete the job.

Provision the User Profile Service using Central Administration.

Run your ULS logger to see what is happening. It should take no longer than 10 minutes to provision.

 

Comments ( 4 )

Unable to change User Profile Service Account

Problem

So you made a mistake by trying to change the service application account for the User Profile Service Application. You try to change it back to your farm account but get an ugly error message saying:

An object of the type Microsoft.SharePoint.Administration.SPWindowsServiceCredentialDeploymentJobDefinition named “windows-service-credentials-FIMSynchronizationService” already exists under the parent Microsoft.Office.Server.Administration.ProfileSynchronizationService named “FIMSynchronizationService”.  Rename your object or delete the existing object.

Solution

This problem is quite easy to fix. As the error message clearly states, there is a job that has already been created when you tried to change the the credentials for the UPS service application previously. However, when the provisioning failed the job never ran (it is a one-time job). This job is responsible for updating credentials on all servers that are running the FIM service.

To fix this, you need to delete the job:

  1. Open Central Administration -> Monitoring -> Job Definitions.
  2. Browse to the last page
  3. Delete the job: Windows Service “FIMSynchronizationService” Credential Deployment
  4. Go back to Security -> Configure Service Accounts and reset your UPS service to your farm account.
  5. Now go back to the Job definitions page, you will see that a new job with the same name has been recreated.
Comments ( 4 )