Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Want to see what's currently in public preview? We've pulled it all together in one place. Check it out here
cancel
Showing results for 
Search instead for 
Did you mean: 
Not applicable

Error: Error: File .\extdata.cpp, Line 1826 when using QEMC





Hi,

I'd this simple script and was able to run successfully using Qlikview on my desktop.

LOAD *;
SQL SELECT *
FROM ProdSite.dbo.EmployeeVw;
STORE KPMGEmployeeVw into \\sgsgaapp18\C$\Data\Test\EmployeeVw.qvd;



However, when I tried to scheduled the same script using QlikView Enterprise Management Console and I got the following error message. This error only happened to this particular table, I tried using another table & it ran through successfully.

06/12/2010 11:17:02 AM: 0016 LOAD *
06/12/2010 11:17:02 AM: 0017 SQL SELECT *
06/12/2010 11:17:02 AM: 0018 FROM ProdSite.dbo.EmployeeVw
06/12/2010 11:17:03 AM: Error: Error: File .\extdata.cpp, Line 1826
06/12/2010 11:17:03 AM: General Script Error
06/12/2010 11:17:03 AM: Execution Failed
06/12/2010 11:17:03 AM: Execution finished.

Anyone had similar encounter ? Pls advise what could have cause this error ?

Thank you.

Sharon

Labels (1)
4 Replies
Not applicable
Author

I also have this problem with just one table. All others load just fine.

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.

hschultz
Partner - Creator
Partner - Creator

I had the same error with an .xlsx file. Simply removing the "Sheet is xxx" at the end made it work fine.

Don't know if it's useful, but that's how I got to this question in the first place

Not applicable
Author

It worked. Thank you.