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.
Does anyone here have any idea where I can get the meaning of the command return code 9 in the Resource Mgmt Monitoring tables??? Preferably code 9 and 96? Been looking in the docs, SSMS, etc. Can't find anything! SO FRUSTRATING!This message has been edited. Last edited by: CoolGuy,
8.2.02M (production), 8.2.02M (test), Windows 10, all outputs.
Posts: 1113 | Location: USA | Registered: January 27, 2015
Nevermind. We figured out what the issues were and have addressed them. Figuring out how to decrypt random undocumented return codes is now no longer relevant.
Thanks anyways!
8.2.02M (production), 8.2.02M (test), Windows 10, all outputs.
Posts: 1113 | Location: USA | Registered: January 27, 2015
The issue was unrelated to the BI layer. The report in question is being triggered from an internal ASP page that requires login before one can submit a form to the report. People were logging in as one person, and another person was attempting to run a report as themselves despite another already being logged in with a different set of access privileges. Also, there is a time out on parameters being available to pass to the report from the ASP layer. A specific parameter was null after a certain period of time had passed with the users' sessions. Thus creating the few issues we were having.
8.2.02M (production), 8.2.02M (test), Windows 10, all outputs.
Posts: 1113 | Location: USA | Registered: January 27, 2015