Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hello Qlikview Community,
We have recently noticed a few anomalies with our Qlikview server and hope to find a solution here.
Currently, we have to re-enter all CALs manually after every server restart.
These CALs are located in the Management Console in the respective dashboards (Document CALs) and under System - Licenses - Qlikview Server - Assigned CALs
We are at our wit's end and have no idea what leads to the deletion of all CALs after a restart.
Has anyone here had similar experiences or knows what the reason is?
We have installed Qlikview May 2023 SR1.
I have also noticed two error messages in the Event Viewer:
1.
(ActiveDirectory.ADItem) Failed to initialize node : Invalid DirectoryEntry (objectGUID/sAMAccountName)
2.
(ActiveDirectory.ActiveDirectoryProvider) Node initialization exception: Invalid DirectoryEntry (objectGUID/sAMAccountName)
However, it can query all users from the Active Directory without any problems. This can be seen from the fact that Qlikview finds the corresponding users with every query.
I would be very happy about help 🙂
Many thanks in advance
Sven
Hello @Chewy,
For context, Named User CALs are stored in the CalData.pgo file (refer to article What Information Is Stored in the QlikView PGO Files?). PGO files are stored in a primary folder: the Root folder configured in the QMC > System > Setup > QlikView Server > @QlikView Server > QVS@ > Folders tab > Root Directory entry, and a secondary folder: %ProgramData%\QlikTech\QlikViewServer.
Typically when Named User CALs become deleted, the cause is a interruption in communication between the QVS and the CalData.pgo file - such as anti-virus software placing a file lock on the .pgo file. Other root cause can be loss of synchronization of the .pgo files in the above locations, or corruption of the .pgo files.
Previous Qlik Community thread https://community.qlik.com/t5/QlikView-Administration/Assigned-Cals-are-getting-deleted-on-the-qlikv... provides the normal method to resolve the issue.
Note that once you have completed assignment of Named User CALs to the desired users, you can take a back up of the CalData.pgo file incase you need to restore the file. This will save time in that the users won't have to be manually assigned. Refer to Qlik article How to Restore PGO Files from a Backup for more details.
Reviewing the QlikView Server Events log with high verbosity enabled is a good troubleshooting step for this issue. Please share these logs for dates of the issue if you can. Otherwise, if you need direct assistance with this issue, suggest that you open a case with Qlik Support.
Best Regards
Hello @Chewy,
For context, Named User CALs are stored in the CalData.pgo file (refer to article What Information Is Stored in the QlikView PGO Files?). PGO files are stored in a primary folder: the Root folder configured in the QMC > System > Setup > QlikView Server > @QlikView Server > QVS@ > Folders tab > Root Directory entry, and a secondary folder: %ProgramData%\QlikTech\QlikViewServer.
Typically when Named User CALs become deleted, the cause is a interruption in communication between the QVS and the CalData.pgo file - such as anti-virus software placing a file lock on the .pgo file. Other root cause can be loss of synchronization of the .pgo files in the above locations, or corruption of the .pgo files.
Previous Qlik Community thread https://community.qlik.com/t5/QlikView-Administration/Assigned-Cals-are-getting-deleted-on-the-qlikv... provides the normal method to resolve the issue.
Note that once you have completed assignment of Named User CALs to the desired users, you can take a back up of the CalData.pgo file incase you need to restore the file. This will save time in that the users won't have to be manually assigned. Refer to Qlik article How to Restore PGO Files from a Backup for more details.
Reviewing the QlikView Server Events log with high verbosity enabled is a good troubleshooting step for this issue. Please share these logs for dates of the issue if you can. Otherwise, if you need direct assistance with this issue, suggest that you open a case with Qlik Support.
Best Regards