Sharepoint 2016 FARM EVENT iD 6398 Solutions

SharePoint 2016 FARM 2 nodes

Node 1 WebFrontEndWithDistributedCache
Node 2 ApplicationWithSearch

On Node 1 Event 6398

Log Name:      Application
Source:        Microsoft-SharePoint Products-SharePoint Foundation
Date:          12/29/2019 6:10:30 AM
Event ID:      6398
Task Category: Timer
Level:         Critical
Keywords:      
User:          OUR\spfarm
Computer:      TGCS027-N1.our.network.tgcsnet.com
Description:
The Execute method of job definition Microsoft.SharePoint.Administration.SPTimerRecycleJobDefinition (ID 2c27cc40-cf3c-4041-b447-8102ade1d7dc) threw an exception. More information is included below.

The timer service was not recycled because the following jobs were still running: Search Topology Statistics - Search Service Application TGCSNET. (Correlation=ce37269f-f8bd-e0f1-3ea7-bd5fec126aff)
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-SharePoint Products-SharePoint Foundation" Guid="{6fb7e0cd-52e7-47dd-997a-241563931fc2}" />
    <EventID>6398</EventID>
    <Version>16</Version>
    <Level>1</Level>
    <Task>12</Task>
    <Opcode>0</Opcode>
    <Keywords>0x2000000000000000</Keywords>
    <TimeCreated SystemTime="2019-12-29T11:10:30.176573400Z" />
    <EventRecordID>42834</EventRecordID>
    <Correlation ActivityID="{ce37269f-f8bd-e0f1-3ea7-bd5fec126aff}" />
    <Execution ProcessID="12236" ThreadID="656" />
    <Channel>Application</Channel>
    <Computer>TGCS027-N1.our.network.tgcsnet.com</Computer>
    <Security UserID="S-1-5-21-3054588571-1341459584-784128302-3142" />
  </System>
  <EventData>
    <Data Name="string0">Microsoft.SharePoint.Administration.SPTimerRecycleJobDefinition</Data>
    <Data Name="string1">2c27cc40-cf3c-4041-b447-8102ade1d7dc</Data>
    <Data Name="string2">The timer service was not recycled because the following jobs were still running: Search Topology Statistics - Search Service Application TGCSNET. (Correlation=ce37269f-f8bd-e0f1-3ea7-bd5fec126aff)</Data>
  </EventData>
</Event>

Log Name:      Application
Source:        Microsoft-SharePoint Products-SharePoint Foundation
Date:          12/29/2019 6:10:30 AM
Event ID:      6398
Task Category: Timer
Level:         Critical
Keywords:      
User:          OUR\spfarm
Computer:      TGCS027-N1.our.network.tgcsnet.com
Description:
The Execute method of job definition Microsoft.SharePoint.Administration.SPTimerRecycleJobDefinition (ID 2c27cc40-cf3c-4041-b447-8102ade1d7dc) threw an exception. More information is included below.

The timer service was not recycled because the following jobs were still running: Search Topology Statistics - Search Service Application TGCSNET. (Correlation=ce37269f-f8bd-e0f1-3ea7-bd5fec126aff)
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-SharePoint Products-SharePoint Foundation" Guid="{6fb7e0cd-52e7-47dd-997a-241563931fc2}" />
    <EventID>6398</EventID>
    <Version>16</Version>
    <Level>1</Level>
    <Task>12</Task>
    <Opcode>0</Opcode>
    <Keywords>0x2000000000000000</Keywords>
    <TimeCreated SystemTime="2019-12-29T11:10:30.176573400Z" />
    <EventRecordID>42834</EventRecordID>
    <Correlation ActivityID="{ce37269f-f8bd-e0f1-3ea7-bd5fec126aff}" />
    <Execution ProcessID="12236" ThreadID="656" />
    <Channel>Application</Channel>
    <Computer>TGCS027-N1.our.network.tgcsnet.com</Computer>
    <Security UserID="S-1-5-21-3054588571-1341459584-784128302-3142" />
  </System>
  <EventData>
    <Data Name="string0">Microsoft.SharePoint.Administration.SPTimerRecycleJobDefinition</Data>
    <Data Name="string1">2c27cc40-cf3c-4041-b447-8102ade1d7dc</Data>
    <Data Name="string2">The timer service was not recycled because the following jobs were still running: Search Topology Statistics - Search Service Application TGCSNET. (Correlation=ce37269f-f8bd-e0f1-3ea7-bd5fec126aff)</Data>
  </EventData>
</Event>

Open in new window

NODE 2

Log Name:      Application
Source:        Microsoft-SharePoint Products-SharePoint Foundation
Date:          12/29/2019 7:15:39 AM
Event ID:      6398
Task Category: Timer
Level:         Critical
Keywords:      
User:          OUR\spfarm
Computer:      TGCS027-N2.our.network.tgcsnet.com
Description:
The Execute method of job definition Microsoft.Office.Server.UserProfiles.FeedCacheRepopulationJob (ID 6ed17471-6e82-4452-8f5e-06e1be07f47b) threw an exception. More information is included below.

Unexpected exception in FeedCacheService.IsRepopulationNeeded: Connection to the server terminated,check if the cache host(s) is running .. (Correlation=223c269f-08fb-e0f1-2cc5-905b8badfd66)
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-SharePoint Products-SharePoint Foundation" Guid="{6fb7e0cd-52e7-47dd-997a-241563931fc2}" />
    <EventID>6398</EventID>
    <Version>16</Version>
    <Level>1</Level>
    <Task>12</Task>
    <Opcode>0</Opcode>
    <Keywords>0x2000000000000000</Keywords>
    <TimeCreated SystemTime="2019-12-29T12:15:39.492941200Z" />
    <EventRecordID>43671</EventRecordID>
    <Correlation ActivityID="{223c269f-08fb-e0f1-2cc5-905b8badfd66}" />
    <Execution ProcessID="12680" ThreadID="13920" />
    <Channel>Application</Channel>
    <Computer>TGCS027-N2.our.network.tgcsnet.com</Computer>
    <Security UserID="S-1-5-21-3054588571-1341459584-784128302-3142" />
  </System>
  <EventData>
    <Data Name="string0">Microsoft.Office.Server.UserProfiles.FeedCacheRepopulationJob</Data>
    <Data Name="string1">6ed17471-6e82-4452-8f5e-06e1be07f47b</Data>
    <Data Name="string2">Unexpected exception in FeedCacheService.IsRepopulationNeeded: Connection to the server terminated,check if the cache host(s) is running .. (Correlation=223c269f-08fb-e0f1-2cc5-905b8badfd66)</Data>
  </EventData>
</Event>

Log Name:      Application
Source:        Microsoft-SharePoint Products-SharePoint Foundation
Date:          12/29/2019 6:30:01 AM
Event ID:      6398
Task Category: Timer
Level:         Critical
Keywords:      
User:          OUR\spfarm
Computer:      TGCS027-N2.our.network.tgcsnet.com
Description:
The Execute method of job definition Microsoft.Office.Server.UserProfiles.LMTRepopulationJob (ID e0957016-6fba-477d-99a3-ee2eeba29c1c) threw an exception. More information is included below.

Unexpected exception in FeedCacheService.IsRepopulationNeeded: Connection to the server terminated,check if the cache host(s) is running .. (Correlation=8639269f-d865-e0f1-2cc5-96b76ba484b8)
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Microsoft-SharePoint Products-SharePoint Foundation" Guid="{6fb7e0cd-52e7-47dd-997a-241563931fc2}" />
    <EventID>6398</EventID>
    <Version>16</Version>
    <Level>1</Level>
    <Task>12</Task>
    <Opcode>0</Opcode>
    <Keywords>0x2000000000000000</Keywords>
    <TimeCreated SystemTime="2019-12-29T11:30:01.005019600Z" />
    <EventRecordID>43669</EventRecordID>
    <Correlation ActivityID="{8639269f-d865-e0f1-2cc5-96b76ba484b8}" />
    <Execution ProcessID="12680" ThreadID="13972" />
    <Channel>Application</Channel>
    <Computer>TGCS027-N2.our.network.tgcsnet.com</Computer>
    <Security UserID="S-1-5-21-3054588571-1341459584-784128302-3142" />
  </System>
  <EventData>
    <Data Name="string0">Microsoft.Office.Server.UserProfiles.LMTRepopulationJob</Data>
    <Data Name="string1">e0957016-6fba-477d-99a3-ee2eeba29c1c</Data>
    <Data Name="string2">Unexpected exception in FeedCacheService.IsRepopulationNeeded: Connection to the server terminated,check if the cache host(s) is running .. (Correlation=8639269f-d865-e0f1-2cc5-96b76ba484b8)</Data>
  </EventData>
</Event>

Open in new window

View Solution Only

Walter CurtisSharePoint AED

Verified Expert

Distinguished Expert 2018

Commented: 2020-01-05

I have also been receiving this event for the last few months. In SharePoint, there are always errors. At least that is what I have seen over the last 15 years. It is always a challenge to determine which ones to spend time on and which ones are not a problem.

This article is a good article:

https://jwcooney.com/2017/08/23/sharepoint-addressing-seemingly-random-critical-error-event-6398/

I used the commands shown in the article and it seems to have corrected my 6398 errors, but It needs to be monitored for a few days before it can be said it is a fix.

Note: it took about 5 minutes for the cache host to come back online, so be patient. Here is code I used, use your server names.

Windows PowerShell
Copyright (C) 2014 Microsoft Corporation. All rights reserved.

PS C:\Windows\system32> add-pssnapin microsoft.sharepoint.powershell
PS C:\Windows\system32> Use-cachecluster
PS C:\Windows\system32> get-cachehost

HostName : CachePort Service Name Service Status Version Info
-------------------- ------------ -------------- ------------
WebFrontEndServerwithCacheRole.local:22233 AppFabricCachingService UP 3 [3,3][1,3]


PS C:\Windows\system32> get-cacheallowedclientaccounts
WSS_ADMIN_WPG
WSS_WPG

PS C:\Windows\system32> Remove-SPDistributedCAcheServiceInstance
PS C:\Windows\system32> Add-SPDistributedCAcheServiceInstance
PS C:\Windows\system32> Get-cachehost

HostName : CachePort Service Name Service Status Version Info
-------------------- ------------ -------------- ------------
PWebFrontEndServerwithCacheRole.local:22233 AppFabricCachingService UNKNOWN 3 [3,3][1,3]


PS C:\Windows\system32> Get-cachehost

HostName : CachePort Service Name Service Status Version Info
-------------------- ------------ -------------- ------------
WebFrontEndServerwithCacheRole.local:22233 AppFabricCachingService UNKNOWN 3 [3,3][1,3]


PS C:\Windows\system32> Get-cachehost

HostName : CachePort Service Name Service Status Version Info
-------------------- ------------ -------------- ------------
WebFrontEndServerwithCacheRole.local:22233 AppFabricCachingService UP 3 [3,3][1,3]


PS C:\Windows\system32>

Hope that helps...

Thomas GrassiSystems Administrator

Author

Walter,

Ran those commands and they all came back as your example. Had to wait for the AppFabricCacheingService to come up and it did.

I ran this on the WebFrontEndWithDistributedCache Role hopefully it clears the 6398 event

Will check in the AM after the timer service completes

Thanks

Tom

Commented: 2020-01-07

Home this worked for you.

Still getting the 6398

I changed the Timer Job for the Search to start at 30 minutes past the hour thinking it might be conflicting with the other timer.

Also ran this on NODE 2

Remove-SPDistributedCacheServiceInstance
Add-SPDistributedCacheServiceInstance

Will see in the AM

Commented: 2020-01-08

Walter

Looks like after changing the timer job start time to 30 past the hour the 6398 is NOT appearing on both Nodes

That's good news

Thank you for the suggestions.

It must have been conflicting with someone else.

Thanks for closing the question...

We help IT Professionals succeed at work.

Sharepoint 2016 FARM EVENT iD 6398

Premium Content

Premium Content