We are also restarting all services every night but this doesn't help.
It is stated by QlikTech Support that this problem is resulted from a sync issue of "TicketData.pgo" file among cluster nodes. We have figured out that some of our Ticketdata.pgo files are not updating so we had to remove and have QVS's recreate them.
Many thanks for your comments,
The TicketData.pgo file has become corrupted or out of sync, and a new version needs to be created.
There is nothing in the file that will cause a loss of anything by recreating new versions. You may also
notice in the QlikView Server Event logs that one server is creating a ticket and the other server is
attempting to consume it but the ticket cannot be found. The reason is the 'shared' TicketData.pgo file is
not updating correctly so the clustered servers will not have access to all tickets generated.
After following the below instructions, the problem has gone:
- Go to C:\Documents and Settings\All Users\Application Data\QlikTech\QlikViewServer (Server 2003) or C:\ProgramData\QlikTech\QlikViewServer (Server 2008) and confirm the TicketData.pgo file timestamp is updating with each user login.
- Go to the location of your QVServer Root Folder path as specified in the Management Console under System\Setup\QlikView Servers\QVS resource\Folders tab (default is C:\Documents and Settings\All Users\Application Data\QlikTech\Documents [Server 2003] or C:\ProgramData\QlikTech\Documents [Server 2008]). Verify the copy of TicketData.pgo is also updating with each user login.
- If either of the above TicketData.pgo files is not updating (check timestamp), stop the QVS services on each server running in the clustered configuration.
- Remove all copies of the TicketData.pgo files.
- Restart the QVS services.
- Verify all copies of TicketData.pgo are now updating as expected