Hi Ben,
sometimes the reason for the"missing" DLL is, that by accident a 32bit Java VM installation was in the PATH, when the SCC was started for the first time. This then leads to a failure to extract the DLL to the correct folder (32bit JVM cannot use 64bit DLL), and the DLL then remains missing, even if later a correct 64bit JVM is used...
Unfortunately it is not easy to "repair" an SCC installation, if its initial startup happened with a 32bit JVM. But in the newer SCC releases (don't remember exactly, but probably starting with one of the 2.7.x releases?!) there is now a built-in check in the Windows Service, and the SCC refuses to start, if it finds a 32bit JVM.
The easiest solution to "clean up" the SCC in such a case is probably:
- Copy DLL to Windows\system32, so the SCC can be started
- Export the configuration
- Uninstall the SCC and delete the DLL from Windows\system32
- Make a fresh installation (with 64bit JVM!) and import the configuration again.
Best Regards, Ulrich