[
https://issues.apache.org/jira/browse/DAEMON-143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mladen Turk updated DAEMON-143:
-------------------------------
Affects Version/s: 1.0.2
(was: 1.0.1)
> Trying to uninstall a non-existant service uses a pop box
> ---------------------------------------------------------
>
> Key: DAEMON-143
> URL: https://issues.apache.org/jira/browse/DAEMON-143
> Project: Commons Daemon
> Issue Type: Bug
> Components: Procrun
> Affects Versions: 1.0.2
> Environment: Don't know which version Tomcat 6.0.18 (see #DAEMON-142
> )
> Reporter: David Newcomb
> Assignee: Mladen Turk
> Priority: Minor
> Fix For: 1.0.2
>
>
> service install Tomcat
> --> The service 'Tomcat' has been installed.
> service install Tomcat
> --> Failed installing 'Tomcat' service
> service remove Tomcat
> --> The service 'Tomcat' has been removed
> service remove Tomcat
> --> The service 'Tomcat' has been removed there is also a pop-up dialogue
> showing "The specified service does not exists as an installed service.
> Unable to delete Tomcat service"
> In the first case the failure is met with an error message, whereas in the
> second case the failure is met with an error message and a pop-up.
> This has made it impossible to use tomcat6.exe to add Tomcat as a service
> from within an installer.
> The problem is that there is nothing to tell you if it is already installed
> as a service. Installing fails if it already exists, updating fails if it
> doesn't exist and deleting gives you a horrible pop up message from deep
> inside your installer. So there are 2 options. 1) delete serviced, add
> service and put put with the fact that the first time you are going to get
> the pop up or 2) have another entry in the registry (or marker somewhere)
> that tells you what state you are in.
> Can we change it so that Update does an install if the service doesn't exist.
> Otherwise what can I do.
> My bug has begun to sound like a support question, but I do think there is a
> real change to be made. I'm also unclear as to whether this issue should be
> reported against Tomcat or procrun so please forgive me if it's in the wrong
> place.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
