FilePro install and license manager service

[Richard Kreiss]

This is mostly for Windows users as I have not done this on a *nix or other OS install.

I already posted that I had some "issues" with the fplm_service not starting on a client computer.  I had to  keep them on the 5.8 version they were running.

I wanted to update my version of 5.8.03 to the EOL version 5.8.03.24.  As I was already running 6.0 on my system and fplm_serivice was installed, I selected not to install the license.  After installing the 64 bit version and receiving an error message about the license manager service, I did some checking.


1.      The install procedure stops the license manager service

2.      It then creates the new service using the install path

3.      Then the service should restart

This is correct as long as one is installing or updating in the same location.  In my case, I was not.  The service was using my 6.0.00 location, w:\databases\fp60 is the folder(directory) where fp is located on my server.  Hence the service would not start as it was looking in the wrong place.  I had to create my own service.  Filepro has supplied a batch file for doing this.  The batch file had to be modified to use the location where filePro was installed.  The other thing to keep in mind, this must be done as an administrator.  Although I am logged in as an administrator, I had to right click on my command icon and select "run as Administrator."  I had to do this as I needed to delete the service that the filePro install had set up.  Run  "sc delete fplm_service" from the command prompt (no quotes).  Then I ran the modified batch file as an administrator.  From the command line, again, I ran sc start fplm_service.  Doing this I could see if the service started or if there was a problem.  Next, I selected the service icon and went to the fplm_service and changed the property to auto start.

Keep in mind that if you modify the batch file supplied the command line must end with fp and not just the folder(directory) where filePro is located.

Here is the command to create my filePro 6.0.00 service: sc create "fplm_service" binpath= "W:\Databases\fp60\fp\fplmservice.exe W:\databases\fp60\fp"

I strongly recommend using the supplied batch file as the spacing of the command is imperative.

Note that the folder is fp60  is where FilePro 6.0 64 bit is installed and that the last entry is the full service path to where the executables are located.  Leave that fp off and you will get a windows error which is not very helpful except to advise you to contact FP Tech support as this is not a MS program.

If I install the 32 bit version of 6.0 it will be in fp60_32.

Note that all versions of filePro at or below the installed license will run.  I have versions 5,5.6,5.7, 5.8 and 6.0 running on my system also  4.0, 4.1, 4.5.  4.8 has an issue as the dll files require a 32 bit OS and not a 64 bit OS.  When I need to run 4.8, I go back to a computer with Windows 7 32 bit. I do have a laptop with Windows XP on it.

As an aside, the install assumes that one is installing filePro in the same location.  That is why the service is stopped.  If it weren't stopped, the program fplm_service could not be replaced during an update.  I have added to the wish list a request that the install program check to see where the service is pointing to ands if different not stop the service.  If it does stop the service, the install should advise that it has stopped the service especially if it can't be restarted.

If one is manually creating the fplm_service to replace the current service, remember to delete it as an administrator even when logged in as an administrator. i.e. run the sc command as an administrator from the command prompt or run the batch file(script) as an administrator.



-------------- next part --------------
A non-text attachment was scrubbed...
Name: winmail.dat
Type: application/ms-tnef
Size: 20672 bytes
Desc: not available
URL: <http://mailman.celestial.com/pipermail/filepro-list/attachments/20190110/352b2197/attachment.bin>