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 have received the following suddenly from a reportcaster job:
BTP1010 Error connecting to the WebFocus Reporting Server EDASERVE: EDA SQL STATUS (-30) ... BTP1010 Task error: Server disconnected, cause 32007 Eda State -30
I have read in the error code manuals that 32007 equates to 'Client disconnected due to communications error' and that -30 indicates 'Invalid Protocol'. Can someone help me understand what that means?
We had issues on this server later in the day where directory/file permissions in c:\temp were affecting the ability to log and hold files. This was addressed by an explicit permissions setting (versus inheritence) and the server was rebooted several times in the process of diagnosing and fixing (so the edaprint logs have been flushed).
I'd just like to give my management a definitive root cause and put some safeguards in place me prevent this in the future.
Thanks for your help!
-ABTThis message has been edited. Last edited by: ABT,
I consulted with our internals and was suggested that, this error most likely is the result of another condition, that is, something else occurred on the Reporting server, an error in the procedure, which caused the client disconnect. Without the Edaprint and traces, it would be very difficult to determine what actually caused the condition. So, please watch it for now and if reoccurs, open a case with Customer Support Services for assistance. The phone number is 1-800-736-6130, or access online at InfoResponse.
Cheers,
Kerry
Kerry Zhan Focal Point Moderator Information Builders, Inc.
Posts: 1948 | Location: New York | Registered: November 16, 2004