After a server reboot, the Qlik Sense Hub and QMC are inaccessible, even though the Windows services appear to have started.
Looking in the Qlik Sense Repository log files in %ProgramData%\Qlik\Sense\Logs\Repository\Trace\
The security log may register either one of the examples below:
Certificate 'CN=QlikClient' (F4FA8D20033432841F989C9187FF83B08C4F2BCF) is invalid because it was not signed correctly by 'CN=SERVERNAME-CA' (9F7A260C62B27244EC86CB5C742C69136A567D07) f44d5a67-3b0e-48f0-b36e-7029e5b1315a
Certificate 'CN=<SERVERNAME>' (2F66E692BBC9DCB5EF43853248A667EAD7CB27B2) is invalid because it was not signed correctly by 'CN=SERVERNAME-CA' (BE907EC90AF8E0B40D442734334493AD2C316A20)
Environment:
Two known possible resolutions:
- Recreate the Qlik Sense Certificates using the instructions in the article How to recreate or just delete certificates in Qlik Sense or find a backup of the old certificates and restore them. Note: If the service account was not a local administrator originally, and only the certificates were replaced, granting permissions to the service account to the new certificates private key may resolve the issue. See How to: Manage Certificate Private Key
- If the Qlik Sense service account recently had the local administrator permission removed, follow the steps under Using an account without administrator privileges to run the Qlik Sense services during the installa...
