As of December 1, 2020, Focal Point is retired and repurposed as a reference repository. We value the wealth of knowledge that's been shared here over the years. You'll continue to have access to this treasure trove of knowledge, for search purposes only.
Join the TIBCO Community TIBCO Community is a collaborative space for users to share knowledge and support one another in making the best use of TIBCO products and services. There are several TIBCO WebFOCUS resources in the community.
From the Home page, select Predict: WebFOCUS to view articles, questions, and trending articles.
Select Products from the top navigation bar, scroll, and then select the TIBCO WebFOCUS product page to view product overview, articles, and discussions.
Request access to the private WebFOCUS User Group (login required) to network with fellow members.
Former myibi community members should have received an email on 8/3/22 to activate their user accounts to join the community. Check your Spam folder for the email. Please get in touch with us at community@tibco.com for further assistance. Reference the community FAQ to learn more about the community.
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,
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.
WebFOCUS 8.1.03, Windows 7-64/2008-64, IBM DB2/400, Oracle 11g & RDB, MS SQL-Server 2005, SAP, PostgreSQL 11, Output: HTML, PDF, Excel 2010 : Member of User Group Benelux :