Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
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?
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
hope this helps
Thank you for your reply.
Central and node are both configured as "both".
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.
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
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
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.