Skip to content

Quick Links

My Account
Welcome Guest
Knowledge

Geo Analytics Server - No valid keystore

Article Number: 000050982 | Last Modified: 2018/08/07

Description

  • A previously working Qlik Geo Analytics Server instance's service is failing to stay in Started state, failing after 2 -3 mins. 
  • Under the logs folder (C:\ProgramData\Qlik GeoAnalytics Server\server3\logs) you will see the following error(s). 
    • "INFO ravegeo.app.JettyServer - Starting Qlik GeoAnalytics Server..."
    • "ERROR ravegeo.app.JettyServer - java.lang.IllegalStateException: no valid keystore

Environment:
  • Qlik GeoAnalytics Server June 2018

Cause

  • Without a valid path to the certificate used during the install the path will fail. 
  • Generally, Admins may believe their certs are superfluous after install, but this file and path must be maintained for the service to start. 
  • The path may be correct but the "Local Service" account used by the GeoAnalytics service may not have permissions to the path location.

Resolution

  • In the config.ini under C:\Program Data\Qlik Geo Analytics Server, you will see a line with keystore=\\filepath\certficate_name.pfx
  • This should be a valid path to the correctly configured .pfx.
  • The "Local Service" account needs permissions to the .pfx file. This can be done by navigating to the executable using Explorer, right clicking Properties, Security, and then assigning the correct permissions. Issue is less likely to occur if the .pfx file is placed under the installation location (C:\ProgramData\Qlik GeoAnalytics Server\ folder by default). Note: A restart of the Qlik GeoAnalytics Server service is needed after the permissions and/or path change.


Get Answers

Find Answers

Qlik Community

Collaborate with over 60,000 Qlik technologists and members around the world to get answers to your questions, and maximize success.

Join Us
Get Support

Have a Question?

Search Qlik's Support Knowledge database or request assisted support for highly complex issues.

Submit a case
Talk with a Representative

Critical Issues

Experiencing a serious issue, please contact us by phone. For Data Integration related issues please refer to your onboarding documentation for current phone number.

Call Us