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've been getting this error quite a bit recently, but not all the time: Error attaching to Reporting Server: EDASERVE The reporting server may not be running or may not be properly defined in the Client Communication Configuration file.
Please notify your server administrator.
However after a bit of research, alot of cases tell us to double check the naming in the odin.cfg file. After we checked it, the naming seemed fine. The only differential was on some of the config files, the "HOST" name is localhost instead of the computername which is uses in other config files. However, after a quick reboot of the whole box, it would seem to "solve" this problem, and it wouldn't resurface until another 1-2 days.
Any suggestions on why this would happen? I have opened several tickets, however they are unable to resolve this issue since it was periodic.
Running: WebFocus Server 7.6.4 WebFocus Client 7.6.4This message has been edited. Last edited by: Kerry,
we had the same behaviour in our production system yesterday. A selfservice-app (IBIF_ex) called every 5 minutes printed this error once yesterday.
Also we had same errors from report caster too. A week ago, a schedule (running every 15 minutes/ 24/7, existing of 2 tasks) returned 2 different errors. Twice we received "EDA SQL Status (-9)" for 1 task, the first task was running fine. Four times we received "Error connecting to managed Reporting" for both the tasks.
The system is up and running since three weeks, and these error started a week ago. To me, these three error seem to be related somehow. But I have no clue where I could look next.
Could not find anything in Virus scan logs, edaprint, scheduler.log, windows event viewer, apache.log (there, these errors seem to have a different behaviour, but still no clue).
I looked into this for several hours by now, but could not find a hint, what's wrong. Furthermore, these errors are too sporadic at this moment, in order to get more information.
Regards, MArkus
WF 7.6.6 (MRE,BID, DevStudio, partly RC) on Windows 2003 /Apache/Tomcat Output: HTML,Excel,PDF,PPT Adapters: SQL Server, DB2, Oracle