topic Re: how to solve this killing qlikview engine problem? in QlikView

how to solve this killing qlikview engine problem?

gowthamrajr — Wed, 25 Nov 2020 16:16:04 GMT

hi experts,

i am getting log details for my scheduled qvw file as below,

(2016-05-05 03:18:14) Information: Reloading

(2016-05-05 03:30:10) Warning: The QlikView Engine is Reloading, it will be killed (Please ignore logged warnings/errors about the kill).

(2016-05-05 03:30:10) Information: Killing the QlikView Engine. ProcessID=10476

(2016-05-05 03:30:10) Information: Reload was aborted.

(2016-05-05 03:30:10) Information: Killing a child process of the QlikView Engine. ProcessID=11400. ProcessName=qvconnect64

(2016-05-05 03:30:10) Information: Successfully killed a child process of the QlikView Engine. ProcessID=10476. ProcessName=qvb

(2016-05-05 03:30:11) Information: Closed the QlikView Engine successfully. ProcessID=10476

(2016-05-05 03:30:11) Error: The task "Extraction FSL QVD.qvw" failed. Exception: || QDSMain.Exceptions.TaskFailedException: Task execution failed with errors to follow. ---> QDSMain.Exceptions.ReloadFailedException: Reload failed ---> System.Threading.ThreadAbortException: Thread was being aborted. || at System.Threading.WaitHandle.WaitOneNative(SafeHandle waitableSafeHandle, UInt32 millisecondsTimeout, Boolean hasThreadAffinity, Boolean exitContext) || at System.Threading.WaitHandle.InternalWaitOne(SafeHandle waitableSafeHandle, Int64 millisecondsTimeout, Boolean hasThreadAffinity, Boolean exitContext) || at SolutionGlobal.ThreadPool.ThreadPoolJob.SafeWaitEvent(WaitHandle eventWaitHandle) || at QDSMain.ReloadTask.Reload(String fileName, TaskResult taskResult, String sectionAccessUserName, String sectionAccessPassword, eReloadOptions reloadOption, String variableName, String variableValue, Boolean moniterCpuUsage) || --- End of inner exception stack trace --- || at QDSMain.ReloadTask.Reload(String fileName, TaskResult taskResult, String sectionAccessUserName, String sectionAccessPassword, eReloadOptions reloadOption, String variableName, String variableValue, Boolean moniterCpuUsage) || at QDSMain.DistributeTask.Execute(TaskResult currentTaskResult) || --- End of inner exception stack trace --- || at QDSMain.DistributeTask.Execute(TaskResult currentTaskResult) || at QDSMain.Task.AbstractTask.TaskExecution(ILogBucket logBucket, TaskResult taskResult)

(2016-05-05 03:30:11) Error: Task failed with exception

(2016-05-05 03:30:11) Error: Exception=The currently executing operation was aborted.

(2016-05-05 03:30:11) Information: TaskResult.status=Finished

can anyone know what happened and how to solve this issue?

Re: how to solve this killing qlikview engine problem?

alexdataiq — Thu, 05 May 2016 14:36:42 GMT

That's odd, that warning usually appears when a task has been aborted from the QMC. Does it happen randomly?

Regards

Re: how to solve this killing qlikview engine problem?

gowthamrajr — Fri, 06 May 2016 04:23:45 GMT

hi Alejandro,

thanks for your reply,

yes it happens continuously three days.

what is the reason behind this error?

Re: how to solve this killing qlikview engine problem?

Sat, 07 May 2016 03:44:29 GMT

Dear Fernandez ,

i am gowtham colleague , still we are facing same issues on daily basis .

Hope its performance issues . usually file takes 4 hours to run , but past 3 days its taking 6 hours to execute and getting failed .

we find out from log file its getting failed on transaction qvd , where it have 50 million records . But past 6 month we are executing same file and didn't face any issues .

could you please help me to sort out

Re: how to solve this killing qlikview engine problem?

ziadm — Sat, 07 May 2016 04:14:18 GMT

Please try to send the qvw log file ... check the log see where the script failed to reload...

also try to analyze your qvw file using the governance dashboard analyzer

QlikView Governance Dashboard

if this helpful please mark resolved or helpful

Re: how to solve this killing qlikview engine problem?

Sat, 07 May 2016 04:38:26 GMT

Thanks for your quick reply ,

Kindly check my attached log , i will check from governance dashboard and close this soon.

Re: how to solve this killing qlikview engine problem?

ziadm — Sat, 07 May 2016 04:59:21 GMT

I think that you are unable to connect to ODBC Data Base

your timeout is set to -1 which is infinity

5/6/2016 9:30:02 PM: OdbcLoginTimeout -1

5/6/2016 9:30:02 PM: OdbcConnectionTimeout -1

This does not seems to be Qlikview script error, seems like ODBC connection is not able to listen to DB and it does not timeout

You can check with DBA, something appears to be wrong from DB side.

if you are to connect from your PC it does not that server is able to reach the DB. I would suggest to check the connection on the server and make sure that server is having all credentials to access the DB

if this is helpful please mark as helpful or resolved

Re: how to solve this killing qlikview engine problem?

marcus_sommer — Sat, 07 May 2016 08:46:57 GMT

Very probably will be the reasons within your database, odbc-driver and/or the network which hits any limitations and/or timeouts.

I suggest to split these qvd-generator into several generators maybe 10, 20 or 50 generators then there are a lot (I think too many) script-parts (SQL queries). It's not mandatory necessary to create for each query a single qvd-generator - they could for example be grouped into logical units.

The advantages from such doing is to get smaller generators which are easier to handle and to maintain and which could run parallel (related to qlikview and to your database) and which minimized the risks in hitting any limitations and/or timeouts. Further if then anything didn't worked like expected or goes wrong it's a lot easier to find and fix the reasons - and also for optimizing some parts, for example to apply incremental logics to the bigger queries.

Maybe this: Advanced topics for creating a qlik datamodel and this: More advanced topics of qlik datamodels is helpful for you.

- Marcus

Re: how to solve this killing qlikview engine problem?

Tue, 10 May 2016 11:38:29 GMT

Dear Ziad ,

Hope there is a problem with ODBC connection on retrieving data. I am checking with my DB team , meanwhile my extraction file runs avg of 4 hours 45 min , but after 3rd may its running up to 6 hours 10 min and getting failed . From log file i noticed , Provisional qvd runs 45 min earlier , but now a days its running for more than 3 hours .

I didn't set any time limit in my QMC , please check my attached image , is it possible to increase duration hours from 6 hours to 9 hours ?.

Please suggest

Re: how to solve this killing qlikview engine problem?

perumal_41 — Mon, 02 Jan 2017 07:54:30 GMT

Hi Sriram,

Still your facing same problem