Qlik Sense : Reloads failing with error "General Script Error in statement handling" and error code 232 in engine logs

[Andrea_Bertazzo]

Many reloads are failing on different schedulers with General Script Error in statement handling. The issue is intermittent.
The connection to the data source goes through our Qlik ODBC connectors.

The Script Execution log shows a  “General Script Error in statement handling” message. Nevertheless, the same execution works if restarted after some time without modifying the script that looks correct.

The engine logs show:

CGenericConnection: ConnectNamedPipe(\\.\pipe\data_92df2738fd3c0b01ac1255f255602e9c16830039.pip) set error code 232

Environment

• Qlik Sense Enterprise on Windows May 2021
• Qlik Sense Enterprise on Windows September 2020 and higher (less frequent occurrence) 

Resolution

Change the reading strategy within the current connector:

Set reading-strategy value=engine in C:\ProgramFiles\Common Files\Qlik\CustomData\QvOdbcConnectorPackage\QvODBCConnectorPackage.exe.config

reading-strategy value=connector should be removed

Switching the strategy to engine may impact NON SELECT queries. See Connector reply error: Executing non-SELECT queries is disabled. Please contact your system administ...  for details.

Internal Investigation ID(s):

QB-8346

[Alastair_Ometis]

Hi @Sonja_Bauernfeind,

@Andrea_Bertazzo, suggested applying this fix to @nik_lim who had similar symptoms with the REST connector.

I have looked and I don't see the key in the appsettings of the REST Connector Config file.

Can you advise how to proceeed?  We are running Qlik Sense May 2023.

Best,

Alastair

[seblabalyerr]

Hi Everyone,

We have also same error for Rest Connector. Since the same parameter is not for REST, how can we edit it?

Thanks

[Sonja_Bauernfeind]

Hello @seblabalyerr 

I  recommend searching the error you receive in our larger community, including information that you are seeing the issue with the REST Connector. As we do not have a lot of information to go by, I can only provide generic advise.

Examples:

QlikSense error General Script Error in statement handling question 
REST API task is failing Intermittently with General Script Error in statement handling 

Either way, please post about your issue in the Connectivity and Data Prep forum, where our active support agents and your Qlik peers can more readily assist you. When doing so, include:

• Your version
• Information about your setup
• The error you receive (both in the script and in the log files)
• Information on whether this worked previously or not

All the best,
Sonja 

[cjgorrin]

We were getting this error in our servers because due to business needs, we had to insert a lot of records into an Oracle DB in an app's load script and we were getting this "General error" with pipe error 232 in the logs.

Applying the patch kind of worked, and I say "kind of" because it broke the !EXECUTE_NON_SELECT_STATEMENT functionality. All our apps that used it with Oracle just stop reloading correctly and failed with DB error "ORA-00933: SQL command not properly ended" because the "!EXECUTE_NON_SELECT_QUERY" part was being sent to the DB as part of the SQL statement (our DBA confirmed this).

So, after testing a lot we found out the following:

• All Oracle data connections created BEFORE the fix have UseBulkReader = False in their connection string.
• All Oracle data connections created AFTER the fix have UseBulkReader = True in their connection string.
• The combination of UseBulkReader = False, reading-strategy value=engine and !EXECUTE_NON_SELECT query just doesn't work. Either you remove the !EXECUTE_NON_SELECT_STATEMENT or you change UseBulkReader to true in the connection string.

We experienced this issue with version May 2023 patch 9. I hope this can help anybody having the same issue.

@Sonja_Bauernfeind and @Andrea_Bertazzo, if you could update the article to reflect this side effect, it would be very useful. Thanks.

[cjgorrin]

We were getting this error in our servers because due to business needs, we had to insert a lot of records into an Oracle DB in an app's load script and we were getting this "General error" with pipe error 232 in the logs.

Applying the patch kind of worked, and I say "kind of" because it broke the !EXECUTE_NON_SELECT_STATEMENT functionality. All our apps that used it with Oracle just stop reloading correctly and failed with DB error "ORA-00933: SQL command not properly ended" because the "!EXECUTE_NON_SELECT_QUERY" part was being sent to the DB as part of the SQL statement (our DBA confirmed this).

So, after testing a lot we found out the following:

• All Oracle data connections created BEFORE the fix have UseBulkReader = False in their connection string.
• All Oracle data connections created AFTER the fix have UseBulkReader = True in their connection string.
• The combination of UseBulkReader = False, reading-strategy value=engine and !EXECUTE_NON_SELECT query just doesn't work. Either you remove the !EXECUTE_NON_SELECT_STATEMENT or you change UseBulkReader to true in the connection string.

We experienced this issue with version May 2023 patch 9. I hope this can help anybody having the same issue.

@Sonja_Bauernfeind and @Andrea_Bertazzo, if you could update the article to reflect this side effect, it would be very useful. Thanks.

[cjgorrin]

UPDATE: we are not sure if the UseBulkReader default value changed when we applied the fix or because we installed a more recent patch. In any case, the third item in the list above is still correct:

Bulk reader False + engine reader strategy + !EXECUTE_NON_SELECT_STATEMENT = problems.