Skip to main content
Announcements
Have questions about Qlik Connect? Join us live on April 10th, at 11 AM ET: SIGN UP NOW

Qlik Sense Management console shows Engine status unknown, never contacted

No ratings
cancel
Showing results for 
Search instead for 
Did you mean: 
Sonja_Bauernfeind
Digital Support
Digital Support

Qlik Sense Management console shows Engine status unknown, never contacted

Last Update:

Aug 25, 2020 2:37:30 AM

Updated By:

Sonja_Bauernfeind

Created date:

Jul 28, 2019 4:44:46 PM

The Qlik Sense Engine stopped responding or an engine has been reinstalled. 

In the Qlik Sense Management Console (QMC) start page, an error is indicated. Reviewing the Nodes section shows the following status: 

Engine status unknown, never contacted

Environment: Qlik Sense any version 
 

Resolution:


Basic verification

  • Verify that Port 4444 is open between the Qlik Sense Enterprise Central Node and the Rim node.
  • Verify that the Service account is added to the Local Administrators Group
  • Restart the Qlik Sense Services 

 

Repair performance counters

  • Navigate to the Node showing that status.
  • In a Windows file explorer locate the following folder:  C:\ProgramData\Qlik\Sense\Log\Repository\Trace
  • Open the file *_System_Repository_* trace file and at the bottom will be an ERROR row with the following message in the string:


Unhandled exception: Value cannot be null.↵↓Parameter name: source↓System.ArgumentNullException: Value cannot be null.

Follow these steps to resolve the problem:

  1. Stop all the Qlik Sense services on the affected node.
  2. Open an elevated command prompt
  3. Type the following at the command prompt
    • C:\Windows\System32> cd ..\syswow64
    • C:\Windows\SysWOW64> lodctr /R
    • The following message will be displayed:

      Info: Successfully rebuilt performance counter setting from system backup store  C:\Windows\SysWOW64>

  4. Start the Qlik Sense services on the Node
  5. Check the QMC, the node Status should change to # of # services are running.

 

Cause:

  • The Central node may require a reboot to ensure communication after a newly installed RIM node. 
  • Ports may not have been opened correctly or the user account does not have sufficient privileges.
  • Windows performance counters were damaged. 
Labels (1)
Contributors
Version history
Last update:
‎2020-08-25 02:37 AM
Updated by: