Day: May 16, 2007

Some times when we make a concurrent request and try to view the log file after complition of request (may be completed normal or some error) from the concurrent manager form we get following type of error

An error occurred while attempting to establish an Applications File Server connection with the node FNDFS_(Your env_name)_(Your_Server_name). There may be a network configuration problem, or the TNS listener on node FNDFS_(Your env_name)_(Your_Server_name) may not be running. Please contact your system administrator.

In this case you need to set one profile which will fix this issue. You need to set the value for RRA: Service Prefix to FNDFS_(Your_Env_name)_.

This can be done using navigation Profiles –> system.

If the concurrent manager is not responding and there are lot of pending request from long time then those request can be killed from the backend using the following query.

UPDATE fnd_concurrent_requests
SET phase_code = ‘C’, status_code = ‘D’
WHERE status_code =’Q’ OR phase_code = ‘P’
AND REQUEST_ID = ;

You can kill all the long running requests.
Also one more option that can be done is login as apps/apps. Also we can make the internal manager to work like a CRM by setting the profile option
Internal Manager: work like CRM to yes.

Concurrent: Use ICM is the profile name

If u r getting Target node/queue unavailable in status column then in the manager –> define form check the Conflict resolution manager node. It should be set to correct node value. Set it to correct value and bounce the CM. By default this value is never set. It will take the node from FND_NODE table.