Skip to main content
Announcements
Qlik Connect 2024! Seize endless possibilities! LEARN MORE
cancel
Showing results for 
Search instead for 
Did you mean: 
sakshikaul
Creator II
Creator II

Migrated app to AWS

There are some issues after moving to the cloud environment.

I am not sure if these issues are due to different version of Qlik installed or due to the cloud environment settings.

Below are the issues I had gathered :

  1. I cannot lease qlik license from the cloud environment, so till now, I am still leasing from the local premise qlik server.
  2. The same pivot table
    • (on local premise qlik server), the columns can collapse
    • (in the AWS server), the collapse columns are still displaying .

 

  1. There is a particular chart with export problem ,    this message will be display “Export failed.  Please check server log for more details. (It's most likely that export process took too much Server resource)”
  2. The same script can reload on the local premise qlik server,  but cannot reload in the AWS qlik server, with script errors.
  3. The “Print Report” function works fine for local premise server (which refers to printing the report as what is shown on the screen),  but does not work in the AWS qlik server (which refers that the report printed out with many missing parts)

 

 

 

4 Replies
sakshikaul
Creator II
Creator II
Author

@nicolas_martin  Please help

rzenere_avvale
Partner - Specialist II
Partner - Specialist II

Hey @sakshikaul ,

just to be sure:

  • did you migrate to Qlik Sense Client Managed on "Windows" or "Kubernetes"? Or did you migrate to Qlik Sense Enterprise SaaS?
  • how did you migrate from your on premise version to the new one? Did you follow an article?

 

Riccardo

sakshikaul
Creator II
Creator II
Author

I have migrated from my premise version to AWS 

sakshikaul
Creator II
Creator II
Author

Hi,

I am getting following error.  cannot lease qlik license from the cloud environment, so till now, I am still leasing from the local premise qlik server.I have open up 4747 port but still following error can be seen.

sakshikaul_0-1619662819053.png