Broadcast report to FTP occasionally sends 0 byte corrupted file .
Resolved
Hi,
There have been reports that some reports sent to FTP server are sent as 0 byte files and cannot be opened. Opening the XLS file shows file is corrupted error.
Can this even occur? As I thought if there were no records returned based on report query, no report will be sent. So thinking if it is a network/connectivity issue to the FTP server.
If the report generation times out for what ever reason, what occurs? Does YellowFin retry to broadcast, how many times before it stops retrying.
Any help will be greatly appreciated.
Thank you,
Duy
Hi Duy Do,
Does the report always generate data when run or does the report sometimes produce an empty report?
This certainly could be related to a network or (disk capacity issue perhaps?)
If the report fails to generate or cause an error, then the broadcast should fail and no file should be sent and Yellowfin will both show a Failure in the Admin Schedule section and an error the yellowfin.log should appear. Are you seeing any errors in the Schedule section or the logs? There is currently no retry feature for the broadcast except to run the next time, but an enhancement has been mad with our Dev team.
Do you have any yellowfin logs applicable to the time this happened last that I can look at?
Regards,
Paul
Hi Duy Do,
Does the report always generate data when run or does the report sometimes produce an empty report?
This certainly could be related to a network or (disk capacity issue perhaps?)
If the report fails to generate or cause an error, then the broadcast should fail and no file should be sent and Yellowfin will both show a Failure in the Admin Schedule section and an error the yellowfin.log should appear. Are you seeing any errors in the Schedule section or the logs? There is currently no retry feature for the broadcast except to run the next time, but an enhancement has been mad with our Dev team.
Do you have any yellowfin logs applicable to the time this happened last that I can look at?
Regards,
Paul
Hi Paul,
Appreciate your reply. It only happens rarely, so when it happens again i will provide the logs.
Thank you,
Duy
Hi Paul,
Appreciate your reply. It only happens rarely, so when it happens again i will provide the logs.
Thank you,
Duy
Hi Duy Do,
That sounds like a good idea. I will leave this with you for a while. Please get back to me when you have the issue again and some logs etc for me to analyse.
Regards,
Paul
Hi Duy Do,
That sounds like a good idea. I will leave this with you for a while. Please get back to me when you have the issue again and some logs etc for me to analyse.
Regards,
Paul
Hi Duy Do,
Have you managed to see this issue again as I have not heard back from you for a little while?
Regards,
Paul
Hi Duy Do,
Have you managed to see this issue again as I have not heard back from you for a little while?
Regards,
Paul
Hi Duy Do,
Hope you're having a good week.
Just wanted to check-in and see how it's all going. Was there anything you were needing from me to help get this resolved?
Regards,
Hi Duy Do,
Hope you're having a good week.
Just wanted to check-in and see how it's all going. Was there anything you were needing from me to help get this resolved?
Regards,
Hi Duy,
Just letting you know that I am going to close off this ticket as I have not heard back from you. If you need further help, please keep in touch.
Regards,
Paul
Hi Duy,
Just letting you know that I am going to close off this ticket as I have not heard back from you. If you need further help, please keep in touch.
Regards,
Paul
Replies have been locked on this page!