topic Re: Cloned environment different behaviour in Management & Governance

Cloned environment different behaviour

johannesholzer — Thu, 20 Mar 2025 10:32:49 GMT

Hi,

we cloned our Qlik environment (QlikSense May2024 Patch1).

So the security rules on both environments are the same.

But one user can't create an app on one environment but can on the other.

Any ideas on what could be the problem?

Or how to trace it?

Re: Cloned environment different behaviour

Alan_Slaughter — Fri, 28 Mar 2025 19:38:46 GMT

Hi are the node purposes the same for both?

https://community.qlik.com/t5/Official-Support-Articles/Guidance-on-how-to-conclude-if-the-issue-is-Security-Rule/ta-p/1716546

Re: Cloned environment different behaviour

johannesholzer — Mon, 31 Mar 2025 06:04:48 GMT

Hi,

the video is already quite nice.

The amount of nodes and the configuration differ.

Thank you

Re: Cloned environment different behaviour

johannesholzer — Mon, 28 Apr 2025 09:50:39 GMT

Is it possible to even dig deeper?

Re: Cloned environment different behaviour

henrikalmen — Mon, 28 Apr 2025 10:32:37 GMT

You say the security rules are the same, but are the licensing rules also the same? What I mean is: has the user got a professional license in the new environment?

Re: Cloned environment different behaviour

johannesholzer — Mon, 28 Apr 2025 11:24:28 GMT

The licencing is the same.

The setup is different. Production 1 central 3 rim, Test 1 central 1 rim, QA 1 central

Re: Cloned environment different behaviour

henrikalmen — Mon, 28 Apr 2025 11:53:36 GMT

Have you checked that the user has got the correct license assigned, i.e. a professional license to be able to create/edit apps? QMC -> License management, and then either "professional access allocations" or if you assign licenses by rules, go to Professional Access Rules and open the rule in edit mode, and then click User Access in the menu to the right (under Associated Items).

Re: Cloned environment different behaviour

johannesholzer — Mon, 28 Apr 2025 13:49:45 GMT

Hi Henrik,

yes, I checked. The user has the Pro Licence.

Thank you so much

Re: Cloned environment different behaviour

henrikalmen — Mon, 28 Apr 2025 14:26:06 GMT

Next step is probably to check log files. Hopefully you have installed the monitoring apps that helps you analyze them, the app "Log Monitor" is possibly the one you want. You may need to increase logging level for some services (I'm not sure which ones) in order to get the details you need to find the problem.

BTW, you say the security rules are the same, but depending on how you have set up the rules they may need to be different. For example, let's say a custom rule uses a specific ID for a stream or a server. In your new environment, those ID:s aren't the same as in the old environment, and the security rules may need to be updated to match the new environment. But I'm kind of thinking that if this is the case, you should have more than one user with the same problem. But in theory, this user may have been directed to a rim node where a specific security rule doesn't apply, and the other users that successfully can create apps may have been on another server and that's why they can and another user can't. But it's very hard to tell from the outside, I'm just guessing...

Re: Cloned environment different behaviour

BTIZAG_OA — Mon, 05 May 2025 14:32:22 GMT

Hello there,

You can try to find on QMC>Audit. Try to filter by user and check if it has Create App resource rights. If you see Green "C" icon check which security rule provided that right.

Alternate method give temporary rights to user with * and check all to see he/she create app now.

Lastly force the user to get same engine node on both server. Try to create a new Virtualproxy and set the load balancing node on the same node 1by1 to see if user get the same roled server in case you are accessing QlikSense via NetWorkLoadBalancer.

Re: Cloned environment different behaviour

RafaelBarrios — Thu, 15 May 2025 06:09:40 GMT

Hi @johannesholzer

I would bet on Node purpose configuration

is the button for creating an app and the work area visible in the hub?

By default, nodes configured as production will not allow to create apps

https://help.qlik.com/en-US/sense-admin/November2024/Subsystems/DeployAdministerQSE/Content/Sense_DeployAdminister/QSEoW/Administer_QSEoW/Managing_QSEoW/configure-node.htm

hope this helps

Re: Cloned environment different behaviour

johannesholzer — Thu, 15 May 2025 06:30:49 GMT

Thank you for your reply.

Central and node are both configured as "both".

Re: Cloned environment different behaviour

RafaelBarrios — Thu, 15 May 2025 09:43:14 GMT

Well

lost the bet

What about “is the button for creating an app and the work area visible in the hub?”

if visible, what happen when clicking on it ?

Another question, when you said “cloned” you cloned the server or did a new installation?

The reason I ask is because when you migrate an installation to another server that has a different name, you need to perform a process that changes the hostnames between the services.

https://help.qlik.com/en-US/sense-admin/May2025/Subsystems/DeployAdministerQSE/Content/Sense_DeployAdminister/QSEoW/Deploy_QSEoW/Restoring-a-site.htm#anchor-2

Also, depending on your license type, if you share the same license between environments, one server may kill the other, or there may be conflicts between users in both environments.

In any case, I suggest checking the repository logs for clues.

C:\ProgramData\Qlik\Sense\Log\Repository

hope this helps

Re: Cloned environment different behaviour

johannesholzer — Thu, 15 May 2025 11:27:06 GMT

Hi,

- the button is not visible.

- we have three environments. They have different amount of nodes. We followed the steps of that link

- we have the signed licence keys

I will check the logs.

Thank you.

Johannes

Re: Cloned environment different behaviour

howdash — Thu, 15 May 2025 12:07:01 GMT

Is the cloned server using the same server license or did you replace the server license on a cloned server with a different server license?

That might be the problem.

If your cloned server using the same license, and the user already consumed a professional license on original server, the new server may not have a professional user license left or there may be some user licensing conflicts that prevent user from being able to create apps in both server environments.

If that’s the case, the solution could be to use a separate server license for the cloned server.