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.LogBucketErrorException ???

Hi,

   I am getting the error "QDSMain.Exceptions.LogBucketErrorException" when i try to reload the document. Can anyone tell me, what is it wrong in the document. 

4 Replies
Anonymous
Not applicable
Author

Good day,

There could be many reasons for this, but in essence there's something wrong in the QLikView script.

I got the same error and I did the following.

First I noticed a small script error where I only wanted to load a subset of data and I misplaced a ';'

Secondly check all "directory" locations.  I had to put the full path in my script include statement.

So check all QVD output locations, etc.

It does not mean if the script works on your client it would work on the server because all the directory structures typically differ.

Regards

Edwin

andriesb
Creator II
Creator II

Easiest is to enable log file within the qvw . This will generate a proper logfile during reload and will show the real cause of the reload problem.

andriesb_0-1647503055864.png

 

For me is it inexplicable why Qlik never add prober and usable info to the email for this kind of errors. Even if the log is enabled, you will never get a proper log file or even the last few lines of the error. Adding that info will save you a lot of time as the only other option is reloading it after enabling the logging option. 

Harvey
Contributor
Contributor


@epayitonline wrote:

Hi,

 

   I am getting the error "QDSMain.Exceptions.LogBucketErrorException" when i try to reload the document. Can anyone tell me, what is it wrong in the document. 


even I got the similar error, but to show you guys I don't have a log because in the next run job was successful and log over written on the failure log..

can you please help me with what fix you have done to your app to avoid this kind job failures..??

andriesb
Creator II
Creator II

Investigate the created log file for the failed report as soon as it appears and before the next reload should reveal the problem. In my case it was a multiple usage of a odbc source and changing the reload start time for one of the jobs did solve my problem.