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 thought that I would post this, and perhaps any others that have encountered weird WF8 errors can post in here too.
This error we encountered in WebFOCUS 8.1.04 was :
WebFOCUS Error (1059)
Unregistered error.
The issue was that we had made a call to an HTML page without supplying the page name, just the location.
The underlying cause was a -SET statement that was coded badly, the IF did not have an ELSE and caused the file name to be blank.This message has been edited. Last edited by: Waz,
We also are getting funny things happening with 8.1.04.....We are finding that characters are getting dropped off output from when we run the following code:-
I have one. Today I started getting the 1059 error on one of my portals. This was on a pie chart. We have several different clients, all using the same set of reports, with different parameters. Only 1 of the clients was getting the error, and only on data that was collected yesterday. I combed through the data, and could not find anything that might cause a strange error. On my graph, I have a command SUM CNT.thefield AS ' ' (note 2 spaces in the AS). On a whim, I removed one of the spaces, and now the thing works.