
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
Scheduler: No Worker Scheduler Found
Jun 14, 2021 3:32:26 AM
Oct 3, 2019 4:55:34 AM
Scenario :
- Single node
- All services installed, up and running
Possible Error messages :
- Unhandled exception: Failed to access performance counter data. Make sure that performance counters are enabled or try rebuilding them with lodctr /R.
- Category does not exist.
- Could not reserve an executor for task: No node found for task(name/id)
- Failed to send alive notification to manager.
- Could not obtain the current CPU load.
- Worker-node XXXX is not alive and cannot run task YYYYYY
Environment:
- Qlik Sense Enterprise on Windows , all versions
- Windows 2012 R2 datacenter edition
Resolution:
Steps for resolution :
1. Rebuild the performance counters (lodctr /R)
Tasks do not reload after upgrade to Qlik Sense June 2018
2. Disable the loopback check
Reopen Registry and navigate to HKEY_LM\System\CCS\Control\LSA\MSV1.0 and create the following DWORD key
DisableLoopbackCheck
Value : 1
3. Then, reboot the box
Related Content:

- Mark as Read
- Mark as New
- Bookmark
- Permalink
- Report Inappropriate Content
Hi I upgrade machine to Qlik Sense May 2024 and i want to execute preload task but i always receiving the same error "No workers found to execute task". I do all what is suggested on this page but no any changes error is same .
After reboot my machine this is log in Scheduler
After reload tasks

- Mark as Read
- Mark as New
- Bookmark
- Permalink
- Report Inappropriate Content
Hello @saso70
Please review A specific task displays Error status message No worker scheduler found for an additional root cause.
Should neither of the articles help, please post about your issue directly in our Qlik Sense Management and Deployment forum, including the version, information about your setup, and the errors you receive.
All the best,
Sonja

- Mark as Read
- Mark as New
- Bookmark
- Permalink
- Report Inappropriate Content
@saso70 Did you find a solution for your problem? I see the same error after upgrading

- Mark as Read
- Mark as New
- Bookmark
- Permalink
- Report Inappropriate Content
Ok, found it myself. Theres a new checkbox in the node settings called "Scheduler to do preloads", which must be enabled...