Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi,
We are migrating from Qlik Sense Windows to Cloud.
When running the migration scipt for migrating apps, it gives error. Tried each line in qlik cli. The line that fails is
qlik qrs app export create $appid --skipdata $SS --exportScope all --output-file $exportAppFile
Error: 400 - Bad Request (empty response)
But when i run the command without the --exportScope all option in qlik-cli it works.
qlik qrs app export create $appid --skipdata $SS --output-file $exportAppFile
Are there any permissions or setup that i am missing?
Thanks,
Anuradha
hello @akshaychavan1
The root cause has been identified as related to the use of cookies in Qlik-Cli. As a temporary workaround, when the error occurs, you can manually delete the cookie store and then re-run your command:
On Linux: delete ~/.qlik/.cookiestore
On Windows: delete %USERPROFILE%\.qlik\.cookiestore
Please note: this workaround needs to be repeated each time the issue comes up, so it’s not a long-term solution. The R&D team is aware and working toward a permanent fix.
Hope this helps in the meantime!
Eyal
@anuradha-bala does that user have permissions to ALL objects in the app?
Hi @anuradha-bala , which version of Qlik Sense for Windows are you using? And which version of the cli?
HI @Daniele_Purrone ,
I encountered the same error when running the API using CLI version 2.26.0 and Qlik Sense November 2024 Patch 10.
In my case, it didn’t matter whether I removed the --exportScope all option — it worked the first and second time, but then after some attempts, it started throwing a 400 Bad Request error.
I will open a support ticket to investigate this further.
Regards
Eyal
Hello Eyal,
We are facing exactly the same issue. We have Qlik Sense November 2024 and CLI version 2.0.
Do let us know if you get the support .
Thanks,
Akshay
Hi @akshaychavan1 . As @eyalnir_qlik already knows, we were able to reproduce the issue ad reported it to R&D as a defect with ID SUPPORT-3800. We are currently waiting for feedback from the dev team.
Hello @Daniele_Purrone @eyalnir_qlik do we have any update on the support ticket?
hello @akshaychavan1
The root cause has been identified as related to the use of cookies in Qlik-Cli. As a temporary workaround, when the error occurs, you can manually delete the cookie store and then re-run your command:
On Linux: delete ~/.qlik/.cookiestore
On Windows: delete %USERPROFILE%\.qlik\.cookiestore
Please note: this workaround needs to be repeated each time the issue comes up, so it’s not a long-term solution. The R&D team is aware and working toward a permanent fix.
Hope this helps in the meantime!
Eyal