- Go to SharePoint Central Administration website
- Click on ‘Manage Service Applications’ under Application Management
- Click on ‘User Profile Service Application’ or the name of your user profile service app
- On ‘Manage Profile Service’ page, click on ‘Configure Synchronization Connections’ under Synchronization section
- Click ‘Create New Connection’
- Enter the Connection Name, Forest Name, Account Name, Password, select OU levels under Containers section to sync profiles from that OU level
- Click OK to configure the connection
In this case, you will get error:
|MOSS MA Not Found Error|
|Correlation Query Tool’s Result based on Correlation ID Error|
- Looking at the query results, I saw that connection was trying to connect to first server and connection was refused. That server has been having issues and was already planned for removal from the farm. It was not running the User Profile Service.
- I then looked at the ‘Manage Servers in the Farm‘ page in SharePoint Central Administration > System Settings. I looked for ‘User Profile‘ service on that page to confirm which servers in the farm are running that service. It was not configured on App Server 1. I then went to ‘Manage Service Applications‘ page under Application Management in Central Administration Website.
SharePoint Manage Service Applications Page – Properties icon grayed out
Hover over the ‘User Profile Service Application‘, don’t click on the name but click on the right side of it. That will select the service application and activate the Operations Ribbon group on top.
SharePoint Manage Service Applications Page – Properties icon active
- Click on Properties icon in the SharePoint ribbon. That will bring the ‘Edit User Profile Service Application‘ dialog box. Scroll to the lower half of page and look under ‘Profile Synchronization Instance‘ field. It is fourth field from the bottom. In my case, it was set to the App Server 1. I changed it to the server that was actively running User Profile Service and clicked OK at the bottom.
SharePoint – User Profile Service Application – Profile Synchronization Instance – Old Server
- Message was displayed saying ‘Profile Service Application successfully updated.’ Click ok on that dialog box to close it.
- I tried to configure the Profile Synchronization Connection again (Steps in Issue Scenario section above). Same error happened. I looked at the ‘Profile Synchronization Instance’ field (step 3 above), the same old App Server 1 was listed there. Not good.
- I started the ‘User Profile Service’ on that old App Server 1 from the Central Administration > ‘Manage Services on Server’ page for App Server 1.
Sharepoint – Started User Profile Service from Manage Services on Server page
- I then changed the server under ‘Profile Synchronization Instance‘ to a new server that was running the User Profile Service. This time the setting stayed permanently and didn’t revert back as in last attempt.
SharePoint – User Profile Service Application – Profile Synchronization Instance – Active Server
- I tried to configure user profile sync again. (Steps in Issue Scenario section above). It was successful this time.
One important thing. I didn’t have to start the ‘Forefront Identity Manager Service‘ on the old server using Windows Services console. That service was in disabled state as before. After successfull Sync connection, I then stopped the ‘User Profile Service‘ on the App Server 1 that was started in step 6 above. I used SharePoint Central Administration website. It is not recommended to start / stop FIM service using Windows Services console.
|Sharepoint – Forefront Identity Manager Service (part of User Profile Service App) in Windows Services Console|