If the module is not giving you any useful error information then you have several courses of action. You should consult the documentation for the module. If that is unhelpful then contact the supplier. Otherwise you are reduced to tracing the kernel calls.

Tracing the kernel calls should give you the exact errors and object names if the problem is related to permissions, as you suspect. You will need a tool such as truss (on Sun) or strace (on Linux, and others). Display the process PID ($$), or write it to a file, then pause your process just before the shared object is created. Then attach truss or strace to the process using the -p option. You will need to be signed on as the same userid, or root. Now allow the application to continue. Once you get sufficient information then kill the truss/strace using <CTRL>C. If there is too much data output (and there often is) then use the -o option to save it to a file for later analysis.