Skip to main content
Announcements
Introducing Qlik Answers: A plug-and-play, Generative AI powered RAG solution. READ ALL ABOUT IT!
cancel
Showing results for 
Search instead for 
Did you mean: 
zxcv23sad
Contributor II
Contributor II

Qlik's Windows services not starting automatically after server restart (event ID 7000)

Hello,

We have Qlik 14.159.4 installed in Server 2019 and problem is that not all of Qlik's Windows services start properly after restarting the server (for example when Windows Update installs the latest CU etc.).

Below is from yesterday evening so after the Server 2019 restarted some of Qlik's services woulnd't start.

And I could fix that by simply going to services.msc and selecting those Qlik's services and "Start".

Those services are configured already to use "automatic (delayed start)" so for them to try to start before network/connection to DC is working seems a bit unlikely?

And as I wrote, some of the Qliks services were up and running this morning when we noticed the issue, but for example Qlik Sense Repository Service and Engine services were down.

Any ideas what to try?

event 7000.png

Error is "The Qlik Sense Repository Service service failed to start due to the following error:
The account name is invalid or does not exist, or the password is invalid for the account name specified."

 

Service settings are like this:

 

zxcv23sad_0-1708586703036.png

 

Labels (1)
7 Replies
rubenmarin

Hi, you can try to log on the server with the user and password that should start the services, just to check that the user credentials works, maybe the password has changed or has expired, also maybe the user is blocked on active directory.

If you can start the session with those credentials try to set them again in the 'Log On' tab of the service properties.

zxcv23sad
Contributor II
Contributor II
Author

As I wrote I could start the services simply by starting them so that's not the issue.

rubenmarin

Ok, sorry, I skip that part.

Maybe in c:\ProgramData\Qlik\Sense\Log\Repository you have more details about the error.

Or in [ShareFloder]\ArchivedLogs\[ServerName]\Repository for older logs.

Just guessing but maybe it could be caused by some antivirus or similar blocking the use of credentials on startup: https://community.qlik.com/t5/Official-Support-Articles/Qlik-Sense-Folder-And-Files-To-Exclude-From-...

henrikalmen
Specialist
Specialist

It seems that you installed the qlik services with an account that has since been removed or has had its password changed. So when the machine restarts, windows tries to start the services with invalid credentials. In the overview list of services you can see what account the services belong to. Hopefully this will give you a hint on how to proceed in your environment.

zxcv23sad
Contributor II
Contributor II
Author

Dude, why do you even reply to these if you can't be bothered to read my post properly?

henrikalmen
Specialist
Specialist

I'm sorry you feel that way. I believe I read your post thouroughly, and actually I still believe that I have. A part of your post is this: Error is "The Qlik Sense Repository Service service failed to start due to the following error: The account name is invalid or does not exist, or the password is invalid for the account name specified."

So I am thinking that the machine tries to auto-restart the services, but it can't because the credentials it is instructed to use are invalid. But when you start the services manually, you are starting them with the currently logged in user and then everything is fine.

But ok, maybe I have completely misunderstood something.

marcus_sommer

I think @henrikalmen is right and the user-credentials are invalide. We had recently the scenario that the user-name of our admin-user was changed - not the user and it's id itself else only the alias. The most things worked afterwards like before unless the QlikView server-services and various windows-tasks which were needing a re-assigning of the user with it's credentials. I don't know why but I could imagine that the services/tasks uses some kind of a (hashed) cache (with additional information to the environment) to make them more stable and/or independent against the active directory request.