Resolving Quest Service Fluctuations in Sisense
Summary
This article could help you fix the Quest service issue in Sisense fluctuating between active (green) and inactive (red) states under the https://yourhost/app/test page.
Step-by-Step Instructions to Resolve the Issue
-
Confirm Plugin Version:
- Ensure that the Quest plugin is updated to the latest version. This could be checked on the marketplace.
-
Check the Logs:
- Review the relevant logs from the following directory: C:\ProgramData\Sisense\application-log\quest.log.
-
Reset Licenses and Reactivate Services:
If you get an error like "OAuth unsuccessful server response status_code=400" in the quest logs, please try to
- Reset the activations for the server where the issue is replicated via my.sisense.com.
- Reactivate Sisense using the Sisense Activation app on the server.
- Restart the Sisense.Oxygen and Sisense.Quest services.
For Multi-Node - Check the Deployment Configuration:
- Ensure that the Quest service and the Plugins service are both running on the same node (typically the build node) and are disabled on any other nodes.
- Refer to the supported deployment models for Sisense multi-node setups: Supported Deployments Overview.
If these steps do not help to fix the issue with the Quest service on the Windows server, please reach out to our Support Team and make sure to specify the Sisense application and add-on version, and attach the quest.log file to your ticket.
