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.
We have some reports built with InfoAssist, that can't be opened again with InfoAssist: Code: 0 Type: xFDMinit Failed to do FDMinit
The error message doesn't help us. We have no idea, which reports are affected. Replacing ACROSS by BY in the text editor enables the reports to be opened by InfoAssist again. But this only the start of a nasty Workaround.
Horst Ebert
8.0.09 on Windows HTML, Excel, PDF outputsThis message has been edited. Last edited by: <Kathryn Henning>,
I have been seeing this issue also, yet we don't have an ACROSS so Horst's workaround won't work for us. If this issue was occurring for only one report then we would just recreate it although that would be a hassle, but this seems to be occurring with multiple reports and for multiple users.
WebFOCUS 7.6 Windows, All Outputs
Posts: 26 | Location: Atlanta, GA | Registered: July 13, 2012
We typically see this when the underlying metadata has changed. For example, the report utilizes a field where the field name has changed. The workaround for us thus far has been to try to find the offending field and manually make the correction in the text editor.
A bit of a bright spot... we are running 8104 in our test environment, and there appears to be error handling to mitigate this issue. The user is presented with a dialogue box stating the metadata has changed and it then gives them the opportunity to select the correct field.
WebFOCUS 8.1.05, Windows 7, All output types
Posts: 13 | Location: Alpharetta, GA | Registered: May 30, 2014