After a patch cycle
the Event log starts filling up on the web/app servers -
The following 6398 Timer errors start appearing every 10/30 minutes in the event viewer:
The Execute method of job definition
Microsoft.Office.Server.Search.Administration.QueryClassificationDictionaryUpdateTimerJobDefinition
(ID <GUID>) threw an exception. More information
is included below.
Unable to locate Managed Metadata Proxy which is
default keyword taxonomy for SSA <ID>
The Execute method of job definition
Microsoft.Office.Server.Search.Administration.CustomDictionaryDeploymentJobDefinition
(ID <GUID>) threw an exception. More information
is included below.
Failed to run flow
Microsoft.CustomDictionaryDeployment. Correlation Id:
<ID>.
All of the search
functions still work, so nothing actually seems to be malfunctioning, however
having the event viewer constantly full of false positives could potentially
create a situation where important events are missed, or it becomes
unnecessarily difficult to find an event you're looking for.
There are several
suggestions when searching online -
- In the Managed Metadata Service Application, check "This service application is the default storage location for keywords" and "This service application is the default storage location for column specific term sets".
- Give your search service account access to the Managed Metadata Service Application.
- Re-run the configuration wizard on the servers one by one.
- Reset the Index and do a full crawl.
None of these
suggestions work if the Managed Metadata Service Application was never added or
configured in the first place. Rather than adding an unnecessary service
application, I opted to just disable the unneeded Timer jobs from the Central
Administrator.
From the CA click on
Monitoring, Check Job Status, then click Job History on the left side
navigation.
From the View: drop
down, select Failed Jobs.
This will bring up
all of the failed Timer jobs. We're looking for the Query Classification
Dictionary and Search Custom Dictionaries jobs.
Click on the job and
click on the Job Title, and then click on Disable. Repeat for the second job.
These erros have been driving me insanse on a couple of legacy SP2013 installs that we have. No metadata service set up, so couldn't understand why we were getting the error. This is a nice little work around to make the logs cleaner.
ReplyDeleteAs you said, if things like the metadata service are not used, no point in provisioning them.
Thank you!!!
What is the cause?
ReplyDeleteDoes this harm the search on the site at all?
ReplyDeleteFantastic post.
ReplyDeleteReally enjoyed reading it and it held my attention all the way through! Keep it up.
Read my Latest Post
Great post
ReplyDeleteThanks.
I am inspired with your post writing style & how continuously you describe this topic. After reading your post, thanks for taking the time to discuss this about sharepoint training, I feel happy about it and I love learning more about this topic.
ReplyDeleteSmm Panel
ReplyDeletesmm panel
iş ilanları
hirdavatciburada.com
tiktok hile indir