Has anyone had issues with a Report Caster job running but not disturbing emails - neither the report email OR the notification?

This message has been edited. Last edited by: FP Mod Chuck,

Hi Jen,

A no report distribution could have several reasons.

1- Does the report, outside RC is showing a result ?
2- What does RC schedule log is showing ?
3- What is your SET EMPTYREPORT option ? ON/OFF

Please share any other more detailed information that you may have.

Thanks so much, MartinY. This is my first focal point post. I should have been more detailed.

This is an RC job that has been successfully running for quite some time (there are actually 4 jobs). The log for 3 of them were that they ran great and did distribute. The 4th did have no data in the report but still should have distributed this information.

I just am not sure if there is something behind the scenes that would prevent the emailing of the report and/or notification?

1) Check your mailserver configuration.
2) Ask your admin to check the firewall connection between Reportcaster server and mailserver. I believe they need to open the Port 25 to send mails from Reportcaster.

Unlikely to be the cause, but we've seen it happen and it's actually quite hilarious:

Check that you still have TCP ports available for creating network connections to your mail server. netstat.exe is a useful tool for diagnosing that.

We've had that happen when we configured an automatic e-mail for any error in RC, but with no e-mail address actually filled in to send those errors to.

The result is that when any error occurs RC creates a connection to the mail server and then the mail server starts waiting for an e-mail address that never arrives. The port remains open.

After a while a time-out occurs and a new e-mail attempt is started and eventually you have almost 64000 TCP ports in use and that's the end of any attempt to send out any other TCP traffic.

Thank you all so much! Turns out there was a problem with our internal mail server. I just received a flood of emails.

I will make note of these proposed solutions for the future!

Thanks again, all!!