Qlik Community
Collaborate with over 60,000 Qlik technologists and members around the world to get answers to your questions, and maximize success.
Join UsIt has been reported that in the version 3.2 of QlikSense we have unfortunately an unwanted strange behavior.
Meaning that we can see the Scheduler Service crashing on startup.
The error can be recognized by inspecting the Scheduler Service trace log, searching for this line:
“System.Scheduler.Scheduler.Core.Utility.SystemInformationProvider 8 704664c5-1aca-40b8-8570-8b294d95d10d DOMAIN\Administrator Unexpected exception when checking Repository responsiveness/validating license An item with the same key has already been added.”
Followed up by an : “System.Scheduler.Scheduler.Main 8 fa6fb50e-cc0c-4a61-be63-1b9c0cb53c9c DOMAIN\Administrator Startup sequence failed. Shutting down to avoid any inconsistent state. Please try to restart the Scheduler.”
Under some special circumstances, the scheduler terminates at startup
The issue is fixed in Qlik Sense 3.2.4 and later.
This is caused by the repository database table "ExecutionSessions" containing rows that have ReloadTask_ID field duplicated.
Collaborate with over 60,000 Qlik technologists and members around the world to get answers to your questions, and maximize success.
Join UsSearch Qlik's Support Knowledge database or request assisted support for highly complex issues.
Submit a caseExperiencing 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