Qlik Sense May 2023 Patch 3 causes REST connection error: "WITH CONNECTION" is not allowed

[Benoit_C]

After an upgrade to Qlik Sense Enterprise on Windows May 2023 patch 3 or later, REST connections fail with the following error: 

"WITH CONNECTION" is not allowed. To allow "WITH CONNECTION", select Allow "WITH CONNECTION" in the connector settings.

The Allow WITH CONNECTION option is not exposed in the REST Connector GUI and cannot be changed.

Qlik Sense Enterprise on Windows August 2023 and later are not affected.

Resolution

To resolve the issue, upgrade to August 2023.

To manually mitigate the issue in the May release branch, replace the  qsdfw_qsefw_qlikview.qliksourceconfig file. Qlik is investigating a solution which does not require manual intervention.

Backup the affected file before continuing with the workaround. When taking the backup, do not keep the backed up file in the same folder. (see end notes)

1. On each Qlik Sense Server node, navigate to: C:\Program Files\Common Files\Qlik\Custom Data\QvRestConnector\
2. Locate qsdfw_qsefw_qlikview.qliksourceconfig
3. Replace qsdfw_qsefw_qlikview.qliksourceconfig with the file attached to this article. 
4. This resolves the issue. 
   
   Subscribe to this article or monitor the release notes for information on an automated fix.
   
   

   This change must be done on all nodes and schedulers.

End notes:

The folder C:\Program Files\Common Files\Qlik\Custom Data\QvRestConnector can only contain one qliksourceconfig file with correct name: qsdfw_qsefw_qlikview.qliksourceconfig

If there are two qliksourceconfig files (even with different names, such as a backup), the first one in alphabetical order will be chosen.

Cause 

QB-20735

Environment

Qlik Sense Enterprise on Windows May 2023 Patch 3 and later 

Does not affect August 2023 and later releases.

Internal Investigation ID(s) 

QB-20735

[fmarvnnt]

Only Qlik Support can publish such a kind of list.

Sorry,

FMa

[Sonja_Bauernfeind]

@fmarvnnt @LDR @ssolli 

We are actively reviewing the status of the fix. I will update the article with news once I have it.

All the best,
Sonja 

[Oliver_GER]

@Sonja_Bauernfeind Is there an ETA for this fix? This issue became a blocker in one of our projects and now we have to make a final decision to wait or implement a timeconsuming workaround.

[peter_turner]

This affects SR5 also.

The workaround listed did resolve the problem for our customer's specific environment.

[Sonja_Bauernfeind]

Hello @Oliver_GER 

It is still actively being worked on and a path forward has been identified. I have no ETA just yet, but will update this article once we know more.

All the best,
Sonja 

[Lech_Miszkiewicz]

HI @Oliver_GER 

Workaround provided here is working so there shouldn't be any blocker for you - just replace the file and you are good to go. It does not even require reboot or anything - just single copy/paste of the file as per instructions in this article.

cheers

[Skage]

Does the May 2023 Patch 6 include a fix for this problem?

[Sonja_Bauernfeind]

Hello @Skage 

I will re-investigate for you, but I do not believe it is included in SR6. Once I know more, the article will be updated accordingly. 

All the best,
Sonja 

[Eduardo_Monteiro]

This issue is fixed on August 2023 Patch 2!

Regards,

[EAQLIKSUPPORT]

looks like this issue has been not fixed in May 2023 Patch 6.