Skip to main content
Announcements
Have questions about Qlik Connect? Join us live on April 10th, at 11 AM ET: SIGN UP NOW
cancel
Showing results for 
Search instead for 
Did you mean: 
Not applicable

Error: File .\extdata.cpp - failure


Hi,

While reloading one QVD generator doucment which fethces data from DB, it throws the below error:

" Error: Error: File .\extdata.cpp, Line 1828 "

Could any one suggest the root cause and the resolution of this failure?

6 Replies
Not applicable
Author

Hi,

I have a similar issue reading from a PostgreSQL database using an ODBC connection.

Normal 0 21 false false false NL X-NONE X-NONE MicrosoftInternetExplorer4

Error: File .\extdata.cpp, Line 1826

SQL SELECT *

FROM <...>

Original script:

Table:

LOAD *;

SQL SELECT *

FROM "database"."public".tabel;

suniljain
Master
Master

is this error comes when extractiong data from sap-bw ?.

Not applicable
Author

Not mine, but I also seem to have found the solution.

On the server there was only 0.8GB memory free of the 6GB total. Other users are busy doing their things on the server as well.

So I will wait till this evening or lateron this weekend to try again.

I tested it with a much smaller selection of the same source and that works nicely.

Not applicable
Author

Hi,

I also had the same problem while loading data from Oracle DB.

What I did is, I splitted up the script into two parts in two QVD generators. One QVD generator with the Query which was getting failed and the other with the rest of the Query.

I made two separate tasks for the two QVD generators making one task dependent of the other.

I ran the splitted up generators at different points of time in a day, and inspite of the huge data volume the tasks ran successfully.
Currently also the tasks are running successfully everyday.

crusader_
Partner - Specialist
Partner - Specialist

Hi, I have this error querying from SAP BW.

Do you have any ideas what could be a reason?

Thanks.

Regards,

Andrei

Not applicable
Author

For troubleshooting it is recommended to run the failing query in a third party SQL query tool, with the following considerations.

  • Use the same ODBC or OLEDB connection
  • Use the same underlying database driver
  • Access the same database server
  • Use the same user credentials, username and password. NOTE: Use the QlikView service user if issue is related to QlikView Server

The third party tool should return an unexpected result. In this context pay extra attention to that the field names are exactly as expected and in readable language without garbage characters.

Common resolution is to correct SQL query so that a valid and expected result is returned by database.

The error message comes from QlikView engine and is related to the database result not having valid fields. Typically this is due to the usage of LOAD * , which means that QlikView will parse the resuls in order to find the returned field names. For some reason the data base has not returned a valid result, most likely due to database driver issues or an invalid SQL query.  If this does not resolve your issue, please log a case with Qlik Support.  However if it does, please mark this as the correct answer.