No aRFC resources available for application server

If no aRFC resources are available for the specific application server, you will receive the message No aRFC resources were available after &1 seconds on server &2 and KPIs might be not collected for this specific server. This message means that the collector job tries to find a free aRFC resource for a specific server, but a resource was not available within N seconds.

There are two possible scenarios for when no aRFC resources are available:

• On a central server on which the collector job is executed. The collector job cannot be executed on this server because it does not have any aRFC resources available and no KPIs are collected.

• On a remote server for which the collector job tries to collect KPIs on a remote system from the central system. This server is excluded from monitoring, and the collector job will collect data from all available application servers except this specific server with no aRFC resources.

If you want to check the aRFC resources on a specific server, use transaction SARFC. In addition, you can check all running work processes on a specific server in transaction SM50. Make sure that you are executing these transactions on the specific application server:

• If it is a central server, start transactions on the central system and the relevant application server.

• If it is a remote server, start transactions on the remote system and the relevant application server.