Article – Fix it – SharePoint 2013 User Profile Synchronization Service cannot be started with SQL Server 2014
I wrote an article on configuring User Profile Service for SharePoint 2010 and I have been using/ following the same steps for so many implementations up until last week.
For those who have not read it before – http://www.sharepoint24x7.com/2011/01/09/configuring-user-profile-services-in-sharepoint-server-2010/
However, I installed a new environment for one of our client last week and tried to start the User Profile Synchronization Service using Manage services on server page in Central Administration web site and it did not work.
When I click Start link to start the User Profile Synchronization Service, it stays in “Starting” state for some time (actually little longer) and then goes back to “Stopped” state.
I executed all the following troubleshooting tasks and made sure that I tried all the possible solutions based on my experience and others experience:
- Adding Farm service account in to the Administrators group
- Deleting User Profile Services service application and recreating it
- Verify the password of Farm service account
- Clearing SharePoint Configuration Cache
- Changing the Log On As account for Forefront Identity Manager Service and Forefront Identity Manager Synchronization Service
I did all these but no luck
I started investigating further and noticed following:
- I managed to successfully start/ configure User Profile Synchronization Service on 03 VMs with Windows Server 2012 R2, SharePoint Server 2013 with Service Pack 1 and SQL Server 2012 R2
- I failed to start/ configure User Profile Synchronization Service in 03 VMs with Windows Server 2012 R2, SharePoint Server 2013 with Service Pack 1 and SQL Server 2014
I downloaded and applied June 2015 Cumulative Update for SharePoint Server 2013.
Woooohhhhooooo…!!!! It worked…!!!
Based on my investigation, I believe that SQL Server 2014 is the culprit and applying June 2015 CU resolved the issue.
I have been trying the new SharePoint Server 2016 bits for few months through the TAP programs and now time has come to talk about in public.
Microsoft released SharePoint Server 2016 preview build 16.0.4316.1217 on 10th August for TAP participants and now the same build has been released to public.
It’s pointless recreating the same blog and visit Bill Baer’s post about to get more information on the SharePoint Server 2016 IT Preview.
Announcing availability of SharePoint Server 2016 IT Preview and cloud hybrid search - https://blogs.office.com/2015/08/24/announcing-availability-of-sharepoint-server-2016-it-preview-and-cloud-hybrid-search/
SharePoint Server 2016 IT Preview Reviewer Guide - http://www.microsoft.com/en-us/download/details.aspx?id=48713
Download SharePoint Server 2016 IT Preview - http://www.microsoft.com/en-us/download/details.aspx?id=48712
This preview meant and focuses on infrastructure new features and enhancements and I believe that’s why they call is as IT Preview.
Yesterday we had our July monthly user group gathering for Sri Lanka SharePoint User Group. We had 02 sessions – Business Continuity and Office 365 API.
Dinusha delivered a session on Office 365 API.
I delivered a session on implementing a business continuity for SharePoint and I covered topics such as monitoring SharePoint using Health Analyzer, Diagnosing logging, Usage and health data collection, implementing high availability using distributing servers and services using SharePoint WFEs, Application services servers, network load balancing, database mirroring, backup SharePoint and SQL Server databases and scheduling using Windows Task Scheduler.
Today we came across with a situation where we keep getting a runtime error when we try to perform our normal day-today operations in our SharePoint 2013 based solution. It started throwing a runtime error with a error code - HRESULT: 0x80131904 and it failed to save data into the SharePoint database.
The reason was the SharePoint Configuration database LOG file has grown to 91 GB and there was not enough free space in the physical disk. Because of this, SharePoint was unable to commit database changes and there was a huge performance impact. The solution we found was:
- Change the recovery model for the Database from Full to Simple
- Shrink the database
I executed the following SQL command and it brought the database log file from 91GB to 1 MB which solved my issues.
ALTER DATABASE[SharePoint_Config] SET RECOVERY SIMPLE WITH NO_WAIT
DBCC SHRINKFILE ('SharePoint_Config_Log')
Did you know that we can implement Metro UI in SharePoint 2013? It can be implemented very easily with out-of-the-box features in SharePoint 2013.
Learn how to implement Tiles navigation in SharePoint 2013:
Host header or Host-named?
Learn the difference between them and how to create host-named site collections.
Learn different service applications available in different editions in SharePoint platform.
Learn authentication improvements in SharePoint 2013.
Not sure whether you have already heard, we will not be having Microsoft world-wide SharePoint Conference in this year. They just announced next SharePoint Conference and that will be in Las Vegas again in March, 2014.
I’m very excited to be in Las Vegas again to be part of the greatest SharePoint conference in the world.
More information: http://sharepointconference.com/
Learn new Shredded Storage feature which is available in SharePoint 2013.