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.
Found a series of cases on tech support for this: 10602123 11672044 83521027 92091142
Resolutions varied -- in some instances it was version issues with .jar files. In some it was putting a space between the & and the spot marker. Take a look. One might be similar to your release, environment, code, etc.
If you don't have an account with tech support, go ahead and create one. There is a lot of useful information available there. (You will need your site code). Searching on this topic resulted in 75-100 hits.
Posts: 118 | Location: DC | Registered: May 13, 2005
The cgivars file has what you mentioned but still it doesnt work. is it some problem with the version of WF that i have installed. This error occurs whenever i define a parameter and run the report.
i got this all the time while i was testing 533. for me, it was always an &var problem, always. Once i made sure all the &vars were initiallized, the problem went away. but then of course, so did 533...we tossed it. i started the fix by writing the code in smaller segments...one executable paragraph at a time...starting from the top of the fex. Just slapping a -EXIT into the existing full code didn't help...i had to start a new text fex, and incrementally add paragraphs until i found the errant &var. They all had to be initialized. works differently from 52. And of course we also had win2003 sp1..which we also just tossed. we rolled back sp1 in prep for trying 534.
Posts: 3811 | Location: Manhattan | Registered: October 28, 2003