Qlik Sense - StdServer: ServiceCtlRequest caught exception -1
Article Number: 000045708 | Last Modified: 2018/11/21
In the Qlik Sense Engine logs (By default stored under C:\Programdata\Qlik\Sense\Log\Engine\Trace\xxx_System.log), you might see from time to time the following error showing up
StdServer: ServiceCtlRequest caught exception -1
You might want to understand the cause and the impacts.
The exception -1 is very generic and might happen for different reasons.
A potential root cause we have seen in another environment is the following:
Looking at what is happening just before this error, we could see different applications being loaded by the user sa_scheduler. (This happen when a reload task is running basically)
Those errors were happening only during working hours so when users were using their application.
So in this environment we noticed heavy reload occurring at the time the users were working on those application in a single environment meaning that the engine was taking care of the calculation for the users as well as reloading the tasks.
Looking at the script logs for those tasks (By default stored under C:\Programdata\Qlik\Sense\Log\Script) we could see that those errors were happening at the end of the reload while the engine was releasing the application.
In any case those errors don't seem to cause any damage or problem to the reload task as they all ended successfully and we could as well see retries until the engine was able to proceed with the request
If you want to completely remove this error from the logs we suggest an analysis of your environment.
If you are running in the same context as mentioned below, we would advise you to either schedule your reloads when there is less/no activities from the users in the environment or perhaps having a dedicated node for the reload.
You can also check the resource consumption on your server to make sure your machine is not overloaded. How to log CPU and memory with Microsoft Performance Monitor on a windows 2012 Server (PerfMon)