There is an increase in the load on the reporting server due to increased number of users accessing the applications. What are all the measures in terms of server settings that can be taken to avoid the server crashing ?
We keep getting the follwoing error most of the times and then we need to restart the server to recover

There are no agents available on reporting server: EDASERVE
Please submit your request again or notify your server administrator.

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

Increase the maximum number of agents if you have the resources available mainly memory related.
Also turn on Queuing which means jobs will wait until an agent is free.

If you are having problems because of crashed agents you can also add crashed_cleanup=on
to the workspace configuration file. This will release resources and remove dumps that take up space.

You will need to turn it off again if you want to run any traces or debug.

Thanks for your response JG.

As of now, I have four agents running, two in DEFAULT and two in WC_DEFAULT. How can I add more agents and how do I check on the memory constraints.

Will adding crashed_cleanup=on help in the recovery of my crashed agents? Is this by any chance what you mean by releasing resources?

Reporting Server Console: Workspace pulldown: Configuration/Data Services. Open Properties and make the change, if you are an admin.

Sounds like you need to go back through the documentation to understand administration of the WF server. The agent running in the WC_DEFAULT service are not available for regular WF request. The WC means Web Console. Those agents only serve requests issued from the WF Server console via the HTTP listener.

There are a number of things you need to understand that will affect the number of agents available. Read up on the items JG and Ginny mentioned, as well as queuing, max agents, number ready, agent refresh rate (and everything else in the server admin manual.)