Skip to main content
Announcements
Have questions about Qlik Connect? Join us live on April 10th, at 11 AM ET: SIGN UP NOW
cancel
Showing results for 
Search instead for 
Did you mean: 
Not applicable

QDSMain.Exceptions.DistributionFailedException:

WHAT THE BELOW MESSAGE MEANS?

QDSMain.Exceptions.DistributionFailedException: Distribute failed with errors to follow. ---> QDSMain.Exceptions.ReloadFailedException: Reload failed ---> QDSMain.Exception@s.LogBucketErrorException: The Source Document was NOT reloaded successfully. DocumentPath=\\SERVER02\ProductionSourceDocuments\QlikView Ops Monitor v9.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.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)

7 Replies
Alejandro_Hernández
Former Employee
Former Employee

can you post the documentlog.txt file?

Not applicable
Author

I've got the same problem. While running manual - works perfectly.

Here's documentLog.txt:

2014.01.09 15:19:00.7191545Information2014.01.09 15:19:00:      Execution started.
2014.01.09 15:19:00.7201546Information2014.01.09 15:19:00:      QlikView Version:11.20.12123.0
2014.01.09 15:19:00.7211547Information2014.01.09 15:19:00:      CPU Target                    x64
2014.01.09 15:19:00.7211547Information2014.01.09 15:19:00:      Operating System              Windows Server (R) 2008 Standard Service Pack 2 (64 bit edition)
2014.01.09 15:19:00.7211547Information2014.01.09 15:19:00:      Wow64 mode                    Not using Wow64
2014.01.09 15:19:00.7221548Information2014.01.09 15:19:00:      MDAC Version                  6.0.6002.18005
2014.01.09 15:19:00.7221548Information2014.01.09 15:19:00:      MDAC Full Install Version     6.0.6002.18005
2014.01.09 15:19:00.7231549Information2014.01.09 15:19:00:      PreferredCompression          2
2014.01.09 15:19:00.7231549Information2014.01.09 15:19:00:      EnableParallelReload          1
2014.01.09 15:19:00.7241550Information2014.01.09 15:19:00:      ParallelizeQvdLoads           1
2014.01.09 15:19:00.7241550Information2014.01.09 15:19:00:      AutoSaveAfterReload           0
2014.01.09 15:19:00.7241550Information2014.01.09 15:19:00:      BackupBeforeReload            0
2014.01.09 15:19:00.7251551Information2014.01.09 15:19:00:      EnableFlushLog                0
2014.01.09 15:19:00.7251551Information2014.01.09 15:19:00:      SaveInfoWhenSavingFile        0
2014.01.09 15:19:00.7261552Information2014.01.09 15:19:00:      UserLogfileCharset            1200
2014.01.09 15:19:00.7261552Information2014.01.09 15:19:00:      OdbcLoginTimeout              -1
2014.01.09 15:19:00.7261552Information2014.01.09 15:19:00:      OdbcConnectionTimeout         -1
2014.01.09 15:19:00.7271553Information2014.01.09 15:19:00:      ScriptWantsDbWrite            false
2014.01.09 15:19:00.7271553Information2014.01.09 15:19:00:      ScriptWantsExe                false
2014.01.09 15:19:00.7281554Information2014.01.09 15:19:00:      LogFile CodePage Used:        1200
2014.01.09 15:19:00.7281554Information2014.01.09 15:19:00:       Reload Executed By ***************
2014.01.09 15:19:00.7281554Information2014.01.09 15:19:00:       Process Executing: QVB
2014.01.09 15:19:00.8291655Information2014.01.09 15:19:00:       Process ID: 13296
2014.01.09 15:19:00.8291655Information2014.01.09 15:19:00:        1 fields found: 
2014.01.09 15:19:01.2302056Information3 lines fetched
2014.01.09 15:19:01.2302056Information2014.01.09 15:19:01:        1 fields found:
2014.01.09 15:19:01.4312257Information
2014.01.09 15:19:01.9312757Information3 lines fetched
2014.01.09 15:19:01.9312757Information2014.01.09 15:19:01:            132 fields found:
2014.01.09 15:19:01.9322758Information
2014.01.09 15:19:14.8515676Information140.390 lines fetched
2014.01.09 15:19:14.8515676Information2014.01.09 15:19:14:            115 fields found:
2014.01.09 15:19:16.0526877Information656 lines fetched
2014.01.09 15:19:16.0526877Information2014.01.09 15:19:15:            121 fields found:
2014.01.09 15:19:17.0537878Information981 lines fetched
2014.01.09 15:19:17.0537878Information2014.01.09 15:19:17:            72 fields found:
2014.01.09 15:19:18.1548979Information155 lines fetched
2014.01.09 15:19:18.1548979Information2014.01.09 15:19:18:            187 fields found:
2014.01.09 15:19:19.9560780Information2.506 lines fetched
2014.01.09 15:19:19.9560780Information2014.01.09 15:19:19:            14 fields found:
2014.01.09 15:19:20.2581082Information55 lines fetched
2014.01.09 15:19:20.2581082Information2014.01.09 15:19:20:             General Script Error
2014.01.09 15:19:20.2591083Information2014.01.09 15:19:20:             Execution Failed
2014.01.09 15:19:20.2591083Information2014.01.09 15:19:20:      Execution finished.
Bill_Britt
Former Employee
Former Employee

Hi,

I would look around this area  of your script to see what is wrong.

2014.01.09 15:19:20.2581082Information55 lines fetched
2014.01.09 15:19:20.2581082Information2014.01.09 15:19:20:             General Script Error

You will need to make sure the service account has rights to get to this data. You can also login as the service account and run the script with the desktop to see what is happening. Could be as simple as a ODBC DSN is setup for user and not system.

Bill

Bill - Principal Technical Support Engineer at Qlik
To help users find verified answers, please don't forget to use the "Accept as Solution" button on any posts that helped you resolve your problem or question.
Not applicable
Author

Thank you, Bill.

If I tried to reload the app manually, it worked perfectly.

I found that this was caused by the server reloading service. I copied a new app version on top of the old version and simply tried to reload it which gave me the exception. Then I switched to the old one, took off the reload service, copied new version and switched the reload once again. The app has document CALs on it. So probably the reload engine remembers something.

chandrasarva
Contributor II
Contributor II

Hello,

any update on this we came across the same issue but when reran the task it runs fine.

we are on 11.2 sr4.

when the task ran initially we see the same Genera' script error immediately after the store into QVD command

Thanks for your help in advance

Thanks

Chandra

umartareen
Creator II
Creator II

Hi All,

Any updates on this issue ? Im facing a similar problem.

Thanks

Umar

Not applicable
Author

It looks like a database permission issue. Check the login that that service is using to access the database and make sure it has read rights to all the tables it needs.