Issue: Cannot fetch Agent errors in smps log
error 'Cannot fetch agent <agent-name> agent' (or)
error 'Cannot fetch agent rm68mlez4nymx/84ghafegu8szctihxhazdwm36bjoffghbqrkh2akoxdischjcq'
Windows, Linux, Unix
In general, cannot fetch agent means policy server unable to locate the agent. When web agent intercept the request, it needs to pass the agent name and target resource to policy server in order for it to check if the resource is protected or not. If the agent name pass in is invalid due to some reason, then we expect to see this error message.
Some of the common issue is end user has bookmarked the login page and the agent name has changed after upgrade. Try to access the protected resource directly without go thru bookmark and check if that make any different.
If the issue is not due to bookmark and happen consistently, try to check the realm that having the problem and make sure the agent exist. Alternatively, you can try to recreate the agent and assigned it to realm and check if that helps.
If your agent name is encrypted, try setting the ACO “EncryptAgentName to No”, so that you can identify the agent causing this error.
1. Try to access the protected resource directly without go thru bookmark and check if that make any different.
2. Check the realm that having the problem and make sure the agent exist.
3. Try to recreate the agent and assign it to the realm.
Release: ESPSTM99000-12.51-Single Sign On-Extended Support Plus
Please Update This Required Field
There is DEFECT DE137802 fixed in 12.52 SP1 CR06 related to the 'Cannot fetch agent' message.