Skip to main content
Announcements
Join us at Qlik Connect for 3 magical days of learning, networking,and inspiration! REGISTER TODAY and save!
cancel
Showing results for 
Search instead for 
Did you mean: 
rhodamineb1
Contributor II
Contributor II

Failed to read data at {0:x}

Hi,

I got a demo from Qlik. I created an app on QlikCloud and connected it to my Mysql database. Then I loaded my databese on data manager but when I try to import my tables into app, I recieve an error like “failed to read data at {0:5}” It only happens on some tables (especially sales and customers) other tables are being imported without a problem. Screenshot_3.pngThanks in advance.

Labels (2)
1 Solution

Accepted Solutions
PadmaPriya
Support
Support

Hi @rhodamineb1 

 

here is an article that could be helpful around size limit in Qlik Sense Enterprise SaaS:

https://community.qlik.com/t5/Deployment-Management/SaaS-error-memory-limit-for-request-was-reached-...

 

Thanks,

Padma Priya

Help users find answers! Don't forget to mark a solution that worked for you! If already marked, give it a thumbs up!

View solution in original post

3 Replies
PadmaPriya
Support
Support

Hi @rhodamineb1 

 

here is an article that could be helpful around size limit in Qlik Sense Enterprise SaaS:

https://community.qlik.com/t5/Deployment-Management/SaaS-error-memory-limit-for-request-was-reached-...

 

Thanks,

Padma Priya

Help users find answers! Don't forget to mark a solution that worked for you! If already marked, give it a thumbs up!
Ken_T
Specialist
Specialist

I am pretty sure this is not a size limit related issue.
I am seeing this same error in QDT. for some data sources but not all. 
i see it for some tables in a postgresql db and not for others.


did you ever get this resolved?
I saw an error about column data type is not supported earlier, 

unable to show the preview column. User does not have permission to access data, or column data type is not supported

and then when permission issue was fixed in the DB, then the “failed to read data at {0:5}” error happened. 


NicolasAimain1
Partner - Contributor III
Partner - Contributor III

For those who encounter this problem, one solution is to convert data on SQL side

I had the same problem on several field but it worked when I excluded these fields or limited the amount of row loaded

I manage to load the full dataset using CONVERT(<my_field>,CHAR) as <my_field> during the SELECT on each field that had an error

Regards