Bugzilla – Bug 15581
"Start as service" UI on Windows control panel doesn't work any more when user/password is entered
Last modified: 2010-03-22 06:49:21 UTC
Using the Squeezebox Server Control panel, it is not possible to persist changes to the startup options. I have tried to start the server at system startup and at login. Neither of these changes work. Steps to reproduce. 1. Stop Server if running. Startup options are not available if running. 2. Change "Startup Options" to "Automatically run at system start" click apply 1. Stop Server if running. Startup options are not available if running. 2. Change "Startup Options" to "Automatically run at login" click apply In both cases, starting the server again reset these options. Clicking the icon in the system tray and setting the option to start at login also has no effect.
working fine here. We need some more information about your system: what Windows version (Home, Ultimate etc.)? Is your user member of the admin group? Have you been asked to enter an admin's password? QA to reproduce. Thanks!
(In reply to comment #1) > working fine here. We need some more information about your system: what > Windows version (Home, Ultimate etc.)? Is your user member of the admin group? > Have you been asked to enter an admin's password? > > QA to reproduce. Thanks! OS is Windows Home Premium 64bit My user is in the admin group. If I set it to start at boot, it does ask for a userId and password. It does not seem to matter what userId/password I give it since it doesn't seem to store that information anywhere. By this I mean that if I close the Squeezebox control panel and reopen, the settings have reverted to not start at all. Clicking Apply doesn't seem to do anything, but it takes a couple of seconds before it will then respond to the OK and close the window. Squeezebox Server Version 7.4.1 / r28947
> If I set it to start at boot, it does ask for a userId and password. I'm sorry, I wasn't precise enough: is _Windows_ asking you for permission to change those values? I'm not asking about the username/password you can enter in the SB Control Panel, but Windows' user elevation or UAC (User Account Control).
(In reply to comment #3) > > If I set it to start at boot, it does ask for a userId and password. > > I'm sorry, I wasn't precise enough: is _Windows_ asking you for permission to > change those values? I'm not asking about the username/password you can enter > in the SB Control Panel, but Windows' user elevation or UAC (User Account > Control). No, Windows is not asking for permission. No UAC windows at all.
*** Bug 15588 has been marked as a duplicate of this bug. ***
I was able to work around this bug by uninstalling Squeezebox Server, deleting the sub-directory where it had been installed and reinstalling.
I have the same problem exactly. Installed with Vista x86 and settings would not stick. Installed Windows 7 x64 on that PC and still setting to start on boot doesn't stick. I see an SqueezeMySQL service that is running but no other Squeezebox NT services. Shouldn't there be a service for Squeezebox server itself?
I have exactly the same problem and have had on 2 separate WHS systems. One a home build and now on a new HP EX495. It doesn't matter if I check the box under settings on the WHS console or set the service itself to automatic within the OS, within a couple of days it had been reset again. This has been a bug for quite a few months. WHS version 3.0.14.33083 Squeezebox Server 7.4.1 r28947 Kaiserdog
Ok, I solved my problem by leaving the username and password blank. I created a Windows service account and used that username and password thinking that's what was needed; but it's not. Why have a spot for the username and password if entering that information breaks the functionality. You might want to consider putting in a note on that page "leave blank for most installations".
Thanks for the feedback. That make sense: unless your user is allowed to run as a service (which might be even more restrictive on W7 than XP) you won't be able to run SBS as a service using that user. I'll try to figure out some UI improvement for this. We've had quite a bit of negative user feedback about the confusing user/password fields.
Moving P3 and lower bugs to next release target
I have the same problem on an HP EX490 MediaSmart running Windows Home Server. HP version: 3.2.1.34990 Squeezebox Server: 7.4.2 - r30215 To reiterate: I select the "Start Squeezebox server when system boots" box in the WHS settings GUI and save the settings. Then later after a reboot the box will be unset and the Squeezebox server will not have started. Given this is meant to be an unattended server it's a really annoyance that this happens!
Please open a new bug for the WHS issue. While it looks the same from the user's perspective, it must be something completely different. This issue here is about the user input field failing the service to register. In the WHS there's no such user input field afair.
...and I can confirm that the service creation can fail under certain circumstances when a username/password is given. Those of you who encounter this issue could you please try to install the service manually from the command line: - open a command line - change to the SBS installer folder (where you'd find SqueezeSvr.exe) - run the following command with your username and password: SqueezeSvr.exe --install --username=xyz --password=abc - open the Windows service manager and try to start SBS. Does it succeed?
Created attachment 6680 [details] add "grant" command to service registration In order to log on as a service, a user needs specific permissions. By default this isn't given. We therefore have to make sure the user is granted this right.
== Auto-comment from SVN commit #30399 to the slim repo by mherger == == https://svn.slimdevices.com/slim?view=revision&revision=30399 == Fixed Bug: 15581 Description: In order to log on as a service, a user needs specific permissions. By default this isn't given. We therefore have to make sure the user is granted this right.