Can you run the ftpdw.exe from the bin folder of the FTP server folder? If it does launch, go to the Java tab and make sure all settings (JVM path, Java Class Path). Make sure the folder in which you placed the DLL is in java.library.path. I'm not quite sure if jre\bin is automatically searched for DLLs or not. You can also place the DLL in any other folder and hopefully be able to add the path for the DLL in the ftpdw.exe window (under the Java Options using -D option).
If everything looks good, then I suspect you might be running into some permissions issue on the jar/dlls. Make sure the service is running under the correct profile (local system account or another valid local/domain profile) that has appropriate permissions to the FTP server folder and sub-folders. Finally, if UAC is ON, I would try turning that off temporarily and see if you get better luck. If none of this works, posting the log file (in debug mode) with complete stacktrace might help. Sai Pullabhotla On Fri, Aug 26, 2011 at 5:46 PM, Ian Goodacre <[email protected]>wrote: > Hi Sai, > > I too have been thinking of class and library path. > > I didn't change either: I added the SQL Server driver jar to ftpserver's > common\lib folder and the dll to java's bin folder. > > If I delete sqljdbc4.jar from the lib folder I get the same error when > running from the command line as the service produces but when I run the > service with the jar present I can see with process monitor that the jar > is found and read (at least in part) and that ftpd.exe reads classpath > from the registry and it includes this jar. So, I think the classpath is > OK and the jar is found by the service OK. > > Interestingly, when run as a service, the error is produced before > sqljdbc_auth.dll is read. In fact, I found no reference to > sqljdbc_auth.dll. > > When I run from the batch file much more of sqljdbc4.jar is read, there > are interactions with SQL Server and, eventually, sqljdbc_auth.dll is > also read. > > So, it appears that for some reason when run as a service sqljdbc4.jar > is accessed but for some reason doesn't accept the URI, without even > communicating with SQL Server. > > Ian > > > > > >
