Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Join us in NYC Sept 4th for Qlik's AI Reality Tour! Register Now
cancel
Showing results for 
Search instead for 
Did you mean: 
NicolaBianchini
Contributor
Contributor

Qlik Repository Service stops shortly after starting – credentials update after reboot

Hi everyone,
I’m reaching out for support regarding an issue we’re experiencing with the Qlik Repository Service.

Following a power outage, all machines were rebooted. This caused the Qlik services to fail on startup because the Windows user (with admin rights) used to run them had its password changed beforehand.

Everything worked fine before the reboot, most likely because the machine had not been restarted for a while and the services didn’t need to relaunch.

After the reboot, our VAR Group partner updated the service credentials across all Qlik services. Most of them are now starting properly. However, the Qlik Repository Service starts and then shuts down automatically after a few seconds.

We tried following the suggestions from this thread:
👉 Qlik Sense Repository Service will not start,
but unfortunately it didn’t help—the service still stops shortly after launch.

Here are some log entries that seem relevant:

122  20250424T163609.542+0200  WARN  PEPQLIK  System.Repository.Repository.Core.ProxySettings.ProxyServiceSettingsInstallerFile  6  a3bdf9e1-5d4a-4d5d-9041-e98ae3d2ae03  PEPLOYAL\qservizi  ProxyServiceSettingsUpdate will be skipped (File: C:\ProgramData\Qlik\Sense\Installation\InitialServiceCluster.xml does not exist)        a3bdf9e1-5d4a-4d5d-9041-e98ae3d2ae03

131  20250424T163939.855+0200  WARN  PEPQLIK  System.Repository.Repository.Core.Licensing.LicensesInitializer  6  ab157f7b-e457-41cd-8be4-e14eae7c2b5f  PEPLOYAL\qservizi  There was an error contacting the license service. Keep retrying... (30 failed requests) GET /v1/licenses/overview StatusCode: InternalServerError Response: .  Could not connect to the license service.  NO-STACKTRACE    ab157f7b-e457-41cd-8be4-e14eae7c2b5f

 

We currently have no clear idea of what might be causing this behavior. Has anyone experienced something similar or can suggest where we should focus (e.g., configuration, missing XML file, licensing, etc.)?

Thanks in advance for any help or suggestions!

 

 

 

 
Labels (3)
0 Replies