Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 
viralkmehta1968
Partner - Contributor II
Partner - Contributor II

Qlik GeoAnalytics Connector gives error

Hi,

I have a Qlik Sense App that uses Qlik GeoAnalytics Connector to plot utility consumption by location (uses Lat/Long).

It has been working fine until now and now the reload task is giving errors. This is happening in both DEV and PROD instances. The error message in the document script log is as follows:

2019-05-21 12:00:36 0741 LIB CONNECT TO 'UD Location Geo Data'
2019-05-21 12:00:36 Connected.
2019-05-21 12:00:36 0744 [GeoData_newark]:
2019-05-21 12:00:36 0745 SQL SELECT [UD_Build_1] as [^BldgKey], [Geometry] FROM Load(dataset='Dataset')
2019-05-21 12:00:36 0746 DATASOURCE Dataset GEOFILE url='file:///E:/Qlik/Group Connections/FACILITIES/Common_Data/UDEL_GEO_DATA/Newark/UD_Buildings.zip', keyField='UD_Build_1', type='shape', expectedGeomType='polygon', encoding='', crs='EPSG:3857'
2019-05-21 12:00:37 Error: Connector reply error: QVX_SYNTAX_ERROR: *null
2019-05-21 12:00:37 Execution Failed
2019-05-21 12:00:37 Execution finished.

Any idea why this would happen? To my knowledge there are no changes to the DEV and PROD Qlik Sense environments.

Thank you,

Viral Mehta

 

 

Labels (2)
1 Solution

Accepted Solutions
Patric_Nordstrom
Employee
Employee

Sorry about that, this was due to a problem with the license server. It has been corrected during the day and should work fine now.

Thanks,
Patric

View solution in original post

5 Replies
lironbaram
Partner - Master III
Partner - Master III

hi 

usually errors in the script , means you have some problem with the geometry

 if you have a line with null value in geometry or ID it'll cause an error

viralkmehta1968
Partner - Contributor II
Partner - Contributor II
Author

Hello,

Thanks for the reply. The geometry has not changed and the reload task has been running successfully until 2 days ago.

Thank you,

Viral

 

Patric_Nordstrom
Employee
Employee

Sorry about that, this was due to a problem with the license server. It has been corrected during the day and should work fine now.

Thanks,
Patric
viralkmehta1968
Partner - Contributor II
Partner - Contributor II
Author

Thank you, Patric.

The issue is resolved now.

Timmie
Contributor
Contributor

Hi Patric, we are experiencing the same issue again. Can you please take a look at the license server?

Thank you!

Timmie