Skip to main content

"Failed to open document" message pointing to tunnel.dll call

No ratings
cancel
Showing results for 
Search instead for 
Did you mean: 
Sonja_Bauernfeind
Digital Support
Digital Support

"Failed to open document" message pointing to tunnel.dll call

Last Update:

Jun 1, 2021 4:10:03 PM

Updated By:

Andre_Sostizzo

Created date:

Mar 6, 2012 8:18:13 PM


Users have intermittent issue opening applications from the QlikView Access Point with IE Plugin client.  

Users see "Failed to open document".
The observed error message indicates issues with failing call to the tunnel.dll

Environment:

QlikView , all versions

 

Cause:

 

Port 4747 is not opened or is being blocked

The IE Plugin client communicates with the QlikView Server over port 4747. If tunneling isn't configured correctly in IIS, the error message will be returned. Tunneling is configured by default is using the QlikView Web Server.

TicketData.pgo file corruption

The TicketData.pgo file has become corrupted, and a new version needs to be created.  The TicketData.pgo file is transitory, so there is nothing in the file that will cause a loss of anything by recreating new versions.  You may also notice in the QVServer Event logs that one server is creating a ticket, but the other server is attempting to consume it but the ticket cannot be found, and the reason is the 'shared' TicketData.pgo file is not updating correctly so the clustered servers have access to all tickets generated.

Version mismatch between the QlikView Server and the IE Plugin client

If the build version of the QlikView Server does not match the version of the IE Plugin client, this error may be returned. This is more prevalent when using a newer version of IE Plugin, such as 12.40.20000, and attempting to connect to an older build version of QlikView Server such as 12.10.XX/12.20.XX.

 

Resolution:

Port 4747 available?

Verify that port 4747 is open. If port 4747 is blocked, QlikView will need to tunnel. If tunneling is not correctly configured, this will fail. 
To verify if tunneling is correctly configure, navigate to the following URL: http://<servername>/scripts/qvstunnel.dll?test 
See How To Configure Tunneling Using Microsoft Internet Information Server (IIS)  if IIS is used. 
Another option is to tick the Always Tunnel check box in QMX > System > Setup > QlikView Web Servers > QVWS@ > AccessPoint > Server Connections
Port 4747 being available is the preferred and recommended method. Tunneling should not be required. 


TicketData.pgo file corruption

Follow the steps below to confirm TicketData.pgo file is working properly:

  1. Go to C:\ProgramData\QlikTech\QlikViewServer and confirm the TicketData.pgo file timestamp is updating with each user login.
  2. Go to the location of your QlikView Server Root Folder path as specified in the Management Console under System\Setup\QlikView Servers\QVS resource\Folders tab, by default this will be C:\ProgramData\QlikTech\Documents to verify the copy of TicketData.pgo is also updating with each user login.
  3. If either of the above timestamped TicketData.pgo files is not updating, stop the QVS services on each server running them in the clustered configuration, and then remove all copies of the TicketData.pgo file and then restart the QVS services.  
  4. Verify all copies of TicketData.pgo are not updating as expected.  Generally the size of the TicketData.pgo will be 1KB, so another thing to check is the file size as well, and if it is larger than 1KB, this may also indicate a problem with the file, and Step 3 should be done as well.

Version mismatch between the QlikView Server and the IE Plugin client

There are two options depending upon if QlikView Desktop is also installed on the client computer.

  • Both QlikView Desktop is installed on the client computer as well as the IE Plugin client (Please note that the installation of QlikView desktop also installs the IE Plugin client by default)
    1. Uninstall both of the mismatched versions of the IE Plugin client and QlikView Desktop
    2. Reboot the client computer
    3. Install the build version of QlikView Desktop which matches the build version of the QlikView Server to ensure a version match
  • Only IE Plugin client is installed on the client computer
    1. Uninstall the mismatched version of the IE Plugin client
    2. In Windows File Explorer, rename the %ProgramData%\QlikTech directory (e.g. QlikTech.old)
    3. Install the IE Plugin client build version which matches the build version of the QlikView Server to ensure a version match
Labels (2)
Contributors
Version history
Last update:
‎2021-06-01 04:10 PM
Updated by: