Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi Guys, QRS has not started after QSE installation – PostgreSQL issue? I don't know..
Before I give you more hints, two major findings from Log files and Event Manager:
Environment:
Step by Step:
I read other related threads but I have not found anything like this.
Thanks @mateusz2.
The issue seems could indeed be linked to:
Qlik Sense Repository Service fails with Error An ... - Qlik Community - 1908453
Cheers,
Albert
Qlik Sense Repository Database should run as Local System.
Qlik Sense Repository Service should run as your named administrator.
Your screenshot shows the opposite user details.
Also make sure that the user running Qlik Sense Repository service has read/write access to the file share, if there are no files generated in your share.
Hi ,
Did you manage to resolve this? if yes how please share, I am facing same issue.
Thanks in advance
Prateek Kamra
Hi,
Has Anyone found a solution for this? I have the same problem.
Thanks in advance
Hi @mateusz2,
What is your Qlik Sense version ?
And what the Qlik Sense repository logs are saying ?
This where I would start in order to try understand why Qlik repository service is not starting.
Regards,
Benoit
Hi @Benoit_C ,
My version is November 2021 patch 3.
My logs are saying the same like in the first post in this topic.
I attached my logs (with translation in the comment).
Was it working before or it's a first installation ?
What account is running the Respository Database service ? And what account is running the Repository service ?
Yeah, it was working until restart the server (planned restart).
Repository Database service is running as local system.
Repository service is running as local admin account with administrator rules.
Can you try a Qlik Sense repair ?
https://help.qlik.com/en-US/sense-admin/November2021/Subsystems/DeployAdministerQSE/Content/Sense_De...
First, I updated Qlik to Version from February 2022 - it didn't solve my problem.
Second, I checked your link and repaired Qlik in that way- it didn't help either.
After theses steps a logs show the same error messages like before.