Skip to main content
Announcements
Qlik Connect 2024! Seize endless possibilities! LEARN MORE
cancel
Showing results for 
Search instead for 
Did you mean: 
JustinDallas
Specialist III
Specialist III

QlikSense Repository Running as LocalSystem

Hello Folks,

 

I have a QS system (relatively late version, I forget the exact one).  Our system was rebooted over the weekend, and the services on the Central node won't start.  I'm getting an error complaining about "dependent services".  

 

The one service that is running is the QlikRepositoryDatabase, but it's running as LocalSystem if I remember correctly.  Would that create problems?

Any help is greatly appreciated.

Labels (2)
2 Solutions

Accepted Solutions
Chetan_MN
Support
Support

Hi @JustinDallas The Qlik Sense Repository Database Service needs to at all times be run by the Local System account.

For dependency error, you can follow instruction in below article
https://community.qlik.com/t5/Official-Support-Articles/1068-The-dependency-service-or-group-failed-...

View solution in original post

JustinDallas
Specialist III
Specialist III
Author

SOLUTION: The issue for the dependency error came from the fact that some other process mucked with the Qlik Service Account, and either locked it out, or expired it's password causing the services to not be able to login.

 

This was NOT a problem with QlikSense but on our own infra's end.

View solution in original post

3 Replies
Chetan_MN
Support
Support

Hi @JustinDallas The Qlik Sense Repository Database Service needs to at all times be run by the Local System account.

For dependency error, you can follow instruction in below article
https://community.qlik.com/t5/Official-Support-Articles/1068-The-dependency-service-or-group-failed-...

ashimdash
Contributor II
Contributor II

Ditto. It needs to be run by the Local System Account. 

JustinDallas
Specialist III
Specialist III
Author

SOLUTION: The issue for the dependency error came from the fact that some other process mucked with the Qlik Service Account, and either locked it out, or expired it's password causing the services to not be able to login.

 

This was NOT a problem with QlikSense but on our own infra's end.