Windows detected your registry file is still in use by other applications or services. The file will be unloaded now. The applications or services that hold your registry file may not function properly afterwards.
Unknown SQL Exception -2146893055 occurred. Additional error information from SQL Server is included below.
A connection was successfully established with the server, but then an error occurred during the pre-login handshake. (provider: SSL Provider, error: 0 – The handle specified is invalid)
User Profile Service Application Stuck On Starting March 15, 2013
User Profile Firewall Problems December 17, 2012
This post talks about various issues seen in User Profile Service application configuration due to Web Proxy configurations. As the User Profile Import using the FIM has not changed in SharePoint 2013 these would apply to SharePoint 2013 as well.
User Profile Service Application Provisioning Sequence December 3, 2010
This is part two, which talks about the Details of setting up the User profile Service application along with details of events which happen under the hood on SharePoint & SQL servers.
Let’s get into the details of Setting up the User Profile Service Application
Start the “User Profile Service”
1) When we start the “User Profile Service” from the Central Administration UI, we first start with provisioning the User Profile Service instance.
User Profile Problem and SQL Alias November 8, 2010
While deploying a SharePoint 2010 farm recently in which I implemented database mirroring in SQL Server 2008 using two servers with a Named Instance respectively for each server (SQL1\PRINCIPAL and SQL2\MIRROR), I could not get the User Profile Synchronization Service to start. It would remain in a status of “Starting” for about 10 minutes before eventually showing a status of “Stopped”.
After reading through dozens of blog posts, especially this one, I determined that the Forefront Identity Manager Synchronization Service (FIMSynchronizationService) was trying to connect to the Default Instance of SQL1, instead of the correct Named Instance of SQL1\PRINCIPAL. Not sure if this is default behavior out of the box, but sure seems to be that way.
The Workaround – configure a SQL alias on the application server. Here’s how:
SQL Alias and named instance and UPS.
User Profile Setup and Social Networking May 17, 2010
User Profile default schema bug. Powershell credentials workaround.
Plan for social computing and collaboration.
User profile setup.
End to end setup of user profile service.
Social networking overview.