[CLOSED] No Free Agents Available Error

November 02, 2012, 03:05 PM

Joey Sandoval

Has anyone experienced this error when trying to access the Reporting Server Console (EDASERVE) " No free agents available on the server to process the request at this time. Try again later."

We checked the agents currently running and there were only about 15 running..

Thank you.

This message has been edited. Last edited by: Joey Sandoval,

November 04, 2012, 05:15 AM

WF_IL

Hi

I have encountered this issue with 8001 server,
Restarting the WFRS resolved this issue,
Also setting agent_refresh=100 made this issue to occur rarely.
I would recommend you to open a case with IBI tech support (you could reference our case which describes similar symptoms 82992509 )

November 04, 2012, 10:06 AM

ABT

see my recent(ish) thread on the same thing: http://forums.informationbuild...1057331/m/4867077606

For what its worth, those changes have worked perfectly for us, I haven't received that message since making the change.

- ABT

------------------------------------
WF Environment:
------------------------------------
Server/Client, ReportCaster, Dev Studio: 7.6.11
Resource Analyzer, Resource Governor, Library, Maintain, InfoAssist
OS: Windows Server 2003
Application/Web Server: Tomcat 5.5.25
Java: JDK 1.6.0_03
Authentication: LDAP, MRREALM Driver
Output: PDF, EXL2K, HTM

------------------------------------
Databases:
------------------------------------
Oracle 10g
DB2 (AS/400)
MSSQL Server 2005
Access/FoxPro

November 05, 2012, 10:55 AM

Joey Sandoval

Thanks ABT. So Did you end up setting the agent_refresh parameter to equal 1 on all data services or just WC_DEFAULT?

I created a case with IBI and they also suggested changing the Maximum value from 2 to 5 or more, depending on how many users we have connecting to the web console.

November 05, 2012, 11:42 AM

ABT

quote:
Originally posted by Joey Sandoval:
Thanks ABT. So Did you end up setting the agent_refresh parameter to equal 1 on all data services or just WC_DEFAULT?

I created a case with IBI and they also suggested changing the Maximum value from 2 to 5 or more, depending on how many users we have connecting to the web console.

Here's my current EDASERVE.cfg (appropriate sections):

crashed_cleanup = on
SERVICE = DEFAULT
BEGIN
  maximum = 50
  number_ready = 2
  agent_refresh = 1
  maximum_q = 10
END
SERVICE = WC_DEFAULT
BEGIN
  maximum = 2
  number_ready = 2
  maximum_q = 20
  agent_refresh = 1
END
SERVICE = DFM_DEFAULT
BEGIN
  maximum = 10
  number_ready = 0
  agent_refresh = 1
  maximum_q = 10
END

I may not have done everything "the smart way", but its effective. ;-)

- ABT

November 05, 2012, 11:44 AM

ABT

FWIW, I don't even know what hits the WC_DEFAULT queue....

November 05, 2012, 04:30 PM

Joey Sandoval

IBI has informed me that updating agent_refresh is no longer necessary on our release. However, I did update the max and number_ready values to 5 as recommended. Thank you all for your input.