topic Re: Access point Tunnel issue in QlikView

Access point Tunnel issue

elie_issa — Wed, 01 Nov 2017 10:47:15 GMT

Dear All,

Please find below the error shown when trying to access the qlikview dashboard from the access point.

For more info we have one live server and one cluster server linked to each others to give better performance and balance if many users are accessing the dashboards.

What it could be the cause of such error ?

Thanks a lot

Re: Access point Tunnel issue

cristinapo — Wed, 01 Nov 2017 16:06:28 GMT

Hi Ellie, is this the first time you try to access it in Access Point? Maybe you don't have access.

Re: Access point Tunnel issue

Chip_Matejowsky — Wed, 01 Nov 2017 16:48:21 GMT

Hello Elie,

Can you please provide greater clarity on this issue?

QVW is hosted on the AccessPoint and end-user is attempting to open it and receives the tunneling.dll error?
What client is the end-user using? I presume it's the IE Plugin.
Does the AJAX client work without issue?

The IE Plugin client uses the QVP protocol to communicate from the client to the QVS server. The QVP protocol strictly uses port 4747 for communication. If port 4747 is not open, then communication will "tunnel" via port 80/443. Tunneling does have to be configured on the QlikView Server and IIS server if using IIS as webserver.

Check QMC > System > Setup > QlikView Web Servers > QVWS@ > AccessPoint tab > Server Connections tab. Is the Always Tunnel checkbox ticked?

You can use the Telnet command to test if port 4747 is open.
1. Open a command prompt on client computer

2. Enter: Telnet <servername or IP address> port 4747

3. If a cursor is returned, then port is open; if something other than cursor is returned, then port is not open

If Telnet is not enabled on computer:

1. Click Start > Control Panel

2. Click Programs

3. Click Turn Windows Features on or off

4. In Windows Features dialog box, tick the Telnet Client check box

5. Click OK to allow system to install the client

6. Perform the Telnet command described above

Hope this helps,

Chip

Re: Access point Tunnel issue

elie_issa — Thu, 02 Nov 2017 09:11:01 GMT

Always Tunnel checkbox was not ticked. should we restart the server after we check it ?

Re: Access point Tunnel issue

elie_issa — Mon, 06 Nov 2017 08:27:10 GMT

Hi Chip,

I tested the access to port 4747 on my Server and it worked properly.

but still we are facing the tunnel issue again and again.

It could be from the IE Plugin ?

Any alternate solution ?

Thanks again.

Re: Access point Tunnel issue

Chip_Matejowsky — Mon, 06 Nov 2017 18:49:23 GMT

Hey Elie,

Did you confirm what client users are using when error is received? If IE Plugin client only, is port 4747 opened on those users's computers? Did you confirm if AJAX client works?

I have seen the tunnelling.dll issue when the external name of the server differs from the internal name. This is mitigated by the

Check QMC > System > Setup > QlikView Servers > QVS@ > General tab > Link Machine Name field. See the below definition of Link Machine Name from the online QlikView Help:

If the QlikView Server cluster is not exposed externally with the same name as is used internally, an external name must be entered in this text box. This is to enable QlikView documents in the Microsoft Internet Explorer plugin. To mimic the behavior of version 8.5, it is possible to enter (FromRequest) (including the parenthesis) in this text box. The name exposed externally will then be the same as the URL that the client uses to connect to the QlikView AccessPoint, that is, the setting is taken from the request coming from the client.

Hope this helps,

Chip

Re: Access point Tunnel issue

elie_issa — Tue, 07 Nov 2017 07:50:28 GMT

Hey Chip,

Below is the link machine name empty. do you suggest to put same name for the two servers or we have to do anything else ?

Thanks.

Re: Access point Tunnel issue

Chip_Matejowsky — Thu, 09 Nov 2017 13:56:35 GMT

Hey. Would suggest that you enter (FromRequest)

Re: Access point Tunnel issue

hani_saghir — Thu, 11 Jan 2018 15:21:35 GMT

check the TicketCal.PGO and XML files, if they are corrupt, they can cause this behavior.

you need to back them up and delete them, the system will recreate them. this did the trick in our environment.