Set up for access manager fails with this error. Pl. Help

Question

Bug Report Form
An error has occurred while executing the application.
Your browser does not support automatic mail sending.
Please E-Mail to the following information
Your Name
Organization
E-Mail Address
Phone Number
Comment
Make sure to append the following traceback in the mail.
Traceback \Oblix\coreid\palantir\webplugins\src\setup_admin.cpp:10389: Error: Exception re-thrown in SetupAdmin HandleEvent()
\Oblix\coreid\palantir\webplugins\src\setup_admin.cpp:10604: Error: Exception re-thrown in SetupAdmin HandleEvent()
\Oblix\coreid\palantir\webplugins\src\setup_admin.cpp:4589: Error: Exception re-thrown in SetupAdmin::GenProcessLDAPPersonOC()
\Oblix\coreid\palantir\webplugins\src\setup_admin.cpp:4119: Error: Exception re-thrown in SetupAdmin::CreateConfigInfo()
\Oblix\coreid\palantir\dblib\src\obconfig_db.cpp:460: Error: Exception re-thrown in ObConfigDB::Flush()
\Oblix\coreid\palantir\dblib\src\ldap_config_db.cpp:519: Error: Exception re-thrown in LDAPConfigDB::WriteOblixDBConfig()
ldap_util_failover.cpp:135: Error: Exception re-thrown in LDAPCompareAttrWFailover()
ldap_util_failover.cpp:121: Error: Unable to compare attributes - No such object in LDAPCompareAttr()
Product NetPoint User Manager Version
Platform Microsoft Windows
What to do???

Answer 1

Hi ,
This message occurs when the listener on the remote node cannot be contacted.
Did you add the host name and IP in your DNS server?
You can try tracing the path or the route a connection is taking from the client to the server. If it encounters an error, then it returns the error stack which gives us more information when compared to an cryptic one line error.
Execute the following:
trcroute host_name
This will help you find the problem and fix it. The problem may fall into one of the following areas:
Check TNSNAMES.ORA:
The TNSNAMES.ORA may contain a wrong address. Check the host and port have been specified correctly. Check the details against the LISTENER.ORA file.
Check the remote node:
Check if the listener has been started on the remote node. Check the status with the STATUS command of the listener control utility (lsnrctl):
lsnrctl
lsnrctl> status listener_name
listener_name is the name of the listener defined in the listener.ora file. If you have not changed the listener name, then it would be called LISTENER.
If the listener has not been started, start it with the command:
lsnrctl> start listener_name
You can check if the fix worked by executing tnsping. It should return an "OK" message if the TNSPING has been successful.
Thanks..
Mohit