Wrapper issues - OpManager will not start

Wrapper issues - OpManager will not start

From wrapper.log

STATUS | wrapper  | 2011/10/17 13:38:25 | --> Wrapper Started as Service
STATUS | wrapper  | 2011/10/17 13:38:26 | Launching a JVM...
INFO   | jvm 1    | 2011/10/17 13:38:28 | WARNING - Unable to load the Wrapper's native library 'wrapper.dll'.
INFO   | jvm 1    | 2011/10/17 13:38:28 |           The file is located on the path at the following location but
INFO   | jvm 1    | 2011/10/17 13:38:28 |           could not be loaded:
INFO   | jvm 1    | 2011/10/17 13:38:28 |             C:\PROGRA~2\MANAGE~1\OPMANA~1\lib\wrapper.dll
INFO   | jvm 1    | 2011/10/17 13:38:28 |           Please verify that the file is readable by the current user
INFO   | jvm 1    | 2011/10/17 13:38:28 |           and that the file has not been corrupted in any way.
INFO   | jvm 1    | 2011/10/17 13:38:28 |           System signals will not be handled correctly.
INFO   | jvm 1    | 2011/10/17 13:38:28 | 
INFO   | jvm 1    | 2011/10/17 13:38:28 | Wrapper (Version 3.1.1) http://wrapper.tanukisoftware.org

This is the only log updated upon a failed start. 

We have seen this in the past, typically a restart of services or reboot of the server resolves it. 

Sometimes, it appears after a DB issue, in which the RepairDB script is run, then a restart of services resolves it.

Forums seem to have seen similar issues, please let me know what else may be required to assist in diagnosing this issue.

                  New to ADSelfService Plus?