Qlik Sense & NPrinting On‑Prem to Private Cloud – Feasibility and Considerations

[balajibc64]

Hello,

We are currently running the following Qlik components in an on‑premises environment:

• Qlik Sense Enterprise
  • Central Node
  • Rim Node
• Qlik NPrinting Server
• All components are Enterprise editions
• Operating System: Windows Server 2016
• No dedicated primary/secondary (failover) setup is in place

We are planning to migrate this setup to a private cloud environment. As per our internal TS team, the proposal is a lift‑and‑shift migration, where the servers will be moved as‑is and only the IP addresses will change.

Queries:

1. Is a lift‑and‑shift approach feasible for Qlik Sense and NPrinting in this scenario?
   Will the environment function correctly if only the IP addresses change?

2. What are the key technical considerations or risks we should be aware of during such a migration (e.g., certificates, services, communication between nodes, scheduling, integration components, etc.)?

3. What steps or validations should be performed before and after the migration to ensure:

   • Qlik Sense Central and Rim node communication remains intact
   • Qlik NPrinting can successfully connect to Qlik Sense
   • Reloads, tasks, and reports continue to work as expected

4. Given that we do not have a HA / primary‑secondary setup, are there any recommended best practices we should follow for a private cloud deployment?

[balajibc64]

Hi @Lech_Miszkiewicz Thanks for the link. I followed the below mentioned steps after that its working fine.

After restore QSR backup tar file. Also copied some folders like Apps, Content (if exists). I'm facing the issue to open the QMC Url in the server. 

Step 8: Login into the Postgres SQL DB via command prompt. Check the tables like Apps, ServerNodeConfigruation, ProxyConfiguration etc. 

Step 9: In the ServerConfiguration table, I have 2 entry one is Central Node and Another one is Rim Node. Here I have delete one entry related to Rim Node. Then update hostname column from my old on-prem server name to new private cloud server name. After that started all the service. 

Step 10: Then try to access the QMC and Hub links. Its working fine. 

Note: I didn't do any certificate changes in the new private cloud server. 

Kindly advise, whether these steps are fine or not. 

[balajibc64]

Hi @Lech_Miszkiewicz @Eduardo_Monteiro  I tired based on the URL its working fine. I can able to take backup and restore into my new private cloud server. Also verified with the on-prem its matching. 

But here I'm facing one issue. I can able to open the HUB URL, but when i tried to access the my app, showing error message like " an error occurred the app you specified could not be found Error Code 1003 ".

Kindly advise. 

[Eduardo_Monteiro]

Hi @balajibc64 

This is probably your service cluster pointing to the wrong path.

Please check the following link: How to change the share path in Qlik Sense (Service Cluster)

Regards,

[Lech_Miszkiewicz]

I agree with @Eduardo_Monteiro that this is likely due to service cluster paths not updated properly, but link I have sent you mentions this as follow up steps so naturally I thought you would just do all the required steps as it is written in official documentation.

Have you read through the link at the bottom and all related links?

[balajibc64]

Hi @Eduardo_Monteiro  Yes you mentioned, I have verified the service cluster. Its showing different path. 

Here my problem is my Test environment and Prod environment cluster is different (included one folder). 

Test On-Prem : //clusterservername/QLIK/Sense/QLS005/Apps 

Prod On-Prem: //clusterservername/QLIK/Sense/Apps (Now this is same as my Test Private Cloud Env).

Can you pls guide. 

@Lech_Miszkiewicz  I didn't do any certificate changes from my end. But as per Qlik Document I have change my hostname automatically using this command 

Repository.exe -bootstrap -standalone -restorehostname

[Lech_Miszkiewicz]

HI @balajibc64 

I didnt mean certificates but also as mentioned earlier the share paths in a cluster setup. They need to be updated as per my link and link from @Eduardo_Monteiro. Mine was generic to say to update hostname, but obviously if you changed shared paths in your environments those need to be reflected so Qlik knows where apps and other content is located. Make sure you update those paths so it reflects your new settings. Then reboot and see what happens.

cheers

[Eduardo_Monteiro]

Hi @balajibc64 

Please read carefully the link I sent you in the last post.

You need to stop all service and start from step 8.

Like @Lech_Miszkiewicz and I said earlier, you need to change your service cluster to reflect your current environment.

You will also need to fix your data connection and check if you have load balancing rules mentioning different node alias or hostname.

BR,

[balajibc64]

Hi @Eduardo_Monteiro I tired as you suggested and also referred the document. Based on the I have changed the Qlik Sense Cluster path. and now correctly showing in my QMC. Also I verified the path to access from my Central node and Rim node server. Able to access the respective path. 

But still facing the same issue 😞

Note: I didn't create any shared folder, because already we created the shared folder and port for both Central and Rim Node server. 

Also, I create one new app in Central node server and tried to open via HUB. Its working fine.  Then I tried to access the same app via Rim Node HUB, but its showing the same issue like " The app you specified could not found" 

Kindly advise 

@Lech_Miszkiewicz 

[Eduardo_Monteiro]

Hi @balajibc64 

Do the following steps:

Create a new app in the hub.

Open the app, load some demo data (ctrl+0+0), close the app

Try opening an existing app

Collect and share the logs from: %ProgramData%\Qlik\Sense\Log\Engine\

Regards,

[balajibc64]

Hi @Eduardo_Monteiro  As you mentioned, I tried. I got the logs. Here I can't able to share the attachment due to organization security policy. 

Can you please suggest which logs required, so i will copy as text here. 

Below are the logs I have. 

SWSCFT5NPQLK101_AuditActivity_Engine.txt
SWSCFT5NPQLK101_QixCounter_Engine.txt
SWSCFT5NPQLK101_Service_Engine.txt
SWSCFT5NPQLK101_Session_Engine.txt
SWSCFT5NPQLK101_System_Engine.txt