Qlik Community

QlikView Performance

Discussion Board for collaboration on QlikView Performance.

Highlighted
shayraber
Contributor

Restart: Server aborted trying to recover by restart. Reason for restart: Phoenix detected: Performance monitor stuck

any idea why it happened?

the error is:

"Restart: Server aborted trying to recover by restart. Reason for restart: Phoenix detected: Performance monitor stuck"

QV server 11.2 SR3

on Win server 2008 R2

144GB RAM and 8 cores

1 Solution

Accepted Solutions
Employee
Employee

Re: Restart: Server aborted trying to recover by restart. Reason for restart: Phoenix detected: Performance monitor stuck

The Phoenix component of the QlikView Server works as a watchdog. If the Phoenix determines that some other QlikView component has gotten stuck, it restarts the service. The performance monitor is one such component.

To resolve the issue, please consider the below steps:

  • Rebuild the Windows performance counters as outlined in Microsoft KB article 2554336: https://support.microsoft.com/en-us/kb/2554336
  • Disable Session Recovery in the QMC > System > Setup > QlikView Servers > QVS@ > Documents tab > untick "Allow Session Recovery" checkbox
  • Ensure that all QlikTech directories and file types are explicitly excluded from any anti-virus and/or system scanning applications
  • Ensure that the Windows Server running QlikView Server is robust enough to provide enough system resources to allow QlikView Server to run optimally
  • Review/re-design QlikView applications to ensure that any expressions are optimized and that there are no Cartesian products and minimal data islands
Sr. Technical Support Engineer with Qlik Support
2 Replies
awhitfield
Esteemed Contributor

Re: Restart: Server aborted trying to recover by restart. Reason for restart: Phoenix detected: Performance monitor stuck

Hi Shay,

check out this extremely long posting:

https://community.qlik.com/thread/21360

It might help!

Andy

Employee
Employee

Re: Restart: Server aborted trying to recover by restart. Reason for restart: Phoenix detected: Performance monitor stuck

The Phoenix component of the QlikView Server works as a watchdog. If the Phoenix determines that some other QlikView component has gotten stuck, it restarts the service. The performance monitor is one such component.

To resolve the issue, please consider the below steps:

  • Rebuild the Windows performance counters as outlined in Microsoft KB article 2554336: https://support.microsoft.com/en-us/kb/2554336
  • Disable Session Recovery in the QMC > System > Setup > QlikView Servers > QVS@ > Documents tab > untick "Allow Session Recovery" checkbox
  • Ensure that all QlikTech directories and file types are explicitly excluded from any anti-virus and/or system scanning applications
  • Ensure that the Windows Server running QlikView Server is robust enough to provide enough system resources to allow QlikView Server to run optimally
  • Review/re-design QlikView applications to ensure that any expressions are optimized and that there are no Cartesian products and minimal data islands
Sr. Technical Support Engineer with Qlik Support
Community Browser