Commented Unassigned: After Installing SP2013 with SP1 Every so often Search fails due to the members of SPSearchDBAdmin being removed from the database role [21167]

After Installing SP2013 with SP1 Every so often Search fails due to the members of SPSearchDBAdmin being removed from the database role and not being added backin.

This happens about once a week.

Anybody any ideas.

I have seen a few blogs about this and all they say is add them back in when they go which is no good on a production system.

Thanks

Nigel
Comments: ** Comment from web user: Nigel_Price **

Hi Brian

I have only seen this happen when the farm was created with AutoSPInstaller. I have seen items on the internet pointing the finger at AutoSPInstaller, which may, of course, be wrong..

The Search account login loses membership of the database role SPSearchDBAdmin in the search database. This results in the Search Admin function not working. The fix is to put the user back into the role. Obviously you cannot keep doing this.

I understand this happens because an as yet unidentified process recreates the database role SPSearchDBAdmin in each of the 4 search databases.

The recreation process drops all the user members in the role; drops the role and then recreates it. The problem is the users do not get added back in.

In our case it does not add back in the users based on our account logins SP_Farm and SP_Search_AGT

The result is the Search functionality being inaccessible to the actual users.

Change the permissions on the database. Give minimal permissions so go to the database and give the service account (SP_Search_AGT) SPSearchDBAdmin role permissions.. Fixed the problem.

A consequence of this change is that the accounts will no longer be affected and the SPSearchDBAdmin role is recreated with the correct members.

Regards

Nigel.