topic Qlikview Distribution service in QlikView

Qlikview Distribution service

Mon, 26 Jan 2026 18:19:17 GMT

Hi,

Recently we are having a problem with the distribution service. It stopped running.

Is there a log file to tell me why it stopped working?

Kind regards

Michael

Re: Qlikview Distribution service

saumyashah90 — Mon, 15 Dec 2014 08:16:05 GMT

Can you tell us more details about Distribution Service?

Re: Qlikview Distribution service

Mon, 15 Dec 2014 08:19:22 GMT

There is a message at the top qlikview management console : "ReloadEngine@Server is down"

Re: Qlikview Distribution service

ashfaq_haseeb — Mon, 15 Dec 2014 08:19:28 GMT

Hi,

You can find logs in below path

C:\ProgramData\QlikTech\QlikViewServer

C:\ProgramData\QlikTech\DistributionService\1\Log.

Regards

ASHFAQ

Re: Qlikview Distribution service

Peter_Cammaert — Mon, 15 Dec 2014 08:26:56 GMT

In C:\ProgramData\QlikTech\DistributionService\1\Log, there are a couple of files called Root_something.txt where this something is the date of the QDS session.

Open the one from the date when troubles with the QDS began. You'll probably find an explanation about why the Distribution Service refuses to operate as expected.

Re: Qlikview Distribution service

Mon, 15 Dec 2014 08:33:01 GMT

Hi,

I found this error but i don't see why it should be related with the distribution service.

Error The task "OLD/FBD - ranking OLD.qvw" failed. Exception:

QDSMain.Exceptions.DistributionFailedException: Distribute failed with errors to follow. ---> QDSMain.Exceptions.ReloadFailedException: Reload failed ---> QDSMain.Exceptions.LogBucketErrorException: The Source Document was NOT reloaded successfully. DocumentPath=C:\ProgramData\QlikTech\SourceDocuments\OLD\FBD - ranking OLD.qvw.

at QDSMain.ReloadTask.VerifyConditions(TaskResult taskResult)

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.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)

26/11/2014 07:28:20.7345314 Error The task "OLD/FBD - Ca OLD.qvw" failed. Exception:

at QDSMain.ReloadTask.VerifyConditions(TaskResult taskResult)

--- End of inner exception stack trace ---

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)

Where can i find more information about this error?

Re: Qlikview Distribution service

ashfaq_haseeb — Mon, 15 Dec 2014 08:38:37 GMT

Hi,

First thing make sure your distribution service is up and running.

Secondly if you have any section access applied to your application, make sure to add service account to section access admin account.

Regards

ASHFAQ

Re: Qlikview Distribution service

SunilChauhan — Mon, 15 Dec 2014 08:42:01 GMT

stop all services and start again

Re: Qlikview Distribution service

Peter_Cammaert — Mon, 15 Dec 2014 08:45:47 GMT

Well, in two places. The Distribution service launches a reload job to handle script execution. For every reload job, a TaskLog.txt file is created in C:\ProgramData\QlikTech\DistributionService\1\Log\date\taskinstance\. But on average, that file won't be very helpful. If you enabled the option "Generator Log file" in Document Properties, another log file called DocumentLog.txt will be generated that reflects the execution result of every single statement in your load script. Those two are the main job-related files to check whenever something goes wrong during execution of a Reload task.

Peter

Re: Qlikview Distribution service

Mon, 15 Dec 2014 08:46:53 GMT

Hi,

i restarted all the service the first time and it stopped after some days.

The service account is local admin.

Is it possible when there is not enough memory while reloading a report that qlikview stopped the distribution service?

Re: Qlikview Distribution service

Mon, 15 Dec 2014 08:47:13 GMT

I do love the generic IT restart solution

Re: Qlikview Distribution service

ashfaq_haseeb — Mon, 15 Dec 2014 08:48:36 GMT

Could be.

Regards

ASHFAQ

Re: Qlikview Distribution service

Bill_Britt — Mon, 15 Dec 2014 19:56:36 GMT

Hi Michael,

I would check the document log to see if it shows an error on the reload. Also, how many processors does your machine have and how many are allotted for the QVB process?

Bill

Re: Qlikview Distribution service

Wed, 17 Dec 2014 10:29:54 GMT

Hi Bill,

I think the reload failed because there was't enough memory available.

We have 2 processors. There is no particulary configuration on the server to allow process to QV

Re: Qlikview Distribution service

Thu, 18 Dec 2014 11:52:39 GMT

I would suggest you look in Windows Event Log, to get the exact timestamp when the service stopped. Also you might find the answer in here by looking at events/error leading up to that timestamp.

Next step is to look in the Distribution Service log folder (the path Peter earlier pointed out - make sure to check any file with the date when the service stopped.). Try to analyze the logged information leading up to the timestamp.

Re: Qlikview Distribution service

Bill_Britt — Thu, 18 Dec 2014 13:51:16 GMT

Hi Michael,

I think according to the information that you have given, you are having a resource issue on the machine. If two processors the max reloads at the same time would be two, but if QVS is running on the machine this will cause issues.

Bill