Troubleshooting - Monitoring a Qlik Sense site

This section describes problems that can occur when monitoring a Qlik Sense site.

The Monitoring apps are not backed up correctly

When upgrading Qlik Sense, the Monitoring apps are not backed up correctly.

Normally, when upgrading Qlik Sense, the existing version number of the Monitoring apps is replaced by the corresponding version number appended to the app name. Then, the latest Monitoring apps are also available under Apps.

Possible cause  

The upgrade process of the Monitoring apps was unsuccessful.

Proposed action  

Manually import the latest apps from %ProgramData%\Qlik\Sense\Repository\DefaultApps\.

Procedere come indicato di seguito:

  1. In the QMC, open Apps.

  2. Click Import and select License Monitor.qvf from %ProgramData%\Qlik\Sense\Repository\DefaultApps\.

    If prompted, do not rename the app.

  3. Publish the newly imported License Monitor app to the Monitoring apps stream, replacing the existing License Monitor.

  4. Repeat step 2 for the Operations Monitor.qvf.

  5. Publish the newly imported Operations Monitor app to the Monitoring apps stream, replacing the existing Operations Monitor.

  6. Repeat steps 2 and 3 for Log Monitor, Reloads Monitor, and Sessions Monitor.

I have accidentally deleted the Monitoring apps

I accidentally deleted the Monitoring apps and cannot find them in the QMC.

Possible cause  

Accidental or intentional removal of the Monitoring apps.

Proposed action  

Procedere come indicato di seguito:

  1. In the QMC, open Apps.

  2. Click Import and select License Monitor.qvf from %ProgramData%\Qlik\Sense\Repository\DefaultApps\.

    If prompted, do not rename the app.

  3. Publish the newly imported License Monitor app to the Monitoring apps stream.

  4. Repeat step 2 and 3 for any of the affected Monitoring apps.

The Monitoring apps have become corrupted

The Monitoring apps have become corrupted and are no longer functional.

Possible cause  

Technical failure.

Proposed action  

Procedere come indicato di seguito:

  1. In the QMC, open Apps.

  2. Click Import and select License Monitor.qvf from %ProgramData%\Qlik\Sense\Repository\DefaultApps\.

    If prompted, do not rename the app.

  3. Publish the newly imported License Monitor app to the Monitoring apps stream, replacing the existing, corrupt License Monitor.

  4. Repeat step 2 for Operations Monitor.qvf.

  5. Publish the newly imported Operations Monitor app to the Monitoring apps stream, replacing the existing, corrupt Operations Monitor.

Reload of the Monitoring apps failed

There is more than one possible cause when the reload fails.

Insufficient administration rights in the QMC

Possible cause  

The service account running the Qlik Sense services does not have the required RootAdmin role in the QMC.

Proposed action  

For the Monitoring apps to successfully retrieve all data, the service account running the Qlik Sense services must be given the role of RootAdmin in the QMC.

Reload is performed on rim nodes

Possible cause  

The load balancing rule ResourcesOnNonCentralNodes causes the reloads to fail on rim nodes.

Proposed action  

Edit the load balancing rule ResourcesOnNonCentralNodes.

Procedere come indicato di seguito:

  1. From the QMC start page, open Load balancing rules.

  2. Select ResourcesOnNonCentralNodes and click Edit.

  3. Under Advanced, edit the Conditions, so that they read as follows:

    ((node.iscentral="false"))

  4. Click Apply.

Message: “Error: Field not found…

Possible cause  

Some fields that are used by the Monitoring apps are missing in the log files.

Proposed action  

Upgrade to 2.1.1 or later.

Message: “Error: Table 'tempDateTimeList' not found…

This error can occur after an upgrade, especially if the environment changes from synchronized persistence to shared persistence, or if the Qlik Sense cluster share where Archived Logs are stored is changed.

Possible cause  

The app cannot find license history data in the log files because the ArchivedLogsFolder data connection is incorrect.

Proposed action  

Fix the ArchivedLogsFolder data connection to point to the correct folder location.

Message: "Error: QVX_UNEXPECTED_END_OF_DATA..."

This error can have different causes.

Customized proxy port

Possible cause  

The proxy's HTTPS port has been customized.

Proposed action  

Change all the monitor_apps_REST_ data connections to use the customized port.

Example:  

CUSTOM CONNECT TO"provider=QvRestConnector.exe;url=https://localhost:4443/qrs...".

Data connections affected include the following:

  • monitor_apps_REST_app
  • monitor_apps_REST_appobject
  • monitor_apps_REST_event
  • monitor_apps_REST_license_access
  • monitor_apps_REST_license_login
  • monitor_apps_REST_task
  • monitor_apps_REST_user
  • monitor_apps_REST_license_user

Changes made to the user account under which the Qlik Sense services are running

Error message: Error: QVX_UNEXPECTED_END_OF_DATA: HTTP protocol error 401 (Unauthorized): Requested resource requires authentication.

Possible cause  

During installation, a user account is created under which the Qlik Sense services run. If the credentials for that account changes, or a different account is selected for the Qlik Sense services to run under, the data connections must be updated accordingly.

Proposed action  

Procedere come indicato di seguito:

  1. Open the Data connections overview page in the QMC.
  2. For each monitor_apps_REST_ data connection, click Edit and enter the new User ID and Password credentials.
  3. Save the changes.

Reloads of License Monitor, Operations Monitor, or Session Monitor fail

Error message: Error: QVX_UNEXPECTED_END_OF_DATA: HTTP protocol error 500 (Internal Server Error): Exception of type 'System.OutOfMemoryException' was thrown.

Possible cause  

The number of users and user attributes is too big.

Proposed action  

Do the following:

  • Clean your user list to reduce its size.
  • In the QMC, in the user directory connectors settings, keep Sync user data for existing users selected to avoid syncing a large number of users and user attributes.

The Monitoring apps fail to reload in a multi-node environment

There is more than one possible cause when the reload fails.

The central node is not a reload node

The Monitoring apps with default monitor_apps_REST_ data connection strings fail to reload in a multi-node environment where the central node is not a reload node.

Possible cause  

The reload node where the Monitoring apps are reloaded does not have any proxy set up.

Proposed action  

Change all the monitor_apps_REST_ data connections to point to the fully qualified domain name (FQDN) of the central node. This is accomplished by replacing localhost in the connection strings URL and trustedLocation parameters with FQDN of the central node.

Example:  

CUSTOM CONNECT TO "provider=QvRestConnector.exe;url=https://centralnodeserver.company.com/qrs...".

Data connections affected include the following:

  • monitor_apps_REST_app
  • monitor_apps_REST_appobject
  • monitor_apps_REST_event
  • monitor_apps_REST_license_access
  • monitor_apps_REST_license_login
  • monitor_apps_REST_task
  • monitor_apps_REST_user
  • monitor_apps_REST_license_user

The repository database is on a separate machine

Possible cause  

The REST data connections point to the FQDN of the Qlik Sense Repository Database and not the Qlik Sense Repository Service.

Proposed action  

In any multi-node or “remote” Qlik Sense Repository Database situation, you need to update the REST data connections to point to the FQDN of the Qlik Sense Repository Service, regardless of where the actual Qlik Sense Repository Database resides.

Operations Monitor App fails to reload after turning off database logging

The Operations Monitor reload task fails after the database logging is turned off.

The following error message is displayed:

Error: Table 'time_range_working' not found

Possible cause  

The Monitoring apps continue to check for recent logs in the database and use these logs for approximately ten hours after the last log message is written in the database. If the database logging is turned off, no new log entries for the load script can be found, and this can cause the reload process to fail.

Proposed action  

The reload fail can be prevented by manually updating the Operations Monitor app’s load script.

  1. Make sure file logging is enabled.
  2. Update the Operations Monitor load script. Because this is a published app, you need to duplicate it first.
    Procedere come indicato di seguito:
    1. Duplicate the Operations Monitor app in the QMC.

    2. Open the duplicate app in the Qlik Sense hub.

    3. Update the load script at line 9 by changing the variable db_v_file_override from 0 (default value) to 1 as follows:

      SET db_v_file_override = 1

      By setting this variable to 1, the script will not check for log entries in the database logging.

    4. Save the app.
    5. Replace the existing Operations Monitor app by publishing the duplicate app to the Monitoring apps stream and selecting Replace existing app.
  3. Launch the Operations Monitor reload task again. If it does not work immediately, wait a few minutes and reload again.

By following this procedure, the database logging can be turned off safely.

Failed to connect to the QRS via the Qlik REST Connector

Nota: This problem will only occur when you have apps that work with the Qlik REST Connector.

An error message is displayed that there is a problem connecting to the QRS via the Qlik REST Connector.

Possible cause  

The Qlik REST Connector is unavailable, because it has been uninstalled or corrupted.

Proposed action  

If the error message appears during a reload, you need to verify that the Qlik Sense installation is working properly. Consider repairing or upgrading Qlik Sense.