Note
Access to this page requires authorization. You can try signing in or changing directories.
Access to this page requires authorization. You can try changing directories.
Question
Friday, July 24, 2015 6:11 PM
Hello all,
Greetings,
I am facing this error at one of my customer SharePoint 2013 environment. "UserProfileApplication.SynchronizeMIIS: Failed to configure MIIS post database".
Scenario:
We are trying to run User Profile Synchronization service, but every time after 5 mins in starting status, it ended up with stopped .
Environment setup:
2 WFE
1 APP
1 SQL 2012
Previously we have SQL Server 2008 R2, and we were getting the same error, In order to get over to this problem, we migrate the SQL Server from 2008 R2 to 2012.
We have gone through each and every blog / forum post and try to rectify based on the recommended steps, but of no use.
The following article link states four Possible causes
Possible Cause 1: This is due to insufficient privileges for the
SharePoint Farm Account on the Sync DB (not the Config DB!). You need to
add the farm account to the Sync DB users as DBO with a default schema
of DBO and then start UPS again.
We have verified that SharePoint Farm Account is DBO with default schema of DBO.
Possible Cause 2: Incorrect
Pre-requisites installed , i.e SQL server Native Client 2012 /2014 is
installed , while the Requirement is to have a SQL 2008 /2008 Sp1 .
Details here : http://technet.microsoft.com/en-us/library/cc262485.aspx#reqOtherCap
We have verified that on all the SharePoint boxes, 2008 R2 native client is installed
Possible
Cause 3: If you use SQL server 2014 to host the Sync DB or Moved your
Databases to SQL 2014 ( Sharepoint 2013 ) , then there is a known issues
& you need to Update to April 2014 CU or above for Sharepoint 2013 ,
https://support.microsoft.com/en-us/kb/2760265
We have SQL Server 2012, not SQL Server 2014
Shakir Majeed Khan, MCITP (SharePoint 2010), MCPD(SharePoint 2010)
All replies (12)
Friday, July 24, 2015 6:12 PM
Following are more information
Possible
Cause 4: Connectivity issues to SQL server , like Wrong Alias . Start
-->Run-->Cliconfg to check & configure aliases
As I have mentioned that we have migrated the Database from 2008 R2 to 2012, we have done entry into the SQL Alias in order to connect with SQL Server.
Previously it was with named instance, now to check that if we make the instance as default that would help, so we make that as default instance. I have followed SQL Alias post and other blog post in order to do SQL Aliasing. But again its of no use.
Possible cause 4 : Using FDQN of SQL server while creating the SharePoint server Farm .
Our Environment used FQDN of SQL Server.
Following steps we have already done with
- Deleting the UPA and created again
- I found out that the native client on SQL and SharePoint boxes are different, on SQL its sqlncli11.dll as this is SQL Server 2012 and on the SharePoint Boxes it is sqlncli10.dll. So I install the SQL 2012 native client on SharePoint boxes, without removing the SQL 2008 r2 native client, but no use. http://blogs.technet.com/b/sajiths/archive/2014/04/12/user-profile-synchronization-service-stuck-in-39-starting-39-state-sharepoint2013.aspx , its mentioned in the comments
- Restarted the servers.
- Done this changes on the server hosting UPS http://www.harbar.net/articles/sp2010ups2.aspx#ups4
Do let me know if you know any thing else which might be helpful to resolve this issue.
Shakir Majeed Khan, MCITP (SharePoint 2010), MCPD(SharePoint 2010)
Sunday, July 26, 2015 1:04 PM
Please respond to the query i posted on below link
Shakir Majeed Khan, MCITP (SharePoint 2010), MCPD(SharePoint 2010)
Tuesday, July 28, 2015 2:18 AM
Hi,
Thank you for your question.
We are currently looking into this issue and will give you an update as soon as possible.
Thank you for your understanding and support.
Best Regards,
Lisa Chen
TechNet Community Support
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected].
Tuesday, July 28, 2015 2:35 AM
HI Shakir,This issue could be of many reasons like the SQL,DB issue,Permissions.Please check the below to resolve the issue.Please check the link provided below that explains the cause of UPS not started.
· Ensure to restart the user profile service and synchronization service
· Ensure to restart the FIM services
· Ensure to do IISReset after the services starts
· Ensure to reboot the server
· Ensure to have the available space on DB server and SP server
http://expertsharepoint.blogspot.de/2014/03/user-profile-synchronization-service.html
Anil Avula[Partner,MCP,MCSE,MCSA,MCTS,MCITP,MCSM] See Me At: http://expertsharepoint.blogspot.de/
Tuesday, July 28, 2015 9:35 AM
Thanks Anil, for your reply,
I have verified the following
· Ensure to restart the user profile service and synchronization service (Done)
· Ensure to restart the FIM services (Done)
· Ensure to do IISReset after the services starts (Done)
· Ensure to reboot the server (Done)
· Ensure to have the available space on DB server and SP server (Done)
I have gone through to your blog, you have mentioned to UIShell , but i am unable to find that folder and the miisclient.exe,
Browse to the location "C:\Program Files\Microsoft Office Servers\15.0\Synchronization Service\UIShell" - See more at: http://expertsharepoint.blogspot.de/2014/03/user-profile-synchronization-service.html#sthash.0v3NdsJG.dpuf
Please let me know if you have any other suggestions, because i am running out of ideas.
Shakir Majeed Khan, MCITP (SharePoint 2010), MCPD(SharePoint 2010)
Tuesday, July 28, 2015 9:36 AM
Appreciated.
Yes this has become very critical from our project perspective, so i required urgent response from your side.
Regards,
Shakir Majeed Khan, MCITP (SharePoint 2010), MCPD(SharePoint 2010)
Tuesday, July 28, 2015 12:21 PM
Hi Shakir,
I will merge these two posts with the same question, thanks for understanding.
Regards,
Daniel Yang
TechNet Community Support
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected].
Tuesday, July 28, 2015 12:23 PM
Thanks a lot !
Shakir Majeed Khan, MCITP (SharePoint 2010), MCPD(SharePoint 2010)
Wednesday, July 29, 2015 7:35 AM
Hi Shakira,
Please try the following steps:
Make sure there are no Profile Synchronization Setup one-time timer jobs stuck running in CA.
Delete all of the FIM certificates using certificate manager:
1.Run the Microsoft Management Console (MMC) and Choose “Add/Remove Snap In” from the File Menu.
2.From the list of snap ins choose Certificates and then choose “Computer Account”
3.Now in the list of certificate stores, we need to examine the one that the command refers to: The Trusted Root Certification Authorities store.
4.Delete all of the ForefrontIdentityManager certificates from the Trusted Root Certification Authorities.
5.Click on Personal > Certificates, delete any ForefrontIdentityManager certificates in the store
6.Run IISRESET
Best Regards,
Lisa Chen
TechNet Community Support
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected].
Wednesday, July 29, 2015 8:16 AM
Dear Lisa,
Correction my name is Shakir :)
I performed all the steps on the server which run the user profile Synchronization service. But it showing the same error.
Regards,
Shakir Majeed Khan, MCITP (SharePoint 2010), MCPD(SharePoint 2010)
Monday, December 4, 2017 4:38 PM
Hi All,
I am having the same exact issue and tried all the possible steps. Went through the posts already mentioned above and everything looks intact, but still getting the same error.
Any idea?
Thanks
Sakthi.
Sakthi Ganesh
Monday, December 4, 2017 6:39 PM
Just to update all ...
It is ultimately connection issue at Transport layer level. We have got the Trans Layer updated to TLS 1.2. The SQL Server 2008 R2 Native Client does not support TLS 1.2 by default. You might want to apply the hotfix for TLS 1.2
https://support.microsoft.com/en-us/help/3135244/tls-1-2-support-for-microsoft-sql-server
Restarted the server and boom, the Profile Sync Service started. I hope this helps someone.
Thanks
Sakthi.
Sakthi Ganesh