4

Yesterday I had to delete search service, I did it simply from CA - click delete search service with associated content. After that come my problem, two databases didn't removed, and search services didn't stop, I stopped service and removed databases by PowerShell but now I'm not able to run new search service I get error in CA and in ULS log I see many:

Fetching app info failed: Microsoft.Office.Server.Search.Query.SearchServiceNotFoundException: The search request was unable to connect to the Search Service.

In evet log:

Event 6398 The Execute method of job definition Microsoft.SharePoint.Administration.SPServiceInstanceJobDefinition (ID 755f7b69-7c8c-4e2c-bf8d-da10c42f80b1) threw an exception. More information is included below.

Attempted to perform an unauthorized operation.

Event 3899 Error executing service instance (un)provisioning job. Service instance: "SharePoint Server Search" (id "96a3525b-c4e8-41df-bdbe-728b1657553a) "Attempted to perform an unauthorized operation.""

Event 7034

The Execute method of job definition Microsoft.Office.RecordsManagement.Preservation.PreservationJobDefinition (ID b54f9c39-0798-4a5e-ac8c-6eb72b45e130) threw an exception. More information is included below.

The search request was unable to connect to the Search Service.

Improve this question
13
  • There error reads like your account does not have enough permissions on the sql server. That would explain why you could not remove the old databases and create the new ones. Can you try to create the Search Service Application with PowerShell like with my script: melcher.it/2012/07/…
    – Max Melcher
    Jun 30, 2014 at 15:22
  • But before I created search service on the same account and so on, I deleted old databases by powershell but now I'm not able to run instance of search, I'm not sure but it seems to me that some of search component wasn't delete and that's wy I can't do this? When I try to create new search service by CA the name of search service is with 1 it looks like this service is always run?
    – Wilon
    Jun 30, 2014 at 16:49
  • Have you tried to reboot the SharePoint servers?
    – Max Melcher
    Jul 1, 2014 at 6:10
  • Yes, restart iis, server etc But nothing change, I'm thinking about restore search service from backup, but I'm not sure if it's ok with my case - probably search service corrupted?
    – Wilon
    Jul 1, 2014 at 8:29
  • 1
    It turned out that wasn't so bad, the farm CA for about 30 minutes has started, there was a problem with content databases, they didn't restore. Search was restored (service application, components) but also without databases but it was. Yesterday I restored virtual machines from snapshot because I was afraid of some hide errors which can happens in the weekend but next week I will try once more but know I try to recreate farm and and then restore only content ...
    – Wilon
    Jul 5, 2014 at 9:38

1 Answer 1

Reset to default
2

If you don't use eDiscovery, you can safely disable the "eDiscovery In-Place Hold Processing" Timer Job in Central Administration.

Navigate to Central Admin > Monitoring > Review job definitions and find the eDiscovery In-Place Hold Processing. Open it and disable it and the Event 6398 stops throwing errors at you.

enter image description here

Source: SharePoint event log- "The Execute method of job definition Microsoft.Office.RecordsManagement.Preservation.PreservationJobDefinition (ID) threw an exception."

Looks like it was from one of the timer jobs used for ediscovery. I think it's the eDiscovery In-Place Hold Processing timer job which runs hourly to start or remove site level holds. If your users doesn't utilize ediscovery, you can just disable this timer job scheduled run.

Improve this answer

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge that you have read and understand our privacy policy and code of conduct.

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