Skip to main content
Announcements
Have questions about Qlik Connect? Join us live on April 10th, at 11 AM ET: SIGN UP NOW
cancel
Showing results for 
Search instead for 
Did you mean: 
HardikNaidu
Contributor II
Contributor II

QlikSenseTask.exe Issue

Hello Guys,
We had earlier used a .bat file to execute Qlik Reload tasks from external too(ControlM), using the below links.

https://developer.qlik.com/garden/56f2e998f1c173fc24afe6ec?_ga=2.78670995.648439966.1575276136-16087...

https://github.com/eapowertools/QlikSenseTask

This was working fine, until the last month, but all of sudden it started to fail with the below error. please could you help us, for the reason for the below error and any possibility to troubleshoot further.

2019_11_29_09_20_21,Information,"Task: Ext_Audit"

2019_11_29_09_20_21,Information,"Proxy: https://XXXXXXXXX"

2019_11_29_09_20_21,Information,"Wait: 60000 seconds"

2019_11_29_09_20_22,Information,"Task is starting..."

2019_11_29_09_20_22,Error,"System.Exception: Forbidden: Forbidden

   at QlikSenseJSONObjects.QlikSenseJSONHelper.StartTaskByName(String taskname, Boolean synchronous)

   at QlikSenseTask.Program.Main(String[] args)"

2019_11_29_09_20_22,Information,"Returning Errorlevel 8"



Cheers

 

Labels (1)
12 Replies
rzenere_avvale
Partner - Specialist II
Partner - Specialist II

Good evening @HardikNaidu ,

I believe we need more info...
Did something happen last month?
Did you rename the task on QS? Did you upgrade QV and/or QS? Did something on the network side happen?
Did you change QV's service user (which is the one that actually triggers the task, in the base version)? Did you change the role of QV's service user on QS or the visibility of the task on QS for said user?

Riccardo

HardikNaidu
Contributor II
Contributor II
Author

Hi Riccardo,
Many thanks for your response.

No we didn't change anything from the network,task name or the service credentials(or the roles of the user).

The only change was the upgradation of the Qlik , to the "Qliksense September 2019 Patch 1 - 13.42.1" version.

CHeers

danielconde
Partner - Contributor
Partner - Contributor

Got a similar issue after upgrading to September 2019, ¿did you found any solution?

simokorpikoski
Partner - Contributor
Partner - Contributor

I'm in the same exact situation. Using control-m to run qlik sense task .bat files.

Running the bat works manually but when trying to execute with control-m I get the following error:

2020_02_19_17_53_26,Information,"Task is starting..."
2020_02_19_17_53_27,Error,"System.Exception: Bad Request: "TASKNAME"
at QlikSenseJSONObjects.QlikSenseJSONHelper.StartTaskByName(String taskname, Boolean synchronous)
at QlikSenseTask.Program.Main(String[] args)"
2020_02_19_17_53_27,Information,"Returning Errorlevel 8"

 

Did you figure out a solution to this?

HardikNaidu
Contributor II
Contributor II
Author

Hello Guys,

Did not find a fix yet on this. Issue seems to be on the Qlik side and we are still trying for a fix or workaround.

md_anasabbasi
Contributor III
Contributor III

Hello @HardikNaidu ,

The Error you are facing should be solved by creating the Control-M user as Content Admin in the QMC, or the other way which I have implemented is create some security rules valid for QMC and give 'read update' privilege to the Control-M user for QMC section App and task and in a separate rule give access to the app and task which needs a trigger from QlikSenseTask.

This way your issue should be resolved. Please mark your answer solved if this solves your issue. 😊

Best Regards,

Anas

md_anasabbasi
Contributor III
Contributor III

Hello @simokorpikoski ,

You have a different issue what Hardik has. Its actually because of the Control M agent service is running by Local System. You need to make sure to run the service of the Control M agent using a controlm user/account. and also make sure this user has access to read and update to the QMC apps and tasks. 

This issue is basically due to the wrong user running the Control-M account.

Please mark me in the comment if you need more help. But this should solve the issue. Cheers!

Best Regards,

Anas

HardikNaidu
Contributor II
Contributor II
Author

Hi Anas,

 

We have tried everything but issue still persists.

We have also installed new version of CtrlM. This seems to be an Integration issue.

DO you have any document on the details you were providing ??

 

Thanks,

Hardik

mianotta
Partner - Contributor
Partner - Contributor

I have the same problem, did you find the solution?