Find Answers
Qlik Community
Collaborate with over 60,000 Qlik technologists and members around the world to get answers to your questions, and maximize success.
Join Us
Knowledge
Qlik Sense Scheduler or Repository Services start back up after being stopped
Article Number: 000038576 | Last Modified: 2018/06/12Description
After attempting the stop the Qlik Sense services, the Scheduler or Repository services start again automatically.
Environments:
Environments:
- Qlik Sense Enterprise, 3.2.3 up to and including June2017
- Multi-node environments
Cause
There are two categories of causes:
Prior to Sept2017:
Bug QLIK-81013
Otherwise:
1. Service properties "Recovery" is set to "Restart" when a service is stopped, or
2. Antivirus is locking the service or related files and preventing it from terminating
Prior to Sept2017:
Bug QLIK-81013
Otherwise:
1. Service properties "Recovery" is set to "Restart" when a service is stopped, or
2. Antivirus is locking the service or related files and preventing it from terminating
Resolution
Workarounds:
Easiest:
In the properties for the Scheduler or Repository service, set "Recovery" to "Take no action".
Most-Involved:
Investigate any AntiVirus programs installed on the server. Open task manager and select to filter by Memory (click the memory column header), and check if an AntiVirus is visible near the top of the list.
Even if there is a belief that the Qlik Sense folders have been excluded in the antivirus configuration, the symptoms warrant another check of the antivirus configuration. Exclude the following from any virus scan:
Fix:
Upgrade to September 2017 release
Easiest:
In the properties for the Scheduler or Repository service, set "Recovery" to "Take no action".
Most-Involved:
Investigate any AntiVirus programs installed on the server. Open task manager and select to filter by Memory (click the memory column header), and check if an AntiVirus is visible near the top of the list.
Even if there is a belief that the Qlik Sense folders have been excluded in the antivirus configuration, the symptoms warrant another check of the antivirus configuration. Exclude the following from any virus scan:
In Synchronized persistence:
* Exclude C:\ProgramData\Qlik\* (or relevant location)
* Exclude C:\Program Files\Qlik\* (or relevant location)
* Exclude C:\Program Files\Common Files\Qlik\*
* Exclude the folder containing the Apps
In Shared persistence:
* Exclude C:\ProgramData\Qlik\* (or relevant location)
* Exclude C:\Program Files\Qlik\* (or relevant location)
* In shared persistence, Exclude the Shared folder
* Exclude the folder containing the Apps
* Exclude C:\ProgramData\Qlik\* (or relevant location)
* Exclude C:\Program Files\Qlik\* (or relevant location)
* Exclude C:\Program Files\Common Files\Qlik\*
* Exclude the folder containing the Apps
In Shared persistence:
* Exclude C:\ProgramData\Qlik\* (or relevant location)
* Exclude C:\Program Files\Qlik\* (or relevant location)
* In shared persistence, Exclude the Shared folder
* Exclude the folder containing the Apps
Fix:
Upgrade to September 2017 release
Get Answers
Find Answers
Get Support
Have a Question?
Search Qlik's Support Knowledge database or request assisted support for highly complex issues.
Submit a case
Talk with a Representative
Critical Issues
Experiencing a serious issue, please contact us by phone. For Data Integration related issues please refer to your onboarding documentation for current phone number.
Call Us