5

I have a problem with my SharePoint 2013 installation, that is driving me nuts. The same error appears in the event logs every 10 minutes:

The Execute method of job definition 'Microsoft.Office.Server.Search.Administration.CustomDictionaryDeploymentJobDefinition'(ID 9bc98c89-33c9-41e4-ae77-291374f254974045149c-1b98-3007-084b-a2c9b948a7b0) threw an exception. More information is included below. Failed to run flow Microsoft.CustomDictionaryDeployment. Correlation Id: 6c6dfa9b-60fb-106c-1067-9f0ff5915935.

It is a fresh install of SP2013 on Server 2012 with AD and SQL on external servers. I did not define any custom dictionaries and I made sure, that my search content access account (SP_Crawl) has reading permissions to the managed metadata service application (as suggested here). Still the error keeps coming.

Any idea what I am missing here?

2

Please give your search content account access to the managed metadata service application: http://get-sharepoint.com/2013/04/failed-to-run-flow-microsoft-customdictionarydeployment/

** EDIT: Above I stated content access account, it should be the service account (windows) that's running search. Apologies for confusion.

  • -1 That's the same page the OP links to in the question, saying it didn't work. – Stu Pegg May 9 '13 at 8:25
  • Hello - he must not have added the permissions correctly, I can assure you this corrects the issue – Ryan May 9 '13 at 12:55
  • Unfortunately that's a discussion you'll have to have with them. If you have any hints as to how to better implement the recommendations in the link then that may help. But as it stands you're recommending steps that they've specifically said didn't work for them. – Stu Pegg May 9 '13 at 15:05
  • The OP says he used the content access account, not the search service account, which is what @Ryan suggested in his edit and what the linked page recommends. Although I suppose if both things are the same account there must be some other issue. – Matt Oct 31 '13 at 17:57
  • +1 Search Service account is the one you should add. Just had the issue and was able to fix it. – Jussi Palo Apr 11 '16 at 10:24
0

Add read access for your Default Content Access Account (that you find in the Search Service Application) in the Managed Metadata Service Application.

  1. Central Admin
  2. Application Management
  3. Manage Service Applications
  4. Select the Managed Metadata Service
  5. Clock Permissions in the ribbon
  6. Give your Default Content Access Account Read Access to Term Store

enter image description here

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.