Qlikview Error | Server & Access Errors

Dealing with Server & Access Errors in QlikView can be frustrating because the cause is often hidden in the background services.

Since these errors usually prevent users from even seeing their dashboards, we need to look at the infrastructure side.

Here are the most common “Server & Access” culprits and how to tackle them:

1. “No Connection” or “Communication Lost”

This usually happens when the QlikView Web Server can’t talk to the QlikView Server (QVS) service.

• The Fix: Open services.msc on the server. Ensure the QlikView Server and QlikView WebServer services are “Running.” If they are, try restarting the Web Server service first.
• Check the Port: Ensure port 4747 (used by QVS) isn’t being blocked by a recent firewall change.

2. “Failed to Load (Local/Server)”

If a specific document won’t open but others will, the issue is likely a corrupted metadata file.

• The Fix: Go to the folder where the .qvw is stored. Look for a file with the same name but a .shared or .puna extension.
• The Test: Temporarily move the .shared file to a different folder and try opening the app again. If it opens, the shared file (which stores user bookmarks and objects) was the problem.

3. “Access Denied” or “Linked Document Not Found”

This usually points to a permissions or licensing bottleneck.

• The Fix: Check the QlikView Management Console (QMC):
  • CALs: Ensure the user has an assigned Client Access License (Named or Document CAL).
  • NTFS Permissions: Ensure the service account running QlikView has “Read” and “Write” access to the actual folder where the files live.

4. “Tunneling” Errors

If you are accessing QlikView from outside a local network (like a VPN), the connection might be timing out.

• The Fix: Check if QlikView Tunneling is enabled in the QMC under Web Server > Settings. Sometimes, toggling this or checking the timeout settings (usually set to 30 or 60 seconds) resolves drops.

FAQs