article QlikView Server crashes with Error Restart: Server aborted trying to recover by restart in Official Support Articles

QlikView Server crashes with Error Restart: Server aborted trying to recover by restart

Sonja_Bauernfeind — Mon, 03 May 2021 07:26:47 GMT

The QlikView Server service may crash with:

Restart: Server aborted trying to recover by restart

Depending on additional log information, different root causes can be identified.

Environment:

Resolution

Resource Bottleneck or Performance Counters corrupted

Restart: Server aborted trying to recover by restart
Reason for Restart: Phoenix detected: Performance Monitor Stuck

Resolve resource shortage
Monitor CPU and RAM usage on the QlikView Server host to identify bottlenecks.
Rebuild corrupted performance counter library
See Error 1067 when starting QlikView services
Avoid file locking
Exclude QlikView files from anti-virus scanning
See QlikView Folder And Files To Exclude From Anti-Virus Scanning
Improve slow performance applications
QlikView Applications may need to be reviewed to identify performance optimisation opportunities
Disable Session Recovery
See Session Recovery in QlikView: How to enable it and how it works

No document purger

Restart: Server aborted trying to recover by restart
Reason for restart: No document purger activity for 120 seconds.

This can occur in some cases where the user has an application with a large number of objects.

QlikView automatically saves and loads the objects layout state in every reload. When this takes longer than 2 minutes, the Restart error appears.

The Layout State can be disabled from 11.20 SR13 onwards.

The default behavior can be changed by modifying the EnableApplyLayoutState setting in the QlikView Server settings.ini file, where 1 (default) = Enabled and 0 = Disabled.

As it is enabled by default this has to be set to 0 (for Desktop users this can be configured also from the Easter Egg menu).

In a QlikView Server environment, the setting is applied with the following steps:

Stop the QlikView Server service
Navigate to C:\ProgramData\QlikTech\QlikViewServer
Locate the settings.ini
Open in a text editor
Add the line EnableApplyLayoutState=0 inside the [Settings 7] section and above the [Authentication] section.
Start the QlikView Server service

Re: QlikView Server crashes with Error Restart: Server aborted trying to recover by restart

hinamasu — Mon, 05 Feb 2024 02:42:44 GMT

Hello @Sonja_Bauernfeind

The QlikView Server has crashed and the following error message was displayed in the log file.
------------------------------------------------------------------------------------------------------------
Restart: Server aborted trying to recover by restart.
Reason for restart: No GDIPlusChecker activity for 30 seconds
------------------------------------------------------------------------------------------------------------

As a resolution for this error, is the parameter "EnableApplyLayoutState=0" mentioned in the description of "No document purger" valid?

Also, are there any negative effects when setting this parameter?

Re: QlikView Server crashes with Error Restart: Server aborted trying to recover by restart

Sonja_Bauernfeind — Mon, 05 Feb 2024 08:34:56 GMT

Hello @hinamasu

This is difficult to answer without more context. The Layout State setting may not apply here at all. No GDIPlusChecker activity for 30 seconds is often seen during resource issues and so I would recommend reviewing Troubleshooting QlikView Server resource problems and crashes.

If you need more assistance, please post about the issue in the QlikView Administration forum, with details on your versions and setup and the errors you are seeing.

All the best,
Sonja

Re: QlikView Server crashes with Error Restart: Server aborted trying to recover by restart

hinamasu — Tue, 06 Feb 2024 01:02:33 GMT

Hello @Sonja_Bauernfeind

Thank you for your prompt response.

I will refer to the URL you introduced.

It seems to be very useful information, thank you.

Best regards,
hinamasu