Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi, we are not able to create QLIK tasks through QEM APIs.
Error we are seeing in server logs:
Hello @rahulkokane
We don't have any APIs to create task using REST API, .NET API and Python API in QEM.
Kindly let us know which command you're trying to run at QEM server.
Below is the supported API commands
Qlik Enterprise Manager API guide | Qlik Enterprise Manager Help
Regards,
Suresh
No we are not using the REST API. Rahul is talking about the action=import which we use to import a task on a server there we are getting
Failed to create cloud task :testattunity. Request Error</p> <p>The server encountered an error processing the request. See server logs for more details.</p>
thanks @ShrinathAnkita for adding this.
Hello @rahulkokane @ShrinathAnkita
As you already opened a support ticket, lets continue to troubleshoot the issue in the opened support ticket.
Regards,
Suresh
>>> Hi, we are not able to create QLIK tasks through QEM APIs.
FWIW: The QEM has it's own forum, but admittedly it only reaches a small audience of experts and also admittedly is heavily polluted by misguided Qlik Sense adventurers. https://community.qlik.com/t5/Qlik-Enterprise-Manager/bd-p/qlik-enterprise-manager-discussions
Anyway, please clarify. Does that mean you are trying to IMPORT tasks through the Enterprise manager with a script?
- Did it ever work? Does it work in a lower (DEV) environment?
- Does it work with through the QEM - UI directly?
- Does it work on the Replicate Servers directly - with UI and/or using REPCTL importrepositry?
>>> Our PROD env is hamered,
?!?! English please! Use your words. Full sentences please. We are not mindreaders.
From the log:
...Database /attunity/data/tasks/RepoGlobal.repo is locked. Retry count is
... Free repository /attunity/data/tasks/xxx/xxx.repo
That feels like poor error handling Assuming a root cause.
Now those logs were set to verbose, which may well be required for analysis. At the same time it may be reporting way to many event which look bad but are in fact good - like when creating a fresh object, one may try to delete it first but if it is not there, that's ok.
Perhaps the root cause is a protection violation ?
Hein.