SharePoint Experts, Information Architects, Expert Witness

We provide consulting in a broad array of business and technology from architecture to design to deployment of global systems with a focus on surfacing data in the enterprise. Specialists in Microsoft, we are a premier provider of SharePoint Expertise (including 2016 and Office 365). We also provide Expert Witness/Legal Expert in eDiscovery, source discovery, patent infringement, piracy and more! We also have established SICG DLDS s.a. - our counterpart in Costa Rica that specializes in water systems ( - Contact me direct: or call 704-873-8846 x704.

Search This Blog

Tuesday, September 29, 2015

Issues with SharePoint 2013 Search - Event ID 1357

New installation - first time I came across this issue and there's no excuse for it. Apparently one of the SharePoint updates (one can only assume) seems to drop the proper permissions within the Search environment and suddenly, you get no new crawls.

You will most likely get Warnings in the event application log for Event ID 1357. The message (cuttting it down to the relevant info):

A database error occurred. Source: .Net SqlClient Data Provider Code: 229 occurred 0 time(s) Description:  Error ordinal: 1 Message: The EXECUTE permission was denied on the object 'proc_MSS_CrawlAdmin', database 'DSNet_Search_AdminDB', schema 'dbo'., Class: 14, Number: 229, State: 5    at System.Data.SqlClient.SqlConnection.OnError(SqlException exception, Boolean breakConnection, Action`1 wrapCloseInAction)
   at System.Data.SqlClient.TdsParser.ThrowExceptionAndWarning(TdsParserStateObject stateObj, 

Go to the SQL Server and check - the Search Service Account probably doesn't have the proper permissions on the Search Databases. In my case, I had ALREADY checked these and they were changed.

In a low risk environment, assign it DBO rights. For high risk, it must have Security Admin and DDL Admin rights. Alternately, you can grant the rights to that account via the Database > Security settings (granting execute to all of the Stored Procecdures).

No comments: