Try running ldconfig that will search and add all new libraries it finds. Maybe (but unlikely since ldconfig SHOULD run on every system startup) is the problem.
Try it, maybe it will work.
OR those libraries are in some unusual place the system does not look. Find where the are, copy them to /lib and run ldconfig.
Is this error generated by RPM? If so i heard that RPM sometimes does these things for no apparent reason. Make sure that those libraries have the EXACT same name as RPM requests. If they dont then make sym. links with the exact names that will point to those libraries.
hope that helps