Skip to main content
Announcements
NEW: Seamless Public Data Sharing with Qlik's New Anonymous Access Capability: TELL ME MORE!

Open in Server fails using QlikView Desktop May 2023 or later against earlier version of QlikView Server

100% helpful (1/1)
cancel
Showing results for 
Search instead for 
Did you mean: 
Chip_Matejowsky
Support
Support

Open in Server fails using QlikView Desktop May 2023 or later against earlier version of QlikView Server

Last Update:

Jun 29, 2023 7:34:43 AM

Updated By:

Sonja_Bauernfeind

Created date:

Jun 29, 2023 7:34:43 AM

Using Open in Server in QlikView Desktop to connect to a QlikView server fails with: 

Connected to server OK, No reply received
Switching to HTTPS tunnelling
Connected to server OK, Security settings denies access
Switching to HTTP tunnelling
Connected to server OK, No reply received

connected to server ok no reply received.png

The Desktop client is running version May 2023 (12.80) or later, while the QlikView server is a previous version, such as May 2022 (12.70).  

 

Resolution

If QlikView Desktop and QlikView Server are running different versions, either upgrade the lower version to match the higher version or set the correct and same session algorithm in the Settings.ini file to resolve the discrepancy.

For issues where the QlikView Desktop is running version May 2023 (12.80) and the QlikView Server is running version May 2022 (12.70) or earlier, the QlikView Desktop settings.ini file must contain the entry SessionAlgorithm=CALG_AES_128.

Modify the QlikView desktop client settings.ini to add SessionAlgorithm=CALG_AES_128. For information on how to modify the settings.ini, see: How to change the settings.ini in QlikView Desktop and QlikView

QV Desktop Settings ini session algorith.png

Cause

The discrepancy in the session algorithm causes the error. QlikView May 2023 (12.80) now uses AES256 encryption instead of AES128, which was used in QlikView May 2022 (12.70) and earlier. 

Related Content 

What's New in QlikView May 2023?
QlikView 12.80: set a different Session Algorithm for QVP communication
Communication to QlikView server fails: Switching to HTTPS tunneling 
QlikView Client connection fails with Connected server OK, negotiations timed out Switching to HTTP ... 

Internal Investigation ID(s)

QV-24861

 

Environment

QlikView 

Labels (1)
Comments
josemanzod
Contributor III
Contributor III

Thank you, Very useful.

alexqin
Contributor
Contributor

what if my desktop version is 12.2 and the version on the server is 12.8?

which file should I modify?

p_verkooijen
Partner - Specialist II
Partner - Specialist II

@alexqin Then you will have to update the Desktop version to 12.8

Johannes_Becker
Partner - Contributor
Partner - Contributor

Hi,

we have 12.8 on both Server and Desktop. This worked until very recently. Now we're getting the above error.

Any ideas?

Cheers,
Hannes

Chip_Matejowsky
Support
Support

@Johannes_Becker,

Since both QlikView Server and QlikView Desktop are version 12.80, it is not likely due to the encryption discrepancy between 12.80 and earlier versions listed in this article. 

Suggest you refer to article QlikView Troubleshooting License Lease issues, and ensure port 4747 open on the computer running QlikView Desktop.

Best Regards

Vajid
Contributor III
Contributor III

@Chip_Matejowsky QV server and QV desktop is in same instance, still am not able to lease license in QV desktop. QV server and QV desktop version is May 2023 SR2.

Chip_Matejowsky
Support
Support

@Vajid 
Suggest you start a thread in the QV Management forum and provide a screen capture of the issue, inform if issue is occurring for all QV Desktop clients or just a specific one(s) and also review article Troubleshooting QlikView License Lease Issues.

Best Regards

Version history
Last update:
‎2023-06-29 07:34 AM
Updated by: