0

I have restored my managed metadata db and user profile db's on a new SharePoint 2013 farm with a SQL 2012 server. I recreated both service applications with the restored db's (created a new sync db otherwise I can't start the sync service). The managed metadata and user profile service application are working. No errors what so ever.

I now try to start the "User Profile Synchronization Service" This process takes a while but ends and the service is still stopped. During this time it is stuck in the famous starting state.

I get the following errors in the ULS Looks like something in combination with the managed metadata service :

ILM Configuration: Setting policy for service account   
ILM Configuration: Configuring database 
ILM Configuration: Re-starting mms service  
ILM Configuration: Checking mms service 
ILM Configuration: Error 'ERR_START_SERVICE'.   
UserProfileApplication.SynchronizeMIIS: Failed to configure MIIS post database, will attempt during next rerun. Exception: System.Configuration.ConfigurationErrorsException: ERR_START_SERVICE     at Microsoft.Office.Server.UserProfiles.Synchronization.ILMPostSetupConfiguration.ValidateConfigurationResult(UInt32 result)     at Microsoft.Office.Server.Administration.UserProfileApplication.SetupSynchronizationService(ProfileSynchronizationServiceInstance profileSyncInstance).   
UserProfileApplication.SynchronizeMIIS: End setup for 'User Profile Service Application'.ILM Configuration: Changing service account credentials

I have created multiple SharePoint 2013 farms in the past so all the requirements needed for starting the "User Profile Synchronization Service" are correct. All permissions etc.. are set.

Any ideas?

Regards Danny

Improve this question
1
  • I have tried the same but now creating a new managed metadata and ups application with new databases. So a clean setup. Even then I get the same error in my ULS
    – Danny
    Commented May 3, 2017 at 8:20

3 Answers 3

Reset to default
0

If you move UserProfileDatabases to a new SharePoint-Installation, you also have to move the Microsoft Identity Integration Server Key (MIIS) encryption key.

The whole process is very well described in this blog. It shows a move from SP2010 to SP2013 but also applies if you copy on the same version.

Improve this answer
2
  • 1
    In the export key section it states: Note: If you do not want to migrate Sync database, then exporting (and later importing) of encryption key is not required. I am using a new Sync database. So I don't need this step
    – Danny
    Commented May 2, 2017 at 16:10
  • Sorry, didn't read all details in your question. Added a new answer.
    – MHeld
    Commented May 3, 2017 at 6:56
0

Please check if you have installed "SQL Server 2008 R2 SP1 Native Client". You might have installed newer versions. The old one is a SharePoint 2013 Prerequisite

Maybe these articles also help:

ERR_config_Db while starting the UPA Synchronization service in SharePoint 2010/2013

Provisioning User Profile Service - Will not start

Improve this answer
2
  • I am using a SQL server 2012 and SharePoint 2013 SP1 and feb 2017 CU. Should I still install this?
    – Danny
    Commented May 3, 2017 at 7:12
  • I just checked in programs and features and the 2008R2 native client is already installed. When I run the installer it says that its already installed.
    – Danny
    Commented May 3, 2017 at 8:27
0

Turns out there was a dependency in the FIM service. The solution provided here

http://fangdahai.blogspot.nl/2017/01/resolved-failed-to-configure-miis-post.html

Fixed my problem.

Improve this answer

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.