Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 
Not applicable

Qlikview task in QMC seems running forever

Hi All,

I am experiencing a strange issue from last few days, a task in QMC seems running forever, usually it takes 3mins to run but currently its running for last 3days, have tried to stop the task manually but it didn't  work. Have restarted management services and distribution services still no luck. Finally had to restart the server still the task is running. Is this some kind of a bug in qlikview??? Is there any way to stop this task??? Has any one of you faced this kind issue???

Product Details:

QlikViewServer 64-bit Edition (x64)

Version 11.0.11440.0

Please give your valuable suggestion.

Regards,

Sakir

20 Replies
Anonymous
Not applicable
Author


Consider adding a timestamp to your log file, this way every execution of the task will create a separate log file and you can always look back at the history.

This is set on a document by document basis. In designer got to Settings/General and enable Timestamp In Logfile Name.

You will then have to manage those log files as they accumualte, zip and archive or delete after n days. But we have found having this history available is really useful, the actual log file created by the QVW sometimes has extra final entries you don't get to see in QMC mined from the Distribution Service xml files.

Not applicable
Author

For the time being we came up with a solution.

Solution is to remove and then create a new task. I dont know whether its advisable or not.

Please share your views.

flipside
Partner - Specialist II
Partner - Specialist II

I'm not sure if this is due to my server configuration, as I set it up a long time ago, but on your server if you go to ...

C:\ProgramData\QlikTech\DistributionService\1\Log (where the drive and folder 1 might be different) ...

you may see folders for each day in the format 'YYYYMMDD'. Within these folders are subfolders for time and tasks in the format 'HHMMSS - {mounted folder}_{name of qvw}.qvw' and these folders contain the document log for each task run. So you may be able to go 'back in time' and look at them if you know when the failure was.

flipside

flipside
Partner - Specialist II
Partner - Specialist II

Your earlier reply where you said the task hadn't completed suggests there's a problem in your document load script, rather than the task itself - I'd be surprised if it didn't re-occur. It could be something like an ODBC or OLEDB connection being locked out or something similar. Have a look at my reply to Paul Routledge to see if you can get to your earlier document logs where the task failed.

flipside


nizamsha
Specialist II
Specialist II

it wont take three days to load the task and all first thing

main thing u have scheduled a task before in qmc after some days u might have chnged the file name and removed a file from the location so what qmc shows is that task is keep on running ..closely look at the file file and check in the path file wont be present there .for this problem .change a file name and scheduled the task again .and if u want to remove the running old task mean in status u have option called disable .disable the task it wont show the old running task for 3 days i hope it helps

ergustafsson
Partner - Specialist
Partner - Specialist

The version you are running is quite an old one. I would recommend you to upgrade and see if the situation improves, considering there have been lots of improvements in the product since. Might be some corruption in the QVPR that causes this.

What is the QDS log files saying?

If the issue persists after an upgrade, you might want to file a support case with QV Support.

simenkg
Specialist
Specialist

Hi, Sakir.

I don't know if you have found a  solution to your problem, but we faced a very similary problem with a task stuck at "running" after reset of the server to a previous snapshot.

Anyways, the solution I found was to delete the corresponding file in the C:\ProgramData\QlikTech\DistributionService\TaskResults\ folder or the custom folder for det QDS log files.

The file should be named something like: TaskResult_e6bcba42-95e4-4406-86e1-ac7caf4cb8ef.xml.

It should have a modified date similar to the "last execution" column for the freezed task.

Removing this file and restarting the service fixed everything for us.

Regards

Simen Kind Gulbrandsen

Not applicable
Author

Hi Simen,

Its not possible to try your solution right now as issue is currently not there. But will definitely try your solution and update you if I face it again.

For the temporary fix, I had to disabled the task and restarted the services. Then re-created the same task.

Thanx,

Sakir

Not applicable
Author

Hi

I had the same problem and it was solvd by the solution from Simen Kind Gudbrandsen.

Thanks a lot!

Best Regards Jonas Berglund

anjali0108
Partner - Creator III
Partner - Creator III

Hi Sakir,

Even I am facing similar problem and because of one task running forever,other tasks are still in waiting state.

Could you please tell what all files I need to delete as there are many files in that folder?

Thanks.