Could not contact Service Manager FNDSM_xxxx_xxx . The TNS alias could not be located

Problem:

When attempting to start concurrent manager, below message occurs in internal manager log file for every non concurrent processing node but concurrent manager is up and running as expected.

Due to this issue, internal manager log file is having irrelevant messages related to concurrent processing which is creating confusion.

Contents of ICM log file:

 Could not contact Service Manager FNDSM_<hostname>_XXXX . The TNS alias could not be located, the listener process could not be contacted, or the listener failed to spawn the Service Manager process.
                     Process monitor session ended : 03-JAN-2014 20:46:26

Cause:

As per the log file, FNDSM listener was trying to connect to server   FNDSM_<hostname>_XXXX and we do not have concurrent manager running on <hostname> server.

For every non concurrent processing node you can see below messages in internal manager log file.
========================
Could not contact Service Manager FNDSM_<HOSTNAME>_<SID>. The TNS alias could not be located, the listener process on <HOSTNAME> could not be contacted, or the listener failed to spawn the Service Manager process.
========================

If the Service Manager is not present/defined for a particular node, then this causes all the services provided by Service Manager like OPP,WF etc.. not to work. 

Either Start APPS/FNDFS listener for each non concurrent processing node manually or upgrade oracle application to Release 12.0.6.

Solution:

This issue was fixed as part of a number of enhancement requests and was fixed in Release 12.0.5 but released in 12.0.6.

Service Manager: <HostName> on any node will start if node will be a concurrent processing node.

For a Concurrent Processing node :
========================
Service Manager: <HostName> => Actual Process = Target Process = 1

Navigate to System Administrator => Concurrent => Manager => Administer => Query for Service Manager: <HostName> => Click on "Processes" => You will see an "Active" process.

But for a Non Concurrent Processing node :
========================
Service Manager: <HostName> => Actual Process = 1, Target Process = 0  

In our case, we deactivated the Service Manager:<hostname> to fix the issue.

Note: <hostname> of the Non Concurrent Processing node

References:

Concurrent Manager Fails To Start With Error 'Could not start Service Manager FNDSM_<server>_<SID>' Error (Doc ID 423170.1)

Concurrent Processing - Internal Manager Log File contains messages "Could Not Initialize the Service Manager FNDSM_<HOSTNAME>_<SID>" for Non Concurrent Processing Nodes (Doc ID 754698.1)

Unable to Bring Up Concurrent Managers after Running Autoconfig (Doc ID 736024.1)

Apps Listener Starts But Fails to Spawn The Service Manager FNDSM (Doc ID 1073677.1)

Concurrent Processing - R12 Output Post Processor Service Not Coming Up. (Doc ID 460578.1)