Json REST error in QMC

[Jonathan_Alm]

Hi,

when reloading a task in QMC all my rest calls fail with the following error (from qvrestconnector log file)

20180412T090328.438+02:00 [4] Product_Version=1.3.0 ERROR hostname=BLP-QLIKSENSE01 pipename=\\.\pipe\000017A0_000016B4_4CBE30DD_04429A84.pip

UserId=NA message=Error processing data:

System.Exception: The connection format is obsolete. Please edit your connection object and save it.

at Qlik.Connectors.Rest.Services.RestClient.PrepareRequest(RestConnectionProperties connectionProperties, WithConnectionOverrideParameters withConnectionOverrideParameters, PaginationOverrideParameters paginationOverrideParameters, CookieContainer cookieContainer)

   at Qlik.Connectors.Rest.RestDataReader.Read(BlockingCollection`1 sourceDataRows)

If I call on the rest api via Postman on the server, I get no error.

If I create an app in qlik sense desktop and call on the API, I get no error. If I import this app that I know works into the QMC and run it as a task, I get this error.

We are running Qlik Sense Febr 2018 release on both server and desktop.

The Data connection that the QMC creates after importing the file is:

CUSTOM CONNECT TO "Provider=QvRestConnector.exe;url=http://{URL}/api/platform/organisation-repository/v1/organisation;timeout=120;method=GET;autoDetectResponseType=true;keyGenerationStrategy=3;useWindowsAuthentication=false;forceAuthenticationType=false;useCertificate=No;certificateStoreLocation=CurrentUser;certificateStoreName=My;queryHeaders=hypernet-customerid%2SE60075;PaginationType=None;IsOffsetStartFieldHeader=false;IsOffsetCountFieldHeader=false;IsOffsetTotalPathHeader=false;IsNextTokenFieldNameHeader=false;IsNextTokenFieldPathHeader=false;IsNextUrlFieldPathHeader=false;"

It is the same connection that we use in Qlik Sense Desktop and in QlikView. Both works. It is only in the QMC that this error occurs.

Does anyone have any idea if this is related to settings in QMC?

Kind regards, Jonathan

[Jonathan_Alm · Accepted solution]

The solution was in the latest release note from Feb 2018 patch 1

The Qlik REST Connector has new security properties in the connection dialog. Existing connections must be modified to conform to the requirements of the new properties. The Qlik REST Connector supports the ability to include HTTP headers in the response object. Starting with the November 2017 release (version 1.2 of the REST Connector), loading of the headers does not happen by default. It must be explicitly allowed. Existing connections that load the response headers must be reconfigured with the Allow response headers parameter.

I had created my REST connections a while back and these were now not valid anymore. So I had to import new apps with new connections made. It was quite tedious but it worked