I recently had an interesting support case that I thought deserved to be shared with everyone. Essentially the customer was unable to run FileCatalyst Server as a service on Windows 7 Premium with the Windows firewall up. After attempting several things we discovered that it was a permissions issue with Java and Windows 7 services. To fix this I edited the fcconf.conf file as an administrator and modified the following line:
to point to location of his Java like this:
(your path may differ). This allowed the FileCatalyst Server to be run as a service. FileCatalyst HotFolder will also behave the same and would need the same modifications. The configuration file is named fchf.conf.
In addition if you are running FileCatalyst Server or HotFolder on a Windows 7 Premium machine and you get an error popup when clicking “run at startup”. Open a command prompt as administrator; navigate to the directory where you have FileCatalyst Server installed. Then run the install_fcserver_service.bat this will install the FileCatalyst Server service.
For the most part, running applications “out of the box” is pretty painless, but when multiple versions of a technology may exist (Java 6 and 7 on the same machine, 32-bit and 64-bit versions on the same machine) or if your system path is misconfigured (simply providing “java” isn’t resolving to the JRE), you may find you need to explicitly specify a path.