Question

Sharepoint-Sunny on Wed, 04 Jan 2017 13:32:41


Hi,


I am facing issue with scheduled search crawls in SP2013 farm.
Incremental or full crawls doesn't start if schedule.
But if run manually it works.

While troubleshoot I notice that the responsible job "Indexing Schedule Manager on <server>" on my AAP server is not running.

No relevant errors in Event logs, found below errors in ULS:
12/05/2016 12:00:25.65 OWSTIMER.EXE (Appserver:0x1840) 0x441C SharePoint Server Search Administration dj6t High not executing job Indexing Schedule Manager on <Appserver> because the service status (Disabled) or job status (Online) is not Online 120dbe9d-5cbb-405c-b31e-8b15a20f8299


12/14/2016 11:00:42.82 OWSTIMER.EXE (Appserver:0x2D8C) 0x50D0 SharePoint Foundation Timer aidhu Verbose Preparing to invoke non-pausable job name=(Indexing Schedule Manager on <Appserver>) , defintion=(02739759-4041-48a9-9fac-169f91389893) 3befc09d-5cc4-405c-b31e-8cdfbe33c249
 
I tried disabling & enabling timer job through UI & command, but no success.
Even restarted timer service on App server but issue persists.

Thanks for any help.

Best regards,

SharePoint-Sunny

Sponsored



Replies

Linda Zhang on Thu, 05 Jan 2017 03:39:20


Hi SharePoint-Sunny,

Please stop timer service and clean the configuration cache, then start the timer service and check if it works.

1. Stop the timer service.

2. Delete all the XML files in the config cache. There are loads of XML files that can be found in the folder “%SystemDrive%\ProgramData\Microsoft\SharePoint\Config\”. (Do not delete the folder and Cache.ini file).

3. Back up the Cache.ini file. Edit the “cache.ini” file, set the content to 1. This indicates that all cache settings need to be refreshed. Eventually this value gets automatically updated to another number when the cache is repopulated.

4. Start the timer service.

Information about Clearing SharePoint configuration cache, you could refer to the following article.

https://blogs.msdn.microsoft.com/jamesway/2011/05/23/sharepoint-2010-clearing-the-configuration-cache/

Best regards,

Linda Zhang

Sharepoint-Sunny on Fri, 06 Jan 2017 08:39:09


Hi Linda,

Thanks for your reply.

I have already cleared cache but it didn't worked.

Sorry I missed to mention that.

Is there anything else that can be done?

Thanks

Linda Zhang on Mon, 09 Jan 2017 02:24:00


Hi SharePoint-Sunny,

Please run the following command to check if the states of search components within the Search Service Application are 'Active'.

Get-SPEnterpriseSearchStatus -SearchApplication "<Search Service Application>"


And run the command below to see if status of the 'Indexing schedule manager on <server>' timer job is Online.

Get-SPTimerJob -Identity 'Indexing schedule manager on <server>'| Format-Table DisplayName,Id,LastRunTime,Status


Best regards,

Linda Zhang

Sharepoint-Sunny on Wed, 11 Jan 2017 09:43:27


Hi Linda,


I executed above commands.
First command showed all components are Active & second command showed below output,

Status: Online
LastRunTime: 01/11/2017 3:40 PM

From above output it seems that the job was ran today, however the crawls I scheduled for today never ran.

Let me know if anything has to be done further.

Thanks!




Linda Zhang on Tue, 17 Jan 2017 10:57:24


Hi Sharepoint-Sunny,

Have you performed an IISRESET? It will restart the entire web server.

Please do an IISRESET on the server to get all the SharePoint servers up to date on the latest farm information.

Best Regards,

Linda Zhang