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

Permanent Solutions
- Resolve resource shortage
   Please make sure you have enough CPU/RAM resource on the QlikView Server Machine

- Rebuild corrupted performance counter library
   Please rebuild the performance counter library in Windows, see https://support.microsoft.com/kb/2554336

- Avoid file locking
   Please exclude QlikView files from anti-virus scanning

- Improve slow performance applications
   Please redesign those QlikView applications for better performance

Temporary Solutions
- Disable session recovery

- Disable performance logging 


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

In some cases, session recovery is taking a very long time due to a few slow expressions in the customer app. QlikView Server needs to evaluate expressions in the app during session recovery, for instance when we figure out which objects were minimized when the session was closed. So if an expression is very slow, session recovery is very slow. During session recovery, sometimes QVS is holding on to an internal lock associated with the document. The performance monitor indirectly needs to get this lock (to get document statistics), and is blocked. Technically it wasn’t stuck, it would eventually continue, but Phoenix can’t know that (it just has a timeout), and then restarts.