#793 rxapi service does not start


ooRexx 4.0.0
Windows XP SP3

The installer was directed to install to "F:\Program Files\ooRexx" instead of the default "C:\Program Files\ooRexx". When the installer tried to start the RXAPI service, it failed -- its image path was "C:\Program Files\ooRexx\rxapi.exe". I edited the registry to change it, and manually started the RXAPI service, so there is a workaround.


  • Mark Miesfeld

    Mark Miesfeld - 2009-08-22

    The only way I see that this is possible is:

    • A previous version of ooRexx is installed in C:\Program Files\ooRexx with rxapi installed as a service

    • When the message box comes up prompting the user to uninstall the previous version, they say no, don't uninstall the previous version, and then continue with the new install.

    • When the new install prompts the user to stop the running rxapi, they say no.

    In that case, the old rxapi service is not uninstalled, and when the installer tries to start rxapi, it fails because it is already running.

    Since installing without removing the previous version is not supported, I think the bug here is continuing with the install when either the user does not uninstall the previous version, or the user does not stop rxapi.

  • Stephen Rondeau

    Stephen Rondeau - 2009-08-23

    I did remove the previous installation, but did not stop the rxapi service -- I thought the uninstaller would uninstall everything, including removing the service. I also did not restart.

  • Mark Miesfeld

    Mark Miesfeld - 2009-08-23

    Okay, I'll retry that scenario.

    The uninstall will remove everything, but the rxapi service has to be stopped. If it is not stopped, it can not be removed as a service. I think that will put us back to the final part of my first outline. The new install will finish okay, the old rxapi will not have been stopped, so the installer will say it can not start rxapi, (because it will already be running.) Since the old rxapi service is not uninstalled, the OS will not have changed the path to that old rxapi.exe.

    All, in all, it is a hole in the installer. We recommend that rxapi be installed as a service. On an install where an existing version of ooRexx is detected, we recommend it be uinstalled. And, when the installer detects rxapi is running, we recommend it be stopped.

    The reality is that you must stop rxapi and you must uninstall the previous version of ooRexx. If you don't, the new version will not be installed correctly.

    Just some FYI. You do not need to restart the system on an install. You can uninstall the rxapi service from the command line, and install it. In your situation you could of done the following to fix things:

    F:>"C:\Program Files\ooRexx\rxapi" /u
    F:>"F:\Program Files\ooRexx\rxapi" /i

    But, I would hardly have expected you to know that. <grin>

  • Mark Miesfeld

    Mark Miesfeld - 2010-08-17

    Committed revision 6114.

    "I did remove the previous installation, but did not stop the rxapi service"

    The installer has been fixed so that it will not proceed if rxapi is not stopped. The user is given adequate warning and plenty of chances to quit if she does not want to stop rxapi.

  • Mark Miesfeld

    Mark Miesfeld - 2010-09-16

    Committed revision 6196.

    4.1.0 merge.

  • Mark Miesfeld

    Mark Miesfeld - 2010-12-05

    The fix for this item was in the 4.1.0 release.

  • Comment has been marked as spam. 

    You can see all pending comments posted by this user  here

    Anonymous - 2015-07-30

    How did you start the rxapi? How can you be sure it was started.



Cancel  Add attachments

Get latest updates about Open Source Projects, Conferences and News.

Sign up for the SourceForge newsletter:

No, thanks