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 am trying to add a task to a report caster schedule. The task is an EXL2K output with three worksheets. The query works in MRE.
When I try to add the task to report to a report caster task, I get the error message:
"Error occured when processing the Managed Reporting procedure information. Possible cause of this error is an ureadable character withing the procedure."
Has anyone come across this before, and do you know what would identify an unreadable character or how to correct this error message?
2 things, first try runnig your report in MRE but stop it before the print step. I am fairly sure thta you will see the error, but MRE allows the report to print even with the erro. Second, the actual error may be in a .mas file, do take a look in your .mas files for bad character.
WF 7.6.11 Oracle WebSphere Windows NT-5.2 x86 32bit
To display the code without executing it, add -SET &ECHO=ON; -SET &STACK=OFF; (and remove that -EXIT), then run again in RC.
From the text of the error message, it rather sounds like it was issued by MR as it read the fex ("procedure"), not by the reporting server. But how much can one infer from a misspelled message?
Posts: 1925 | Location: NYC | In FOCUS since 1983 | Registered: January 11, 2005
Check your MRE fex for tab characters. Older servers ignored the tab but now they can error on that. The MRE front end removes tabs when it executed the fex. Caster execution does not (never has). We attempted to remove the "clean tabs from the fex" behavior in the MRE client but it caused a few accounts a lot of headache. (1000s of fexs, tabs everywhere,...) So while I do not like the fact we clean the tabs - we have to live with it...
Brian Suter VP WebFOCUS Product Development
Posts: 200 | Location: NYC | Registered: January 02, 2007