I have upgraded from 7.6.0 to 7.6.6 (requires a full reinstall) and now my group view returns a "There are no agents available on reporting server: EDASERVE" error when it attempts to run a report.

Here's the funny thing though -- if I go to Dev Studio and run a report first (which works fine) the dashboard begins to function properly. If I close the dashboard and re-enter, it fails again. It requires a Dev Studio run before it will work properly in dashboard.

Any insight?

J.

This message has been edited. Last edited by: Kerry,

John, is this an upgrade of a server or DS ?

Could your odin file need configuration ??
Could it be pointing to the wrong port ?

WF Client only.

This is pure speculation, but have you checked the WebFOCUS Server console for the number of agents ready?

Workspace > Configuration > Data Services > number_ready

The agents are ready to go, and they function correctly once Dev Studio has connected. The basics are all in place. For some reason the dashboard (my guess is that it's some setting or variable in IE) does not have sufficient information to run and the error I'm seeing is a red herring.

Very strange.

J.

Can you run the same report from MRE?

Question,

Do do have Dev Studio open when you start the dashboard?

I have seen this problem before when both Dev studio and dashboard are open at the same time (or MRE java app and dashboard).

They appear to be incompatible because of the cookies they set, rewrite and screw up.

The scenario of Opening, closing and opening Dev studio would suggest that this may be the cause.

John, I think you will find that Waz is correct on this one. I've seen a few upgrades in the last months where the same thing was happening. Open the WF Client admin console, and goto "Reporting Servers/Remote Services", and check the setting for EDASERVE. The host or port could be wrong.

Good question bud -- no, won't run from the MRE applet either. I get the same behavior where it runs once I've run in Dev Studio. That likely takes Dashboard out of the equation. Here's the url created by the java applet:

http://10.140.5.253:8080/ibi_a...9131765976425414135&

Note that this routine was created when the 7.6.0 client was in place.

The entire focexec in MRE is this one line --
-MRNOEDIT -INCLUDE applicant_startup.fex

This is about as straightforward as it gets . . . unless it's not managing the NT box security . . . it's not challenging me for an ID on the server! That's the heart of it. Dev Studio has a userid set for Client access. It's not serving up a login page.

J.

Ok, so I start the Reporting Server with security off and everything runs hot and straight. So the problem is that the 7.6.6 Client is not playing nice with the 7.6.5 Reporting server. This HAS to be a configuration issue. A 7.6.5 server should work just fine with a 7.6.6 Client.



Right?

i've never known anyone to tackle upgrading the client w/o uping the server as well.
I've seen lots of 'other way 'round' b/c client is so hard and server is so easy.
This is one for the recordbooks, John. Gutsy

Susannah is quite correct.

Client can be lower than a server but should never be higher than a server.

.


The Client required a Pre-Prompt setting in the WF_AutoSignon field. All is well now.

Had the error message mentioned security in it somewhere this likely would have taken 30 minutes to fix instead of hours. Lesson learned.

J.