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.
there is another new patch that was released on August 9 by Microsoft which fixes the issue that caused the reports to not open (the original issue was caused in mid July). As a work around, users can do save and open (instead of just open) or can actually do a save and go to the file. If they go to the file, some users need to click on properties and unblock the file. I'm told double click does not work on the file for some (but others it does ... depending on versions of browsers, etc.). If you google the fixpack from Microsoft, you find even more solutions (if you choose not to do their latest fix that fixes the previous problem ... some suggestions end up causing vulnerability so we did not go that route). This was when the issue was introduced: KB3115262, KB3170008, and KB3115322 and these are the fixes that correct the issue. 3115438 (office 2016), 3115455 (office 2013), 3115476 (office 2010). If you need additional solutions, just google the KB#.