Qlik Community

QlikView Deployment

Discussion Board for collaboration related to QlikView Deployment.

atsushi_saijo
Contributor II

QlikView Client Disconnection Issue with QVP://(Server) | Server communication lost, closing document!

I started investigation on the disconnection issue between QlikView server and QlikView client.

Very much often we currently experience such error, like every 10-15 mnutes. It is highly possible that this is related to the Client-Server communication.

Dev 28-Mar-17 0  48.29.jpg

On QVS, document timeout is 480 min.

DocumentTimeOutSetting.shf.jpg

Also in QVS, session timeout is set to none. But disconnection is recurring.

AnotherSetting.shf.jpg

All the server services are running normally.

Dev 28-Mar-17 0  68.36.jpg

License leasing is properly executed. Users can open documents in OpenInServer, and explore for 10-15 minutes. Then disconnection comes.

To start investigation, we have prepared WireShark to monitor TCP communication on the test server. Now, what port should we watch for such error? What type of keep-alive mechanism could we implement?

To be safe side, we have disabled Add-on Congestion Control Provider on WIndows Server 2008 R2.

[Old Config]

Old.jpg

[New Config]

New.jpg

I should highly appreciate for any feedback/advices.

1 Solution

Accepted Solutions
atsushi_saijo
Contributor II

Re: QlikView Client Disconnection Issue with QVP://(Server) | Server communication lost, closing document!

This turned out (the certitude is not 100%) to be insufficient hardware resource. This symptom was observed in a specific client, where reloading and pubslishing takes place withn single server host. At certain moment, the system resource maxed out, and user experiences disconnection.

1 Reply
atsushi_saijo
Contributor II

Re: QlikView Client Disconnection Issue with QVP://(Server) | Server communication lost, closing document!

This turned out (the certitude is not 100%) to be insufficient hardware resource. This symptom was observed in a specific client, where reloading and pubslishing takes place withn single server host. At certain moment, the system resource maxed out, and user experiences disconnection.