Repository Service Is Restarted Every 5 Minutes Or Regularly

This article explains that why Repository Service is restarted every 5 minutes or regularly with workaround.

Symptoms:
1. Qlik Sense June 2018 or November 2018 or February 2019 after upgrading
2. Repository Service is restarted every 5 minutes or regularly.
3. There are same error messages in Repository and Event logs
4. Clients may receive error "You cannot access Qlik Sense because you have no access pass" every 5-10 minutes of activity

Repository log:
...
  33 2018-11-29 09:53:12 20181129T095312.429+0100 ERROR eastwood-booztx-com System.Repository.Repository.QRSService 10 c0005f6f-b03d-46f8-8e85-3c6abeac394a EASTWOOD-BOOZTX\qlik Unhandled exception: Instance 'Repository' does not exist in the specified Category.↓System.InvalidOperationException: Instance 'Repository' does not exist in the specified Category.↵↓ at System.Diagnostics.CounterDefinitionSample.GetInstanceValue(String instanceName)↵↓ at System.Diagnostics.PerformanceCounter.NextSample()↵↓ at System.Diagnostics.PerformanceCounter.NextValue()↵↓ at Repository.Core.Monitoring.PerformanceInfo.<.ctor>b__5_4()↵↓ at Repository.Core.Monitoring.PerformanceInfo.GetValue(String counterName)↵↓ at Repository.Core.Monitoring.PerformanceLogData..ctor(IPerformanceInfo performanceInfo)↵↓ at Repository.Core.Monitoring.PerformanceLogger.Log()↵↓ at System.Action.Invoke()↵↓ at Qlik.Sense.Common.Triggers.TriggerBase.TriggerInternal()↵↓ at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)↵↓ at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)↵↓ at System.Threading.TimerQueueTimer.CallCallback()↵↓ at System.Threading.TimerQueueTimer.Fire()↵↓ at System.Threading.TimerQueue.FireNextTimers() c0005f6f-b03d-46f8-8e85-3c6abeac394a 
...

Event log
Faulting application name: Repository.exe, version: 23.11.2.0, time stamp: 0x5be0344c

Faulting module name: unknown, version: 0.0.0.0, time stamp: 0x00000000
Exception code: 0x80131623
Fault offset: 0x00007fff1f2dd388
Faulting process id: 0x34c0
Faulting application start time: 0x01d487c6aa2fca4a
Faulting application path: C:\Program Files\Qlik\Sense31\Repository\Repository.exe
Faulting module path: unknown
Report Id: a4b2b130-f3ba-11e8-80e4-3ca82a1ee127
Faulting package full name:
Faulting package-relative application ID:

and

Application: Repository.exe
Framework Version: v4.0.30319
Description: The application requested process termination through System.Environment.FailFast(string message).
Message: Unhandled exception: Instance 'Repository' does not exist in the specified Category.
System.InvalidOperationException: Instance 'Repository' does not exist in the specified Category.
at System.Diagnostics.CounterDefinitionSample.GetInstanceValue(String instanceName)
at System.Diagnostics.PerformanceCounter.NextSample()
at System.Diagnostics.PerformanceCounter.NextValue()
at Repository.Core.Monitoring.PerformanceInfo.<.ctor>b__5_4()
at Repository.Core.Monitoring.PerformanceInfo.GetValue(String counterName)
at Repository.Core.Monitoring.PerformanceLogData..ctor(IPerformanceInfo performanceInfo)
at Repository.Core.Monitoring.PerformanceLogger.Log()
at System.Action.Invoke()
at Qlik.Sense.Common.Triggers.TriggerBase.TriggerInternal()
at System.Threading.ExecutionContext.RunInternal(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.ExecutionContext.Run(ExecutionContext executionContext, ContextCallback callback, Object state, Boolean preserveSyncCtx)
at System.Threading.TimerQueueTimer.CallCallback()
at System.Threading.TimerQueueTimer.Fire()
at System.Threading.TimerQueue.FireNextTimers()
Stack:
at System.Environment.FailFast(System.String)
at Repository.QRSService.AppDomainUnhandledExceptionHandler(System.Object, System.UnhandledExceptionEventArgs)
at System.Diagnostics.CounterDefinitionSample.GetInstanceValue(System.String)
at System.Diagnostics.PerformanceCounter.NextSample()
at System.Diagnostics.PerformanceCounter.NextValue()
at Repository.Core.Monitoring.PerformanceInfo.<.ctor>b__5_4()
at Repository.Core.Monitoring.PerformanceInfo.GetValue(System.String)
at Repository.Core.Monitoring.PerformanceLogData..ctor(Repository.Core.Monitoring.IPerformanceInfo)
at Repository.Core.Monitoring.PerformanceLogger.Log()
at System.Action.Invoke()
at Qlik.Sense.Common.Triggers.TriggerBase.TriggerInternal()
at System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext, System.Threading.ContextCallback, System.Object, Boolean)
at System.Threading.TimerQueueTimer.CallCallback()
at System.Threading.TimerQueueTimer.Fire()
at System.Threading.TimerQueue.FireNextTimers()

Environment:

• Qlik Sense Enterprise November 2018

Reference IDs:

QLIK-92496
QLIK-92800
QLIK-93208
 

Qlik Sense April 2019 will log information including instructions to resolve the issue. See the related Release Notes for ID QLIK-92800.

See also Performance Counter issues with Qlik Sense.

Workaround:
1. Extend value/duration of "performance counter" in Repository.exe.config
    Default :C:\Program Files\Qlik\Sense\Repository\Repository.exe.config
   Default( 5 minutes) :       <add key="PerformanceLoggerIntervalInSeconds" value="300" />   
   Change TO (15 days):    <add key="PerformanceLoggerIntervalInSeconds" value="1296000" />

   : 60*60*24*8= 691200 (8days) or 60*60*24*15=1296000 (15days)

2. If Windows OS is rebooted before reaching the duration of "performance counter".  the duration will be initialized.

   For example:
   Set value of "performance counter" = "1296000" (15 days)
   If Windows OS is rebooted before reaching 15 days(1296000), the duration will be initialized and restarted again from 0.