Last week I experienced major problem which took me more than two days to resolve. On one of our SharePoint farms User Profile Synchronization Service was stopped, and nothing I tried could not help to start it. And believe me, I tried almost everything I read on internet. But no, service was stubborn, not wanting to start. Then after two days of wall hitting I noticed following entry in ULS log file:
Failed to set the new Service Broker on database User_SyncDatabase on server SQL. Exception: The operation cannot be performed on database "User_SyncDatabase" because it is involved in a database mirroring session or an availability group. Some operations are not allowed on a database that is participating in a database mirroring session or in an availability group. ALTER DATABASE statement failed. ALTER DATABASE statement failed.
It turned out that the reason for all this mess is because all SharePoint database are in SQL High Availability group, despite the fact that Microsoft is claiming that this is allowed (http://ift.tt/291xETQ).
Just by removing User_SyncDatabase from High Availabilty group User Profile Synchronization service was started without a glitch. Go figure!
After starting the service, I returned database to HA group, and everything is working without further issues.
Of course, documentation regarding this strange behavior does not exist, there is only one blog explaining this, and it is on Russian. For those who can understand it, here it is: http://ift.tt/28XXRQw
I hope my blog post will help some poor soul, who lost all hopes that User Profile Synchronization Service would start ever again. For sure, I needed one.
by Krsto Savic via Everyone's Blog Posts - SharePoint Community
No comments:
Post a Comment