Resolution
=============
Beginning with the EMS 5.1 release, the EMS daemon is no longer statically linked but EMS install will create symbolic link automatically.
The issue occurs due to the installer not creating some symbolic links on the lib directory of the EMS install.
Try to run ls -lrt and verify the output with a below a sample 8.3 lib:
[jsinghal@localhost lib]$ ls -lrt
lrwxrwxrwx. 1 jsinghal root 20 Aug 6 04:27 libcrypto.so -> libcrypto.so.1.0.0
lrwxrwxrwx. 1 jsinghal root 15 Jul 6 04:27 libssl.so -> libssl.so.1.0.0
lrwxrwxrwx. 1 jsinghal root 13 Jul 6 04:27 libz.so.1 -> libz.so.1.2.8
lrwxrwxrwx. 1 jsinghal root 13 Jul 6 04:27 libz.so -> libz.so.1.2.8
lrwxrwxrwx. 1 jsinghal root 21 Jul 6 04:27 liblber.so -> liblber-2.4.so.2.10.3
lrwxrwxrwx. 1 jsinghal root 21 Jul 6 04:27 liblber-2.4.so.2 -> liblber-2.4.so.2.10.3
lrwxrwxrwx. 1 jsinghal root 21 Jul 6 04:27 libldap.so -> libldap-2.4.so.2.10.3
lrwxrwxrwx. 1 jsinghal root 21 Jul 6 04:27 libldap-2.4.so.2 -> libldap-2.4.so.2.10.3
lrwxrwxrwx. 1 jsinghal root 16 Jul 6 04:27 libxml2.so -> libxml2.so.2.9.2
lrwxrwxrwx. 1 jsinghal root 16 Jul 6 04:27 libxml2.so.2 -> libxml2.so.2.9.2
Double check them if they are present in your library, if they are not present, please reinstall them.
It is suggested to create the symbolic link for all the library file.
Creating symbolic links works correctly
eg:
ln -s libcrypto.so.1.0.0 libcrypto.so
ln -s libssl.so.1.0.0 libssl.so
ln -s liblber-2.4.so.2.10.3 liblber.so
ln -s liblber-2.4.so.2.10.3 liblber-2.4.so.2
ln -s libldap-2.4.so.2.10.3 libldap.so
ln -s libldap-2.4.so.2.10.3 libldap-2.4.so.2
ln -s libxml2.so.2.7.6 libxml2.so
ln -s libxml2.so.2.7.6 libxml2.so.2
Link to create symbolic links:
https://www.cyberciti.biz/faq/unix-creating-symbolic-link-ln-command/