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.
Your reporting server is running with OPSYS or operating system security and your admin has not supplied a default id for running WebFOCUS requests when coming in from a browser.
You have several options. You can add the IBIC_user and IBIC_pass to your URL though this isn't a good thing because of exposure.
You can have the admin add a default id in the WebFOCUS client console.
You can have the admin change to security off which I don't recommend.
Or you can use a logon page with a WF_SIGNON action to run your request after you logon.
Do a search on the techsupport website for WF_SIGNON to find a model that you can use.
After we restart the Server it is working fine.I am suspect due to the space issue it may be the issue for this error .Before i restart the server the space is 100% full ... is it makes this error?
I would expect a different error if you were out of space. Was the space in edatemp or just on the server? Did you have a bunch of crashed agents before the restart with core dumps?
At any rate, you might have had two problems.
Are you the server admin? Are you running with OPSYS security? You might want to check out the Unix Server Adminstration Manual to learn more about server security settings.
If you run out of disk space, i'd say all bets are off. Depending upon the action that was required at the time, you could've received an error based upon the fact that you couldn't authenticate against the reporting server because an agent couldn't be activated