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

Announcements
Join us in Toronto Sept 9th for Qlik's AI Reality Tour! Register Now
cancel
Showing results for 
Search instead for 
Did you mean: 
Not applicable

General Script Error

Beyond Frustrated!

I am getting a General Script Error. The Reload has successfully fetched all lines of data from all tables and there are no sythetic keys.

Can anyone shed light on why this might be happening?

Thanks

Lee

1 Solution

Accepted Solutions
prieper
Master II
Master II

Have only couple of guesses:

load only under debug 10 records each - check again for synthetic keys.
load tables one by one (probably also in debug) and see where the error incurs
in the faulty table please check for "strange" fieldnames or contents
does it always happen on the same table? if you change the order of loading?
do you have the rights to read in the database?

Peter

View solution in original post

18 Replies
Anonymous
Not applicable
Author

The most often "general script error" - incorrect use of "group by". Can you post the part of script that generates the error?

Not applicable
Author

Hi Michael,

Thanks for the reply ... please see the whole script below ... in debug the animation goes right to the end and says Script Finished ... so I am not sure what is erroring. Just to confirm ... no Synthetic Keys are created either.


SET ThousandSep=',';
SET DecimalSep='.';
SET MoneyThousandSep=',';
SET MoneyDecimalSep='.';
SET MoneyFormat='$#,##0.00;-$#,##0.00';
SET TimeFormat='hh:mm:ss';
SET DateFormat='DD/MM/YYYY';
SET TimestampFormat='DD/MM/YYYY ';
SET MonthNames='Jan;Feb;Mar;Apr;May;Jun;Jul;Aug;Sep;Oct;Nov;Dec';
SET DayNames='Mon;Tue;Wed;Thu;Fri;Sat;Sun';

CONNECT TO [Provider=SQLOLEDB.1;Integrated Security=SSPI;Persist Security Info=False;Initial Catalog=BirchMdfReportingDev;Data Source=wok-bi-data-02;Use Procedure for Prepare=1;Auto Translate=True;Packet Size=4096;Workstation ID=WOK-BI-WKST-119;Use Encryption for Data=False;Tag with column collation when possible=False];
SQL SELECT *
FROM BirchMdfReportingDev.dbo.RptAccount;
//SQL SELECT *
//FROM BirchMdfReportingDev.dbo.RptAccountFunding;
SQL SELECT *
FROM BirchMdfReportingDev.dbo.RptActivity;
SQL SELECT *
FROM BirchMdfReportingDev.dbo.RptActivityAudience;
SQL SELECT *
FROM BirchMdfReportingDev.dbo.RptActivityCode;
SQL SELECT *
FROM BirchMdfReportingDev.dbo.RptActivityCodeROI;
SQL SELECT *
FROM BirchMdfReportingDev.dbo.RptActivityCustomer;
SQL SELECT *
FROM BirchMdfReportingDev.dbo.RptActivitySoftware;
SQL SELECT *
FROM BirchMdfReportingDev.dbo.RptActivitySolution;
SQL SELECT *
FROM BirchMdfReportingDev.dbo.RptActivityVertical;
SQL SELECT *
FROM BirchMdfReportingDev.dbo.RptAudience;
SQL SELECT *
FROM BirchMdfReportingDev.dbo.RptClaim;
SQL SELECT *
FROM BirchMdfReportingDev.dbo.RptCountriesArea;
SQL SELECT *
FROM BirchMdfReportingDev.dbo.RptCurrency;
SQL SELECT *
FROM BirchMdfReportingDev.dbo.RptCustomer;
SQL SELECT *
FROM BirchMdfReportingDev.dbo.RptFund;
SQL SELECT *
FROM BirchMdfReportingDev.dbo.RptObjective;
SQL SELECT *
FROM BirchMdfReportingDev.dbo.RptROI;
SQL SELECT *
FROM BirchMdfReportingDev.dbo.RptROIDescription;
SQL SELECT *
FROM BirchMdfReportingDev.dbo.RptSLA;
SQL SELECT *
FROM BirchMdfReportingDev.dbo.RptSoftware;
SQL SELECT *
FROM BirchMdfReportingDev.dbo.RptSolution;
SQL SELECT *
FROM BirchMdfReportingDev.dbo.RptState;
SQL SELECT *
FROM BirchMdfReportingDev.dbo.RptStatusCode;
SQL SELECT *
FROM BirchMdfReportingDev.dbo.RptUsage;
SQL SELECT *
FROM BirchMdfReportingDev.dbo.RptUser;
SQL SELECT *
FROM BirchMdfReportingDev.dbo.RptUserAccountSecurity;
SQL SELECT *
FROM BirchMdfReportingDev.dbo.RptVertical;
SQL SELECT *
FROM BirchMdfReportingDev.dbo.RptXRate;




prieper
Master II
Master II

Did you try to switch the log-option to OFF?
After a crash or after having killed the application, it can be that the logfile is still blocked and trying to create a new one then fails with such error-message.

HTH
Peter

Not applicable
Author

Hi Peter.

Just given that a try and still not loading ... I have been through and built it up table by table by commenting and uncommenting and it appears to be failing on 9 tables with no commonality as to why they might fail. Have you come across something like that before?

Thanks

Lee

prieper
Master II
Master II

Have only couple of guesses:

load only under debug 10 records each - check again for synthetic keys.
load tables one by one (probably also in debug) and see where the error incurs
in the faulty table please check for "strange" fieldnames or contents
does it always happen on the same table? if you change the order of loading?
do you have the rights to read in the database?

Peter

Not applicable
Author

Hi Peter,

Still no luck but thank you for you suggestions ... I have full rights, changed the load order, reduced the data load ... the fields are all pretty standard e.g. ObjectiveDescription the various field types match e.g nvarchars etc. Really stumped now.

Cheers

Lee

Not applicable
Author

do you have any section access/section application statements in a hidden script? any form of security within the document?

Not applicable
Author

Hi,

Have you used a Store to create a QVD at the end ?

Have you tried to remove some SQL SELECT statments and do it step-by-step ?

Not applicable
Author

Hi,

Thanks for reply Naveen.

I do but I had commented them out until this is fixed. A real head scrambler this one!

Cheers

Lee