Skip to main content
Woohoo! Qlik Community has won “Best in Class Community” in the 2024 Khoros Kudos awards!
Announcements
Nov. 20th, Qlik Insider - Lakehouses: Driving the Future of Data & AI - PICK A SESSION
cancel
Showing results for 
Search instead for 
Did you mean: 
Emmanuelle__Bustos
Partner - Specialist
Partner - Specialist

Restart QVS Error

Hi Qlikview Users,

Today in the morning we have an rare issue, the QVS Service restarted and all the NAMED CALS assignations were deleted so we had to assign all licenses to users again. The error found in the Events logs was:

2015-02-09 11:32:00    2015-02-17 08:34:25    1    300    Error    Restart: Server aborted trying to recover by restart. Reason for restart: No document purger activity for 120 seconds.

2015-02-09 11:32:00    2015-02-17 08:34:25    1    300    Error    Restart: Server aborted trying to recover by restart. Reason for restart: No document purger activity for 120 seconds

2015-02-09 11:32:00    2015-02-17 08:34:26    4    700    Information    Debug: Done Running

2015-02-09 11:32:00    2015-02-17 08:34:39    4    700    Information    Document PreLoad: Stop

2015-02-17 08:35:31    2015-02-17 08:35:34    4    700    Information    NUMA: QVS configured to get adapt to NUMA environment

2015-02-17 08:35:31    2015-02-17 08:35:34    4    700    Information    NUMA: NON-NUMA DETECTED

2015-02-17 08:35:31    2015-02-17 08:35:37    4    700    Information    WorkingSet: Configured Working Set Size is 5.600-7.200 GB (setting 70%-90%)

2015-02-17 08:35:31    2015-02-17 08:35:37    4    700    Information    Debug: Calling StartServiceCtrlDispatcher()

2015-02-17 08:35:31    2015-02-17 08:35:37    4    700    Information    Debug: Entering CNTService::ServiceMain()

2015-02-17 08:35:31    2015-02-17 08:35:37    4    700    Information    Debug: CNTService::SetStatus(14408208, 2)

2015-02-17 08:35:31    2015-02-17 08:35:37    4    700    Information    Debug: CNTService::SetStatus(14408208, 4)

2015-02-17 08:35:31    2015-02-17 08:35:38    4    700    Information    PGO: Creating file IniData.pgo


Does somebody know about this issue, I check another disscusion with the same Error but they got message:


2015-02-09 11:32:00    2015-02-17 08:34:25    1    120    Error    Restart: Server aborted trying to recover by restart. Reason for restart: No document purger activity for 30 seconds.


The difference Is the 30 seconds instead my 120 seconds and the error number es 120 instead mine 300.


I see in my Event logs after the restart is a record Information with the Pgo: Creating file IniData.pgo, i think in somehow the pgo were deleted that's why my assignation were deleted as well, some advice?

3 Replies
peter_turner
Partner - Specialist
Partner - Specialist

Hello Emmanuelle,

I've encountered similar behaviour before, but never been able to pin this down to anything specific.

There are a couple of general points you could do:

Make sure any anti virus software is set to exclude your QV server folders, specifically where the PGO files are stored, as the real time anti virus scan of some products can lock this PGO and cause problems for the QVS.

There are 2 copys of the PGO file (one is a backup) and they should both have the same filedate and time as they are synchronized, if there are different you have an issue with the PGO's and i'd recommend recording all your CAL information, stopping the QVS services and deleting the PGOs. They will then be re-created and you can re-assign the CALs again.

Last point is there are the Power Tools on the community, one will allow you to backup the CAL information and restore it back at a later time, very useful if you have many CALs to assign and don't want to-do them individually.

jerrysvensson
Partner - Specialist II
Partner - Specialist II

Some nice person installed anti virus software on your server this weekend? 🙂

Emmanuelle__Bustos
Partner - Specialist
Partner - Specialist
Author

Hi Peter

This was one point I considered and we have created rules of exception for the antivirus to avoid it block or corrupt the PGO files, as you said it looks like there is not the correct thing that caused the issue yet.