'This page isn't working' error when opening a specific Qlikview Application

[duzford13]

We have two applications that have been in production for years.  This week users noticed that when they try to open the app they given an error that states 'This page isn't working  <access point path> didn't send any data  ERR_EMPTY_RESPONSE'.    The apps are reloading with no problem from the QMC and we can open them without error on the server directly.   Out of hundreds of apps, these two appear to be the only ones affected. One of them is a binary load off the other, so it makes sense that they are linked.  We have tried to restore backup copies from a couple of weeks ago, but those also show the same issues on the Access Point.  We have an additional load balancer on top of the Qlik load balancer to help direct traffic. The only thing that has changed is that users now go to https instead of http and are redirected. We have not changed to https within QV yet.  Any ideas or help would be very appreciated!!

[Chip_Matejowsky]

Hi @duzford13,

Ensure that the QlikView Server logs are configured as detailed in article Best Settings for QlikView Server Logs to Troubleshoot Issues.  Then reproduce the issue and review the QVS Events log, for the time stamp and userID of when you attempted to open the app.  By default, the QVS logs are stored in %ProgramData%\QlikTech\QlikViewServer.  If you have configured the QVS logs to be written to a different location, you can check for the location in QMC > System > Setup > QlikView Servers > QVS@ > Logging tab > Log folder.

Also review the QVWS logs.  The default location for the web server logs is %ProgramData%\QlikTech\WebServer\Log.

If you need assistance with errors you find in the logs, post questions back here and attach the logs if you can.

Best Regards

[duzford13 · Accepted solution]

Thank you @Chip_Matejowsky! We could not find any records in any of the logs for those attempts. We found that it did have something to do with the initial load balancer being pushed to https. I think it wasn't even hitting the service to ever create a record in the log files. We rolled back that change and now things are working. We just have to identify what is going on in those apps that https doesn't like. 

[Chip_Matejowsky · Accepted solution]

Hi @duzford13,

Okay, glad you were able to roll back and able to somewhat identify the issue being with the load balancer.  One requirement for QlikView to play well with a load balancer is that Sticky Sessions need to be enabled on the LB.  Refer to article Clustering QlikView Servers With Load Balancing Of Webservers for more details.

Best Regards