Unlock a world of possibilities! Login now and discover the exclusive benefits awaiting you.
Hi,
In a two-server cluster environment, sometimes users get an immidiate "no connection" error. When they refresh the page for several times then they finally succeed to open the document. Next time , they may or may not get the same error message. It totally depends on something unknown for now. All we could track is the web server logs generated at the same time this error occurs like:
.....
Create client: Mode=Authenticate, Host=sparrow:4747, ClientIP=10.250.20.80, MachineId=3fb55203-8987-4789-a3ff-d981174f1044, Slot=
Warning: m_Sock.Receive throws zero
.....
Is there any specific description of "Warning: m_Sock.Receive throws zero" record in the generated Web Server logs.
Hi,
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,
Main Cause:
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:
Hi,
I haven't heard that before.
But I would suggest you to start you services by selecting Automatic (Delayed Start)
Regards
ASHFAQ
You may have to check the services and restart them whenever the No connections message displays.
Hi,
Thanks for your comments. But the error that I receive is "No connection" not "No Server" message.
I think that windows services have nothing to do with this problem. All services are up and running all the time.
Few days before our clients reported seeing "No Connection" message like below on the Access Point. We restarted the QlikView Server and it worked. If it is happening consistently with your environment then I think you may have to check the QlikView server.
HI,
this problem hast to do with the qlik view services on your server when you start them new everything should work fine again. We used to have the same problem and we solved it by restarting the services every night.
In our case the problem was theat our ram on the server was full.
regards,
MT
Hi,
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,
Main Cause:
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: