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 got this error and spent three hours trying to figure out what was wrong. The program worked just fine when run from Dev Studio, but failed in RC.
I finally figured out that the last character in fex file was a binary 00. How it got there is a mystery, but I suspect that it was put there by the Dev Studio text editor. I normally edit files with my favourite external text editor, but I think I made a change using the internal text editor, which introduced this character.This message has been edited. Last edited by: Francis Mariani,
Francis
Give me code, or give me retirement. In FOCUS since 1991
Production: WF 7.7.05M, Dev Studio, BID, MRE, WebSphere, DB2 / Test: WF 8.1.05M, App Studio, BI Portal, Report Caster, jQuery, HighCharts, Apache Tomcat, MS SQL Server
Dev Studio 8.0.08 - when opening a fex in an external text editor, a 00 hex character is added to the end of the file. If you save the file, the hex character is saved along with file. This causes Report Caster to fail. This occurs with fexes located on the reporting server or in the repository. I've tested with EditPlus, UltraEdit and Notepad.
Francis
Give me code, or give me retirement. In FOCUS since 1991
Production: WF 7.7.05M, Dev Studio, BID, MRE, WebSphere, DB2 / Test: WF 8.1.05M, App Studio, BI Portal, Report Caster, jQuery, HighCharts, Apache Tomcat, MS SQL Server
I found my issue. It was a ';' on a line by itself. When running in dev studio it ignored the error and continue to complete the report, but went run in RC it completed running the report but just would not distribute it. This then placed the error at the end of the report, making it look it that was where the issue was when it actually happened at the beginning.
I have a habit of putting -RUN statements after every TABLE or DEFINE END statement. I put a -RUN after FILEDEF and JOIN statements. If there is an error, the error will be displayed at the -RUN statement, not at the end.
Francis
Give me code, or give me retirement. In FOCUS since 1991
Production: WF 7.7.05M, Dev Studio, BID, MRE, WebSphere, DB2 / Test: WF 8.1.05M, App Studio, BI Portal, Report Caster, jQuery, HighCharts, Apache Tomcat, MS SQL Server
This is to inform you that a Dev Studio 8.0.08 Hot Fix is available (DS-90_DS8008HF.zip) which solves the "00 hex byte at end of file" bug. Hallelujah.
Francis
Give me code, or give me retirement. In FOCUS since 1991
Production: WF 7.7.05M, Dev Studio, BID, MRE, WebSphere, DB2 / Test: WF 8.1.05M, App Studio, BI Portal, Report Caster, jQuery, HighCharts, Apache Tomcat, MS SQL Server