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.
I wish I could discuss this over a XXXX at Circular Quay or some other place, but I have'nt got very much more information than you've got. We're on a Windows Server, SQL Server 2005 and WF 7.6.10. I bounced the WF and RC servers and it seemed to solve it, at least temporarily. I did'nt check it the last hours before COB. The only clue I can provide you with is that we had a number of Report Caster jobs falling over. I don't know, it might be a Java issue, cause there were a number of RC jobs having really odd Java messages (also not seen before).