What?
I have setup a new SharePoint 2010 non-production farm in a single server environment with Active Directory, SQL Server 2008 and SharePoint 2010 installed. (Not stand-alone installation)
The dreaded User Profile Synchronization Service fails to start as usual in a newly setup SharePoint 2010 farm.
The following error was found in the ULS logs:
UserProfileApplication.SynchronizeMIIS: Failed to configure ILM, will attempt during next rerun. Exception: System.Data.SqlClient.SqlException: Specified collection 'StringSchemaCollection' cannot be dropped because it is used by object...
Note that the above message shows up as an entry with High priority and not as an exception in ULS log.
Why?
There could be hell a lot of reasons why the User Profile Synchronization Service fails to start. First of all, it does not work in a single server stand alone installation with inbuilt database.
In my case, there were a couple of issues and I will try to explain how I fixed them in this post.
I have setup a new SharePoint 2010 non-production farm in a single server environment with Active Directory, SQL Server 2008 and SharePoint 2010 installed. (Not stand-alone installation)
The dreaded User Profile Synchronization Service fails to start as usual in a newly setup SharePoint 2010 farm.
The following error was found in the ULS logs:
UserProfileApplication.SynchronizeMIIS: Failed to configure ILM, will attempt during next rerun. Exception: System.Data.SqlClient.SqlException: Specified collection 'StringSchemaCollection' cannot be dropped because it is used by object...
Note that the above message shows up as an entry with High priority and not as an exception in ULS log.
Why?
There could be hell a lot of reasons why the User Profile Synchronization Service fails to start. First of all, it does not work in a single server stand alone installation with inbuilt database.
In my case, there were a couple of issues and I will try to explain how I fixed them in this post.