Jobs failing intermittently with General Script Error in Qliksense

[sukanyadutta]

Hello,

One job in Qliksense  failed with an error below:

20210603T124122.213+0200 0015 LOAD *
20210603T124122.213+0200 0016 SQL SELECT DISTINCT QVD_NAME FROM QVMANAGEMENT.QVMGT_QVD_MASTER_T
20210603T124122.213+0200 0017 WHERE QVDID = ''
20210603T124124.892+0200 General Script Error in statement handling
20210603T124127.700+0200 Execution Failed
20210603T124127.703+0200 Execution finished.

It failed once on 03/06/2021 When triggered twice, it was a success. We have not done any recent changes in app script and anything in app schedule or app related changes.

We've checked the environment, it was up and  RAM and CPU was not fully exhausted.

We have found some errors regarding connector at the time of failure :

CGenericConnection: Failed to send QVX_TERMINATE to process 9240 (reason 999); C:\Program Files\Common Files\Qlik\Custom Data\QvOdbcConnectorPackage\QvOdbcConnectorPackage.exe
CGenericConnection: Skipping QVX_TERMINATE for process 9240 (reason 999); C:\Program Files\Common Files\Qlik\Custom Data\QvOdbcConnectorPackage\QvOdbcConnectorPackage.exe

we are running on version 'September 2020' and no changes in app script since it is deployed. Running fine right now as well.

Any suggestions ?

[PadmaPriya]

Hello @sukanyadutta 

Please find the below articles:

https://community.qlik.com/t5/Connectivity-Data-Prep/Monitoring-App-Error-CGenericConnection-QvConne...

Also it could be at times issue with Antivirus hence follow below article too:

https://support.qlik.com/articles/000028726

Thanks,

PadmaPriya

[sukanyadutta]

Hi PadmaPriya,

-We are using QvOdbcConnectorPackage but the article you mentioned is showing for Rest connector. 
-All of our servers are whitelisted from Antivirus scan. 

[PadmaPriya]

Thanks for your response @sukanyadutta 

Reason 999: Termination of the named pipe happened in a wrong state.
The Named pipe can be affected by windows memory handling as it's a in memory communication handling between the connector and Engine.
Possible reasons could be elevation of creating these connections or antivirus that stops us from doing this.

If we need more information we need to see what is sent on that named pipe, please only use this with caution as this may even log out sensitive information. Meaning this setting should be enabled as short as possible.

Settings.ini
SELOG_QVSConnector = 1

Basic information about named pipe if that is interesting to read:

https://en.wikipedia.org/wiki/Named_pipe

[sukanyadutta]

Hi PadmaPriya,

I found some articles how can we enable the mentioned settings. How To Enable Logging For Direct Discovery (qlik.com). But It's for Qlikview. Do you have any article for qliksense multi node environment? And also, is there any need of service restart after applying the setting? What services should we restart?

[BTIZAG_OA]

In which log file can we chase the entries after we set  SELOG_QVSConnector = 1