Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
When deleting users in PostGres, by mistake deleted all the users in Postgres except RootAdmins and few other users. I did this 3 days ago and trying to figure out how to get all the Qlik Internal accounts and Qlik server accounts. Any help is much appreciated.
Did not do any manual backup in Postgre or Qlik or server backup. And the Qlik has lot of data, apps, extensions, data connections in it.
Learned my mistakeS not gonna touch Postgres in future. Any help or direction to fix the current issue is much appreciated.
@Mr_Pearl I am glad the solution works for you via our case. If so, could you please mark this is answered? Thank you.
If any one face the same issue, please log the case with support for the solution.
@Mr_Pearl There are two ways for Qlik Sense to have Qlik Sense user Account in QMC.
1. User manually login. As long as the user has been authenticated successfully, the user account will be automatically created.
2. Load users in batch mode through UDC.
So you users account can be recovered easily. Only the user's bookmark and etc will be lost.
To recover users, you can either let them login individually or load from UDC. If there is no UDC, you can create UDC but make sure to have correct filter and load those users who are allowed to access Qlik Sense. Otherwise extra users can be loaded into QMC.
More details about UDC can be found from https://help.qlik.com/en-US/sense/February2019/Subsystems/ManagementConsole/Content/Sense_QMC/user-d....
Hope this helps.
@Lisa_Sun Thank you for your reply. But I am not talking about user accounts. I am talking about lost Qlik accounts like sa_repository, sa_api etc., and Qlik sense server setup accounts (accounts that are responsible to install and run the Qlik sense server). Without these accounts we cannot open or run Qlik QMC/Qlik hub.
@Mr_Pearl I am glad the solution works for you via our case. If so, could you please mark this is answered? Thank you.
If any one face the same issue, please log the case with support for the solution.