Monday, 17 September 2018

Sense Monitor App Reload Failure

QlikSense

QlikSense Monitor App Reload Failure



Please perform the following:


1. First, it's very important to verify that the Service Account is added to your proper AD Group and is an admin, especially if your UDC in the QMC uses an LDAP filter.


2. If the user account to run the Qlik Sense Services has changed, follow these instructions. If not, please skip this step:



 http://help.qlik.com/en-US/sense/November2017/Subsystems/PlanningQlikSenseDeployments/Content/Deployment/Change-user-accounts.htm



3. Temporarily disable antivirus, and then open all ports in the firewall that are needed according to the only documentation for the November release.


4. Check that all services are running and can be restarted, as well as verifying the user account running them.


5. Now, let’s dive into the Admin Portal and have you open the QMC


6. Delete all connections in the "Data Connections" tab that begin with "QRS_" (before June 2017) and "Monitor_Apps_" (after June 2017) -- delete all of them for both with those names


7. Delete all monitoring apps in the "Apps" tab that are named License Monitor, Operations Monitor, etc.


8. Minimize QMC. Delete all "QVD" files within the Windows Directory that related to the monitoring apps (usually C:\ProgramData\Qlik\Sense\Log"). All files related to "reloads", "governance", "monitor", "etc... any QVD file listed in this Log folder needs to be deleted except ones with "central logging"


9. In addition, go to the shared ArchivedLog shared folder in Windows and ZIP all log files especially the Engine logs, as anything older than 6 months can sometimes cause the reloads to fail. Once a ZIP is done, delete all log files.


10. Open QMC


11. Check the Virtual Proxy to see if they use a prefix. If so, this prefix needs to be included in the DC connection strings.


12. Check the Proxy and verify the HTTPS Default port is 443. If not, update the DC connection strings.


13. Check the Proxy and verify that Kerberos Authentication is notenabled.


14. It is required that at least one virtual proxy uses the Windows authentication pattern for the monitoring apps to work. Please confirm you are using "Windows" in the Virtual Proxy settings under the "Authentication" section.


15. Now, in the Apps section of the QMC, import the new default monitoring apps using the "Import" button within the "Apps" section of the QMC. C:\ProgramData\Qlik\Sense\Repository\DefaultApps


16. After which, click on "Tasks" under "Associated Items" for each Monitoring App that was imported and create an automatic rule to have them automatically refresh. Set the time for the first start to 1 minute from now so that the trigger will automatically kick off once you save.


17. Go to the "Data Connections" section of the QMC to verify that new "QRS_" (before June 2017) or "Monitor_Apps_" (June 2017+) data connections were re-created.


18. Open one of them and view the entire connection string. Verify that this exists in the string ";skipServerCertificateValidation=true;"


19. Verify if https://localhost (June or newer: listed twice in each data connection and both must be updated; 3.2.5 or older: listed once) or the FQDN should be listed in each connection string and change if needed. FQDN is required for multi-nodes or cloud solutions.


20. Go to the Apps section, click on the monitoring apps that were imported, choose "More Actions" and click "Reload Now".


21. Go to the "Tasks" tab to see if they reloaded. Hit refresh in the top right of the QMC page.


22. If the task fails, open each Data Connection beginning with "QRS_" (before June 2017) or "Monitor_Apps_" (after June 2017), and put in the User ID and Password for the Service Account running the Qlik Services. This account must be an administrator with Full Control and be a part of the required AD Groups listed in the installation guide.


23. In November 2017 release there is a code related issue. If it’s an upgraded November 2017 (non-patch) release then use a copy of the September 2017 mon app QVF files, in the QMC import them, then replace the November mon app files. The Data Connections and QVD files in the folder may or may not need to be deleted; trial and error.


24. Reload tasks manually and collect the Script Reload Logs.




No comments:

Post a Comment

Nprinting- (ver -16) Server Certificate Update Process

Certificate Update Process for QLIK Nprinting Import the certificate to QV Nprinting Server 1. Copy the certificate to the Server th...