none
Application: Search Event ID 2159 - Unified Logging Service RRS feed

  • Question

  • I keep get a ton of these messages on my search server : Event 62 (Search) of severity 'Error' occurred 136 more time(s) and was suppressed in the event log

    I tried this solution but its still didn't work for me. 

    Solution was:

    http://www.sharepointdiary.com/2015/05/reset-search-index-in-sharepoint-2013-using-powershell.html 

    Basically it appears the search index partition becomes corrupted. In this event the link becomes dead, the following steps resolved the issue:

    1. Stop the Timer Service
    2. Clear the configuration cache - Find in %ProgramData%Microsoft\SharePoint\Config the folder where the file cache.ini exists
    3. Delete every file from this folder EXCEPT cache.ini
    4. Open cache.ini, delete the content and put '1' (without the quotes) in it and save the file
    5. Restart the Timer Service
    6. Index reset
    7. Full crawl

    The Error am getting from task manager is below:

    - System 

      - Provider 

       [ Name]  Microsoft-Office Server-Search 
       [ Guid]  {6AA8A41D-229D-42E8-A45E-49DD4F7F6E09} 
     
       EventID 2159 
     
       Version 16 
     
       Level 2 
     
       Task 36 
     
       Opcode 0 
     
       Keywords 0x800000000000000 
     
      - TimeCreated 

       [ SystemTime]  2019-07-15T16:57:14.298128500Z 
     
       EventRecordID 205239 
     
       Correlation 
     
      - Execution 

       [ ProcessID]  4264 
       [ ThreadID]  4360 
     
       Channel Application 
     
       Computer myserver.domain.org
     
      - Security 

       [ UserID]  S-1-5-21-269429255-930636928-310601177-85786 
     

    - EventData 

      int0 62 
      string1 Search 
      int2 136 

    Any assistance will be greatly appreciated. 

    Monday, July 15, 2019 5:04 PM

Answers

  • FINALLY !!!  I was able to resolve this issue by clearing the cache and then deleting the Search service on my environment.  Before creating the the search service again, I stopped the Search Host Controller and Search 16. I ran the Powershell script to rebuild search and restarted the services again (Search Host Controller and Search 16).  So far i have not seen the error in the event viewer.  
    • Marked as answer by Azizmod23 Wednesday, July 31, 2019 7:07 PM
    Wednesday, July 31, 2019 7:07 PM

All replies

  • Hi Azizmod23,

    The above error is logged for the Unified Logging Service. Something to check for:

    • See if Named Pipes is enabled in SQL configuration. If it is, then proceed to the step below:
    • If not, then enable Named Pipes and once that is done restart the services.

    Open up SQL Server Management Studio and create a new query. Run the following:

    USE master
    GO
    GRANT VIEW SERVER STATE TO “Domain\Timer_Service_User”
    GO

    Once the query has completed, close SQL Server Management Studio and check the event viewer. The errors should be gone.

    Thanks & Regards,


    sharath aluri

    Tuesday, July 16, 2019 1:15 AM
  • Hi Azizmod23,

    If the reply is helpful to you, you could mark the reply as answer. Thanks for your understanding.

    Best regards,

    Sara Fan

    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    SharePoint Server 2019 has been released, you can click here to download it.
    Click here to learn new features. Visit the dedicated forum to share, explore and talk to experts about SharePoint Server 2019.

    Tuesday, July 16, 2019 4:49 AM
    Moderator
  • Hi Sharath,

    Pipes has been enabled and services restarted.  I ran the sql query but am getting the same error.  I seems to be happening at a 5 min interval. 





    • Edited by Azizmod23 Tuesday, July 16, 2019 6:50 PM
    Tuesday, July 16, 2019 6:47 PM
  • did you grant the farm account “VIEW SERVER STATE” under the SQL Server properties ?

    Thanks & Regards,


    sharath aluri

    Tuesday, July 16, 2019 7:13 PM
  • Yes I did. 
    Tuesday, July 16, 2019 7:47 PM
  • Try Clearing config cache from the below script. still issue remains same you may have to reboot the server.

    https://github.com/DwayneSelsig/spcachecleaner/blob/master/SPCacheCleaner.ps1

    Thanks & Regards,


    sharath aluri

    Tuesday, July 16, 2019 9:57 PM
  • Hi Azizmod23, 

    To troubleshoot the issue, check things below:

    1. Create a new search service application to check if the same issue will occur.

    2. Check the details about the issue in ULS log.

    Best regards,

    Sara Fan


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    SharePoint Server 2019 has been released, you can click here to download it.
    Click here to learn new features. Visit the dedicated forum to share, explore and talk to experts about SharePoint Server 2019.

    Wednesday, July 17, 2019 9:02 AM
    Moderator
  • Hi, 

    I deleted search and recreated it all over again.  This worked for a few mins but the error came back again. I also cleared the index and rebuilt everything up again.  I soon as i started the crawler, the error came back. 

    Am working clearing the farm cache now.

    Wednesday, July 17, 2019 3:16 PM
  • I ran the script and rebooted the server and still the same error. 
    Wednesday, July 17, 2019 3:29 PM
  • Hi Azizmod23, 

    To troubleshoot the issue, you could run SharePoint 2016 products configuration wizard.

    And then check the details about the issue in ULS log.

    Best regards,

    Sara Fan


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    SharePoint Server 2019 has been released, you can click here to download it.
    Click here to learn new features. Visit the dedicated forum to share, explore and talk to experts about SharePoint Server 2019.

    Thursday, July 18, 2019 8:56 AM
    Moderator
  • This is the errors i found in the logs

    07/18/2019 09:39:29.74 NodeRunnerContent1-a26fc93d-83f (0x10E0) 0x3968 Search                        Document Parsing              ai3n0 Monitorable SandboxWorker[5]: Parser server failed to start.  Exception: System.ComponentModel.Win32Exception (0x80004005): Process needs SeAssignPrimaryTokenPrivilege. Cannot continue.     at Microsoft.Ceres.Common.Tools.Sandbox.SandBoxInterop.StartProcess(SandBoxedProcessArguments sbpArgs, Boolean fSuspended, ProcessInformation* psandBoxProcessInfo)     at Microsoft.Ceres.Common.Tools.Sandbox.SandBoxedProcess.StartProcessSuspended(SandBoxedProcessArguments sbpArgs)     at Microsoft.Ceres.Common.Tools.Sandbox.SandboxLauncher.Launcher.Start(String application, String arguments, Int32 memoryLimitMegabytes, Boolean suspended, SecurityIdentifier uniqueSidToAllow, Boolean loopForJobMessages, IThreadManager threadManager)     at Microsoft.Ceres.DocParsing.Runtime.Core.Sandbox.SandboxWorker.StartServer()   ... fa4ad16d-1836-46b8-9a24-c028cb5b23ec
    07/18/2019 09:39:29.74* NodeRunnerContent1-a26fc93d-83f (0x10E0) 0x3968 Search                        Document Parsing              ai3n0 Monitorable ...  at Microsoft.Ceres.DocParsing.Runtime.Core.Sandbox.SandboxWorker.StartRetry() fa4ad16d-1836-46b8-9a24-c028cb5b23ec
    07/18/2019 09:39:29.74 NodeRunnerContent1-a26fc93d-83f (0x10E0) 0x3968 Search                        Document Parsing              ai3nu Monitorable SandboxWorker[5]: The parser server failed to start, will try to restart. Retry 3 of 4. fa4ad16d-1836-46b8-9a24-c028cb5b23ec
    07/18/2019 09:39:29.77 NodeRunnerContent1-a26fc93d-83f (0x10E0) 0x1990 Search                        Document Parsing              ai3n0 Monitorable SandboxWorker[1]: Parser server failed to start.  Exception: System.ComponentModel.Win32Exception (0x80004005): Process needs SeAssignPrimaryTokenPrivilege. Cannot continue.     at Microsoft.Ceres.Common.Tools.Sandbox.SandBoxInterop.StartProcess(SandBoxedProcessArguments sbpArgs, Boolean fSuspended, ProcessInformation* psandBoxProcessInfo)     at Microsoft.Ceres.Common.Tools.Sandbox.SandBoxedProcess.StartProcessSuspended(SandBoxedProcessArguments sbpArgs)     at Microsoft.Ceres.Common.Tools.Sandbox.SandboxLauncher.Launcher.Start(String application, String arguments, Int32 memoryLimitMegabytes, Boolean suspended, SecurityIdentifier uniqueSidToAllow, Boolean loopForJobMessages, IThreadManager threadManager)     at Microsoft.Ceres.DocParsing.Runtime.Core.Sandbox.SandboxWorker.StartServer()   ... a2f3c7e1-536a-44dd-ae0e-ec51fd5e64cd
    07/18/2019 09:39:29.77* NodeRunnerContent1-a26fc93d-83f (0x10E0) 0x1990 Search                        Document Parsing              ai3n0 Monitorable ...  at Microsoft.Ceres.DocParsing.Runtime.Core.Sandbox.SandboxWorker.StartRetry() a2f3c7e1-536a-44dd-ae0e-ec51fd5e64cd
    07/18/2019 09:39:29.77 NodeRunnerContent1-a26fc93d-83f (0x10E0) 0x1990 Search                        Document Parsing              ai3nu Monitorable SandboxWorker[1]: The parser server failed to start, will try to restart. Retry 3 of 4. a2f3c7e1-536a-44dd-ae0e-ec51fd5e64cd
    07/18/2019 09:39:29.93 OWSTIMER.EXE (0x337C)                    0x4B8C SharePoint Foundation          Monitoring                    b4ly High    Leaving Monitored Scope: (Performance Inspect Scope) Execution Time=187.675319069882; CPU Milliseconds=0; SQL Query Count=0; Parent=Task (SPServer Status Inspector Scope) c077f19e-3215-20e5-ca40-62139b15458b
    07/18/2019 09:39:29.98 NodeRunnerIndex4-a26fc93d-83f4- (0x1170) 0x4270 Search                        Search Component              amtqt Medium  Microsoft.Ceres.SearchCore.Indexes.FastServerIndex.Merger.GlobalMergeScheduler: PeriodicCheck has started (5393).
    07/18/2019 09:39:29.98 NodeRunnerIndex4-a26fc93d-83f4- (0x1170) 0x4270 Search                        Search Component              a1e2w Medium  Microsoft.Ceres.SearchCore.Indexes.FastServerIndex.Merger.GlobalMergeScheduler: Ongoing merges: {}
    07/18/2019 09:39:30.09 OWSTIMER.EXE (0x337C)                    0x4BD4 SharePoint Foundation          Monitoring                    nasq Medium  Entering Monitored Scope (RefreshCache: Refreshing the cache). Parent=None 7b43ef7e-f6aa-43f2-bec9-003ee49bf853
    07/18/2019 09:39:30.09 OWSTIMER.EXE (0x337C)                    0x26C0 SharePoint Foundation          Timer                          apm5x Medium  Successfully started timer job {BEB7EF09-10B0-46C7-B22F-313110BD830E} [Application Server Administration Service Timer Job] in store for service {9557DF65-CEFA-4C12-8765-D31F3E11829E}, vserver {00000000-0000-0000-0000-000000000000}, current target 0 10b2e03b-cb96-41ff-b91e-10c238a790c1
    07/18/2019 09:39:30.09 OWSTIMER.EXE (0x337C)                    0x26C0 SharePoint Foundation          Monitoring                    nasq Medium  Entering Monitored Scope (Timer Job job-application-server-admin-service). Parent=None 10b2e03b-cb96-41ff-b91e-10c238a790c1
    07/18/2019 09:39:30.09 OWSTIMER.EXE (0x337C)                    0x26C0 SharePoint Foundation          Logging Correlation Data      xmnv Medium  Name=Timer Job job-application-server-admin-service c077f19e-a22a-20e5-ca40-69b9e8fd3cd2
    07/18/2019 09:39:30.09 OWSTIMER.EXE (0x337C)                    0x26C0 SharePoint Server Search      Administration                dkd5 High    synchronizing search service instance c077f19e-a22a-20e5-ca40-69b9e8fd3cd2
    07/18/2019 09:39:30.09 OWSTIMER.EXE (0x337C)                    0x26C0 SharePoint Server Search      Administration                eff0 High    synchronizing search data access service instance c077f19e-a22a-20e5-ca40-69b9e8fd3cd2
    07/18/2019 09:39:30.09 OWSTIMER.EXE (0x337C)                    0x4BD4 SharePoint Foundation          Config Cache                  umbj Medium  Deserializing the type named Microsoft.Office.Server.Search.Administration.SearchServiceApplicationMonitoring, Microsoft.Office.Server.Search, Version=16.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c and with id 2d7f14a4-289f-47bf-bd65-5a933fc13ea5. 7b43ef7e-f6aa-43f2-bec9-003ee49bf853
    07/18/2019 09:39:30.09 OWSTIMER.EXE (0x337C)                    0x4BD4 SharePoint Foundation          Config Cache                  a0ic2 Medium  Refreshed SPPersistedObject with Name Monitoring_7F19A5D194F942e6A9856FCFD6EE6F63, Id 568a0473-96ad-4802-b2c3-ace03b16356b, Parent a26fc93d-83f4-4e01-9439-6c3b8b565437, Version 4152786. Last update info: [User: [Account] Process:OWSTIMER (13180) Machine:Server Time:July 18, 2019 09:39:16.0000 Stack trace (Thread [22] CorrelationId [bc77f19e-b2bc-20e5-ca40-6ba2fa4489df]): ] 7b43ef7e-f6aa-43f2-bec9-003ee49bf853
    07/18/2019 09:39:30.09 OWSTIMER.EXE (0x337C)                    0x4BD4 SharePoint Foundation          Topology                      a3zho Medium  LogSPPersistedObjectStatistic - operation duration too low to log. Duration 5ms. 7b43ef7e-f6aa-43f2-bec9-003ee49bf853
    07/18/2019 09:39:30.09 OWSTIMER.EXE (0x337C)                    0x4BD4 SharePoint Foundation          Config DB                      a4cn4 Medium  RefreshCache - Number of objects updated 1. 7b43ef7e-f6aa-43f2-bec9-003ee49bf853
    07/18/2019 09:39:30.09 OWSTIMER.EXE (0x337C)                    0x4BD4 SharePoint Foundation          Monitoring                    b4ly Medium  Leaving Monitored Scope: (RefreshCache: Refreshing the cache) Execution Time=5.53596895694844; CPU Milliseconds=1; SQL Query Count=1; Parent=None 7b43ef7e-f6aa-43f2-bec9-003ee49bf853
    07/18/2019 09:39:30.09 OWSTIMER.EXE (0x337C)                    0x4BD4 SharePoint Foundation          Monitoring                    nasq Medium  Entering Monitored Scope (Refreshing object collection file cache.). Parent=None 7b43ef7e-f6aa-43f2-bec9-003ee49bf853
    07/18/2019 09:39:30.10 OWSTIMER.EXE (0x337C)                    0x2910 SharePoint Foundation          Timer                          apm5x Medium  Successfully started timer job {F0CEB2D1-20A6-4DAE-907C-1931F361455E} [Diagnostic Data Provider: SQL Blocking Queries] in store for service {F8125BA7-C8AF-4022-AC3D-0A355503E452}, vserver {00000000-0000-0000-0000-000000000000}, current target 0 bcb9412d-0c88-45ce-9977-66f7ab37d8ac
    07/18/2019 09:39:30.10 OWSTIMER.EXE (0x337C)                    0x2910 SharePoint Foundation          Monitoring                    nasq Medium  Entering Monitored Scope (Timer Job job-diagnostics-blocking-query-provider). Parent=None bcb9412d-0c88-45ce-9977-66f7ab37d8ac
    07/18/2019 09:39:30.10 OWSTIMER.EXE (0x337C)                    0x2910 SharePoint Foundation          Logging Correlation Data      xmnv Medium  Name=Timer Job job-diagnostics-blocking-query-provider c077f19e-a22b-20e5-ca40-605be097b085
    07/18/2019 09:39:30.12 OWSTIMER.EXE (0x337C)                    0x2910 SharePoint Foundation          Timer                          an9i8 Medium  Completed processing of timer job [job-diagnostics-blocking-query-provider] with lock type [Job] against target instance [f0ceb2d1-20a6-4dae-907c-1931f361455e] [SPDiagnosticsBlockingQueryProvider Name=job-diagnostics-blocking-query-provider]. Start time: [07/18/2019 13:39:30]. Duration: [00:00:00.0156269]. Status result: [Succeeded]. Status ressage (if any): []. c077f19e-a22b-20e5-ca40-605be097b085
    07/18/2019 09:39:30.12 OWSTIMER.EXE (0x337C)                    0x2910 SharePoint Foundation          Monitoring                    b4ly Medium  Leaving Monitored Scope: (Timer Job job-diagnostics-blocking-query-provider) Execution Time=18.0122753031461; CPU Milliseconds=3; SQL Query Count=6; Parent=None c077f19e-a22b-20e5-ca40-605be097b085
    07/18/2019 09:39:30.12 OWSTIMER.EXE (0x337C)                    0x2910 SharePoint Foundation          Timer                          apm55 Medium  Successfully completed with result 2 timer running job {F0CEB2D1-20A6-4DAE-907C-1931F361455E} for service {F8125BA7-C8AF-4022-AC3D-0A355503E452}, webapp {00000000-0000-0000-0000-000000000000} bcb9412d-0c88-45ce-9977-66f7ab37d8ac
    07/18/2019 09:39:30.24 OWSTIMER.EXE (0x337C)                    0x317C SharePoint Foundation          Monitoring                    aeh57 Medium  Sql Ring buffer status eventsPerSec = ,processingTime=0,totalEventsProcessed=0,eventCount=0,droppedCount=0,memoryUsed=0
    07/18/2019 09:39:30.29 OWSTIMER.EXE (0x337C)                    0x3C2C SharePoint Foundation          Monitoring                    b4ly High    Leaving Monitored Scope: (Performance Inspect Scope) Execution Time=187.535915877577; CPU Milliseconds=0; SQL Query Count=0; Parent=Task (SPServer Status Inspector Scope) c077f19e-a22b-20e5-ca40-60d2799960b3
    07/18/2019 09:39:30.40 OWSTIMER.EXE (0x337C)                    0x4BD4 SharePoint Foundation          Config Cache                  a5wmi Medium  SPPersistedObjectCollectionCache.RefreshCache: Processed 153 collection files. 7b43ef7e-f6aa-43f2-bec9-003ee49bf853
    07/18/2019 09:39:30.40 OWSTIMER.EXE (0x337C)                    0x4BD4 SharePoint Foundation          Monitoring                    b4ly High    Leaving Monitored Scope: (Refreshing object collection file cache.) Execution Time=303.559460769455; CPU Milliseconds=79; SQL Query Count=153; Parent=None 7b43ef7e-f6aa-43f2-bec9-003ee49bf853
    07/18/2019 09:39:30.40 OWSTIMER.EXE (0x337C)                    0x4BD4 SharePoint Foundation          Monitoring                    nass High    ____SQL Query Count=153 7b43ef7e-f6aa-43f2-bec9-003ee49bf853
    07/18/2019 09:39:30.40 OWSTIMER.EXE (0x337C)                    0x4BD4 SharePoint Foundation          Monitoring                    arm3c High    ____CPU Milliseconds=79 7b43ef7e-f6aa-43f2-bec9-003ee49bf853
    07/18/2019 09:39:30.40 OWSTIMER.EXE (0x337C)                    0x4BD4 SharePoint Foundation          Monitoring                    nass High    ____Execution Time=303.559460769455 7b43ef7e-f6aa-43f2-bec9-003ee49bf853
    07/18/2019 09:39:30.43 wsstracing.exe (0x0878)                  0x42F4 SharePoint Foundation          Tracing Controller Service    8094 Warning Trace logs are reaching to the configured storage limit (10). Please increase the maximum storage settings. Otherwise, older files will be deleted once the limit is reached.
    07/18/2019 09:39:30.45 NodeRunner.exe (0x11B0)                  0x1F54 SharePoint Foundation          Topology                      atega Medium  1 file changes detected
    07/18/2019 09:39:30.45 NodeRunner.exe (0x11B0)                  0x1F54 SharePoint Foundation          Monitoring                    nasq Medium  Entering Monitored Scope (Firing DelayedFileSystemWatcher notifications). Parent=None
    07/18/2019 09:39:30.45 NodeRunner.exe (0x11B0)                  0x1F54 SharePoint Foundation          Config Cache                  barmt Medium  OnBulkChanged: While processing bulk notifications.
    07/18/2019 09:39:30.45 NodeRunner.exe (0x11B0)                  0x1F54 SharePoint Foundation          Config Cache                  a3c25 Medium  Entering Monitored Scope (FetchObjectFromFileSystem: Fetching object [568a0473-96ad-4802-b2c3-ace03b16356b], IdFieldsOnly = [True].). Parent=Firing DelayedFileSystemWatcher notifications
    07/18/2019 09:39:30.45 NodeRunner.exe (0x11B0)                  0x1F54 SharePoint Foundation          Config Cache                  a3c25 Medium  Leaving Monitored Scope: (FetchObjectFromFileSystem: Fetching object [568a0473-96ad-4802-b2c3-ace03b16356b], IdFieldsOnly = [True].) Execution Time=0.493638157922306; CPU Milliseconds=0; SQL Query Count=0; Parent=Firing DelayedFileSystemWatcher notifications
    07/18/2019 09:39:30.45 NodeRunner.exe (0x11B0)                  0x1F54 SharePoint Foundation          Config Cache                  barmw Medium  OnBulkChanged: Change Map has been built with 1 items.
    07/18/2019 09:39:30.45 NodeRunner.exe (0x11B0)                  0x1F54 SharePoint Foundation          Config Cache                  a3c25 Medium  Entering Monitored Scope (FetchObjectFromFileSystem: Fetching object [568a0473-96ad-4802-b2c3-ace03b16356b], IdFieldsOnly = [False].). Parent=Firing DelayedFileSystemWatcher notifications
    07/18/2019 09:39:30.45 NodeRunner.exe (0x11B0)                  0x1F54 SharePoint Foundation          Config Cache                  umbj Medium  Deserializing the type named Microsoft.Office.Server.Search.Administration.SearchServiceApplicationMonitoring, Microsoft.Office.Server.Search, Version=16.0.0.0, Culture=neutral, PublicKeyToken=71e9bce111e9429c and with id 2d7f14a4-289f-47bf-bd65-5a933fc13ea5.
    07/18/2019 09:39:30.45 NodeRunner.exe (0x11B0)                  0x1F54 SharePoint Foundation          Config Cache                  a0ic2 Medium  Refreshed SPPersistedObject with Name Monitoring_7F19A5D194F942e6A9856FCFD6EE6F63, Id 568a0473-96ad-4802-b2c3-ace03b16356b, Parent a26fc93d-83f4-4e01-9439-6c3b8b565437, Version 4152786. Last update info: [User: [Account] Process:OWSTIMER (13180) Machine:Server Time:July 18, 2019 09:39:16.0000 Stack trace (Thread [22] CorrelationId [bc77f19e-b2bc-20e5-ca40-6ba2fa4489df]): ]
    07/18/2019 09:39:30.45 NodeRunner.exe (0x11B0)                  0x1F54 SharePoint Foundation          Config Cache                  a3c25 Medium  Leaving Monitored Scope: (FetchObjectFromFileSystem: Fetching object [568a0473-96ad-4802-b2c3-ace03b16356b], IdFieldsOnly = [False].) Execution Time=0.5710921360117; CPU Milliseconds=0; SQL Query Count=0; Parent=Firing DelayedFileSystemWatcher notifications
    07/18/2019 09:39:30.45 NodeRunner.exe (0x11B0)                  0x1F54 SharePoint Foundation          Topology                      a3zho Medium  LogSPPersistedObjectStatistic - operation duration too low to log. Duration 0ms.
    07/18/2019 09:39:30.45 NodeRunner.exe (0x11B0)                  0x1F54 SharePoint Foundation          Monitoring                    nasq Medium  Entering Monitored Scope (Invalidating object collection file cache according to change type). Parent=Firing DelayedFileSystemWatcher notifications
    07/18/2019 09:39:30.45 NodeRunner.exe (0x11B0)                  0x1F54 SharePoint Foundation          Monitoring                    nasq Medium  Entering Monitored Scope (Updating child collection file cache.). Parent=Invalidating object collection file cache according to change type
    07/18/2019 09:39:30.45 NodeRunner.exe (0x11B0)                  0x1F54 SharePoint Foundation          Monitoring                    b4ly Medium  Leaving Monitored Scope: (Updating child collection file cache.) Execution Time=1.10558744197936; CPU Milliseconds=0; SQL Query Count=1; Parent=Invalidating object collection file cache according to change type
    07/18/2019 09:39:30.45 NodeRunner.exe (0x11B0)                  0x1F54 SharePoint Foundation          Monitoring                    nasq Medium  Entering Monitored Scope (Updating dependency collection file cache.). Parent=Invalidating object collection file cache according to change type
    07/18/2019 09:39:30.45 NodeRunner.exe (0x11B0)                  0x1F54 SharePoint Foundation          Monitoring                    b4ly Medium  Leaving Monitored Scope: (Updating dependency collection file cache.) Execution Time=0.00942857262585049; CPU Milliseconds=0; SQL Query Count=0; Parent=Invalidating object collection file cache according to change type
    07/18/2019 09:39:30.45 NodeRunner.exe (0x11B0)                  0x1F54 SharePoint Foundation          Monitoring                    b4ly Medium  Leaving Monitored Scope: (Invalidating object collection file cache according to change type) Execution Time=1.30582238804094; CPU Milliseconds=0; SQL Query Count=1; Parent=Firing DelayedFileSystemWatcher notifications
    07/18/2019 09:39:30.45 NodeRunner.exe (0x11B0)                  0x1F54 SharePoint Foundation          Config Cache                  barmz Medium  OnBulkChanged: Notifications have been sent for 1 items.
    07/18/2019 09:39:30.45 NodeRunner.exe (0x11B0)                  0x1F54 SharePoint Foundation          Monitoring                    b4ly Medium  Leaving Monitored Scope: (Firing DelayedFileSystemWatcher notifications) Execution Time=3.0607241981872; CPU Milliseconds=2; SQL Query Count=1; Parent=None
    07/18/2019 09:39:30.51 NodeRunnerIndex1-a26fc93d-83f4- (0x1140) 0x2FA0 Search                        Search Component              amtqt Medium  Microsoft.Ceres.SearchCore.Indexes.FastServerIndex.Merger.GlobalMergeScheduler: PeriodicCheck has started (5393).
    07/18/2019 09:39:30.51 NodeRunnerIndex1-a26fc93d-83f4- (0x1140) 0x2FA0 Search                        Search Component              a1e2w Medium  Microsoft.Ceres.SearchCore.Indexes.FastServerIndex.Merger.GlobalMergeScheduler: Ongoing merges: {}
    07/18/2019 09:39:30.51 NodeRunnerContent1-a26fc93d-83f (0x10E0) 0x3968 Search                        Document Parsing              ai3n0 Monitorable SandboxWorker[5]: Parser server failed to start.  Exception: System.ComponentModel.Win32Exception (0x80004005): Process needs SeAssignPrimaryTokenPrivilege. Cannot continue.     at Microsoft.Ceres.Common.Tools.Sandbox.SandBoxInterop.StartProcess(SandBoxedProcessArguments sbpArgs, Boolean fSuspended, ProcessInformation* psandBoxProcessInfo)     at Microsoft.Ceres.Common.Tools.Sandbox.SandBoxedProcess.StartProcessSuspended(SandBoxedProcessArguments sbpArgs)     at Microsoft.Ceres.Common.Tools.Sandbox.SandboxLauncher.Launcher.Start(String application, String arguments, Int32 memoryLimitMegabytes, Boolean suspended, SecurityIdentifier uniqueSidToAllow, Boolean loopForJobMessages, IThreadManager threadManager)     at Microsoft.Ceres.DocParsing.Runtime.Core.Sandbox.SandboxWorker.StartServer()   ... fa4ad16d-1836-46b8-9a24-c028cb5b23ec
    07/18/2019 09:39:30.51* NodeRunnerContent1-a26fc93d-83f (0x10E0) 0x3968 Search                        Document Parsing              ai3n0 Monitorable ...  at Microsoft.Ceres.DocParsing.Runtime.Core.Sandbox.SandboxWorker.StartRetry() fa4ad16d-1836-46b8-9a24-c028cb5b23ec
    07/18/2019 09:39:30.51 NodeRunnerContent1-a26fc93d-83f (0x10E0) 0x3968 Search                        Document Parsing              ai3nu Monitorable SandboxWorker[5]: The parser server failed to start, will try to restart. Retry 4 of 4. fa4ad16d-1836-46b8-9a24-c028cb5b23ec

                             
    Thursday, July 18, 2019 1:55 PM
  • I did't find anything in the logs with the above related issue of yours.

    Thanks & Regards,


    sharath aluri



    Thursday, July 18, 2019 8:17 PM
  • Hi Azizmod23, 

    To troubleshoot the issue, you could grant the account with SeAssignPrimaryTokenPrivilege on the local SharePoint server.

    Go to the SharePoint server->click Start->type “secpol.msc”-> Security Settings->Local Policies->User Rights Assignment->find “Replace a process-level token”->right click “Replace a process-level token”->select “properties”->add the account who run the search.


    For more detailed information, refer to the article below.

    SharePoint Hung Crawl – Sandbox worker pool is closed.

    https://blogs.technet.microsoft.com/sharepointrecipes/2015/06/17/sharepoint-hung-crawl-sandbox-worker-pool-is-closed/

    Best regards,

    Sara Fan


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    SharePoint Server 2019 has been released, you can click here to download it.
    Click here to learn new features. Visit the dedicated forum to share, explore and talk to experts about SharePoint Server 2019.

    Friday, July 19, 2019 8:19 AM
    Moderator
  • Hi Azizmod23, 

    How is everything going?

    Is there anything update about this issue?

    If the reply is helpful to you, you could mark the reply as answer. Thanks for your understanding.

    Best regards,

    Sara Fan

    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    SharePoint Server 2019 has been released, you can click here to download it.
    Click here to learn new features. Visit the dedicated forum to share, explore and talk to experts about SharePoint Server 2019.

    Tuesday, July 23, 2019 1:55 AM
    Moderator
  • We implemented the solution but to no avail.  The error is back every 5 mins. 
    Wednesday, July 24, 2019 6:02 PM
  • Hi Azizmod23, 

    You could repair the SharePoint products. Go to start->control panel->programs->right click “SharePoint 2016” and select change->click Repair.

    And if the issue still exists, you could consider re-installing SharePoint 2016.

    Best regards,

    Sara Fan


    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    SharePoint Server 2019 has been released, you can click here to download it.
    Click here to learn new features. Visit the dedicated forum to share, explore and talk to experts about SharePoint Server 2019.


    Thursday, July 25, 2019 8:55 AM
    Moderator
  • This did not help either.  I think my only option right now is un-install everything and begin from scratch.  This is only happening in one environment.  All the rest were configured the same and do not have the same issue.  Thank you for your assistance. 
    Monday, July 29, 2019 1:10 PM

  • Hi Azizmod23, 

    If the reply is helpful to you, you could mark the reply as answer. Thanks for your understanding.

    Best regards,

    Sara Fan

    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    SharePoint Server 2019 has been released, you can click here to download it.
    Click here to learn new features. Visit the dedicated forum to share, explore and talk to experts about SharePoint Server 2019.

    Tuesday, July 30, 2019 1:28 AM
    Moderator
  • FINALLY !!!  I was able to resolve this issue by clearing the cache and then deleting the Search service on my environment.  Before creating the the search service again, I stopped the Search Host Controller and Search 16. I ran the Powershell script to rebuild search and restarted the services again (Search Host Controller and Search 16).  So far i have not seen the error in the event viewer.  
    • Marked as answer by Azizmod23 Wednesday, July 31, 2019 7:07 PM
    Wednesday, July 31, 2019 7:07 PM
  • Hi Azizmod23, 

    It is very happy that you have resolved your problem.

    Thank you for your sharing and it will help others have the same issue.

    Best regards,

    Sara Fan

    Please remember to mark the replies as answers if they helped. If you have feedback for TechNet Subscriber Support, contact tnmff@microsoft.com.

    SharePoint Server 2019 has been released, you can click here to download it.
    Click here to learn new features. Visit the dedicated forum to share, explore and talk to experts about SharePoint Server 2019.

    Thursday, August 1, 2019 1:19 AM
    Moderator