Bug 12812 - Control Panel reinstalls Windows service for no reason
: Control Panel reinstalls Windows service for no reason
Status: CLOSED FIXED
Product: Logitech Media Server
Classification: Unclassified
Component: Windows Control Panel
: 7.4.0
: PC Windows Server 2003
: P2 normal (vote)
: 7.4.0
Assigned To: Michael Herger
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2009-07-11 23:11 UTC by Jim McAtee
Modified: 2009-10-05 14:30 UTC (History)
1 user (show)

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Jim McAtee 2009-07-11 23:11:53 UTC
I've modified the startup command (changing IP addresses using command line parameters) for the Windows service that was installed by the CP.  When you go back into the CP with the service in a stopped state and you start the server, it reinstalls the service and wipes out any modifications made to the registry.  There should be no reason to reinstall the service again.
Comment 1 Michael Herger 2009-07-30 01:17:34 UTC
I'm sorry to say that I'm not sure we can support customized command lines from the control panel.
Comment 2 Michael Herger 2009-07-30 01:18:33 UTC
Oh wait... it shouldn't change it unless you change the startup mode. That would be a bug to be fixed.
Comment 3 Michael Herger 2009-07-30 04:30:58 UTC
Jim - can you reproduce this issue? The service should only be re-registered if you change either of username, password or startup mode. But never if you just want to restart it or similar.
Comment 4 Jim McAtee 2009-07-30 10:00:28 UTC
I just installed the latest nightly (using the option to install the update from SqueezeTray), then stopped the server using the Control Panel.  I then changed the HKLM\SYSTEM\CurrentControlSet\Services\squeezesvc registry settings, changing ImagePath, Description, DisplayName, and adding FailureActions from the Services applet.  I then started the service from the Control Panel, and the entire registry hive was wiped out and reset.  No changes were made in the Control Panel.  The Startup Options were left at 'Automatically run at system start', with blank Username and Password.

Could it be the blank username and password?  I recall at one point in the initial setup that either the installer (or maybe the Control Panel) insisted on a username and password.  I entered one, but I don't think it was ever placed in the registry, as when I went to change it using the Services applet, it was running under the Local System account.
Comment 5 Michael Herger 2009-07-30 10:26:44 UTC
would you mind posting your registry key for the service registration?
Comment 6 Michael Herger 2009-07-31 08:28:13 UTC
Ok, found it. It does indeed register the services before starting SC. Will have to investigate why I did this. No need for the registry export.
Comment 7 Michael Herger 2009-07-31 08:59:31 UTC
change 27960 - starting SC would re-initialise startup mode, under some circumstances even incorrectly. Only init if needed (mode, user or password changed) and use the correct change handler.

Could you please give this another try? Thanks!
Comment 8 Michael Herger 2009-08-03 06:57:27 UTC
Jim - please re-open this bug if you still see this issue.
Comment 9 James Richardson 2009-10-05 14:30:38 UTC
This bug has been marked as fixed in the 7.4.0 release version of SqueezeBox Server!
    * SqueezeCenter: 28672
    * Squeezebox 2 and 3: 130
    * Transporter: 80
    * Receiver: 65
    * Boom: 50
    * Controller: 7790
    * Radio: 7790  

Please see the Release Notes for all the details: http://wiki.slimdevices.com/index.php/Release_Notes

If you haven't already, please download and install the new version from http://www.logitechsqueezebox.com/support/download-squeezebox-server.html

If you are still experiencing this problem, feel free to reopen the bug with your new comments and we'll have another look.