Hi there

We recently noticed the following Critical error thrown in Windows Application Event Viewer every 10 minutes:

The Execute method of job definition Microsoft.Office.Server.Search.Administration.CustomDictionaryDeploymentJobDefinition (ID 7488ea1a-5549-45e4-9405-76cce715dc65) threw an exception. More information is included below.

Failed to run flow Microsoft.CustomDictionaryDeployment. Correlation Id: 8229149d-b6a1-9013-06fa-13eb7e6cd953.

Here's the corresponding SharePoint log for the correlation ID:

06/26/2015 11:10:16.63 	OWSTIMER.EXE (0x3CD8)                   	0x5908	SharePoint Server Search      	Administration                	ad840	Medium  	Found settings: Dictionaries last checked for changes 01/01/1754 00:00:00	8229149d-b6a1-9013-06fa-13eb7e6cd953
06/26/2015 11:10:16.63 	OWSTIMER.EXE (0x3CD8)                   	0x5908	Search                        	Linguistic Processing         	68	Warning 	Custom dictionary deployment timer job failed. SearchComponent: OWSTIMER.EXE, SearchServiceApplication: {f0417fac-93d1-4f7f-bdea-90ad544d3150}, FlowName: Microsoft.CustomDictionaryDeployment, CorrelationId: {8229149d-b6a1-9013-06fa-13eb7e6cd953}, Failure: System.InvalidOperationException: Unable to locate Managed Metadata Proxy which is default keyword taxonomy for SSA f0417fac-93d1-4f7f-bdea-90ad544d3150     at Microsoft.Office.Server.Search.Administration.SearchServiceApplication.FindDefaultMMAProxy()     at Microsoft.Office.Server.Search.Administration.CustomDictionaryDeploymentJobDefinition.GetChangedDictionaryTermSetIds(DateTime lastChecked)     at Microsoft.Office.Server.Search.Administration.CustomDictionaryDeploymentJobDefinition.DoExecute(CtsConnection connection)     at Microsoft...	8229149d-b6a1-9013-06fa-13eb7e6cd953

This error and the bit of digging Ive done point to the Managed Metadata Service, but we dont have this service installed and never have and this error only recently started 

The  only two changes we've made recently was updating to the latest June CU (from May) and removing and re-configuring the SSRS service due to issues we were seeing there. We dont believe this error was thrown prior to these changes.

Thanks in advance!

• Edited by timofcourse 16 hours 14 minutes ago