After manually installing the Service on Windows Server 2003, Web Publisher is giving me error messages such as "Couldn't open database" and "Reference Manager Web Publisher is not available at this time". It might work fine with 'normal'/'non-service' Web Publisher but fails when Web Publisher is run as a service.
N.B. Since this article would normally only be of interest to your institution's IT Department, it assumes some knowledge of working with Windows Server 2003. Please contact us if there's any part you don't understand.
1. Ensure that Reference Manager is installed to the default location of C:\Program Files\Reference Manager 12\
2. Ensure that there are two instances of RMWP_Apache_Admin.exe running in the Task Manager. If there aren't, then Web Publisher service has not installed correctly. Please re-try the installation steps.
3. Open the database via a UNC path, not a mapped drive. Windows Services often have trouble resolving mapped drives. For example, when you go to publish the database, navigate to bit by typing: \\server\share\database name.rmx, not S:\my folder\database.rmx
If this fails, then the database will have to be hosted on the local machine.
NOTES: --In one case the database had to be located in the Database folder of the Program Files\Reference Manager 12. We suspect this was due to the configuration of the Server's security settings, but cannot confirm this.
--This is unique to Web Publisher running as a Service. If your IT Policy dictates that you're not allowed the Reference Manager database to reside on the local machine then you should run Reference Manager's Web Publisher is 'normal'/'non-service' mode, or try running it as a Service on Windows XP.
4. Ensure you're not trying to publish more than 15 databases.