Bug 9458 - SqueezeCenter 7.2 Windows service now fails to start on boot
: SqueezeCenter 7.2 Windows service now fails to start on boot
Status: CLOSED DUPLICATE of bug 8108
Product: Logitech Media Server
Classification: Unclassified
Component: Windows Service
: 7.2
: PC Windows XP
: -- major (vote)
: 7.x
Assigned To: James Richardson
:
Depends on: 8108
Blocks:
  Show dependency treegraph
 
Reported: 2008-09-10 13:15 UTC by Ross Duckworth
Modified: 2012-02-27 17:18 UTC (History)
2 users (show)

See Also:
Category: ---


Attachments
Startup log (596 bytes, application/octet-stream)
2008-09-11 01:55 UTC, Ross Duckworth
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Ross Duckworth 2008-09-10 13:15:51 UTC
History:
The same machine (Win XP SP3) has been running SqueezeCenter since version 5. The service has always started successfully on boot first time.

Problem:
Upgraded to SqueezeCenter 7.2 on 9/9/2008. SqueezeCenter no longer starts properly on boot. It stays in the tray with its status marked as 'Starting SqueezeCenter...' for ever. Squeezebox devices cannot connect.

Workaround:
Exiting SqueezeCenter via the system tray icon then restarting it works. This occurs each and every time. No other software or windows updates were installed just prior or after upgrading to SqueezeCenter 7.2.
Comment 1 Chris Owens 2008-09-10 16:39:24 UTC
Ross, if you could, try starting squeezecenter.exe from the command line and see if anything interesting comes up in the text.
Comment 2 Ross Duckworth 2008-09-11 01:55:40 UTC
Created attachment 3971 [details]
Startup log

This is what was logged during startup. Manual startup actually works. However, there were at least 2 attempts where SqueezeCenter.exe failed to start completely, and produce the following error (running again immediately after worked):

Can't create 'C:\DOCUME~1\Ross\LOCALS~1\Temp\pdk-Ross/auto/Win32/Win32.dll': Per
mission denied at perlsvc line 686.
BEGIN failed--compilation aborted at /<C:\Program Files\SqueezeCenter\server\squ
eezecenter.exe>FindBin.pm line 201.
BEGIN failed--compilation aborted at /<C:\Program Files\SqueezeCenter\server\squ
eezecenter.exe>FindBin.pm line 201.
BEGIN failed--compilation aborted at slimserver.pl line 105.
Undefined subroutine &main::main called at slimserver.pl line 90.
Comment 3 James Richardson 2008-09-16 12:13:47 UTC
Michael: Can you comment on the attached log?
Comment 4 Michael Herger 2008-09-16 14:10:33 UTC
The log doesn't contain anything interesting. We'd need more lines.

If SC is configured to run as a service you wouldn't even have the option to start it from the tray icon. Did the service enabler succeed? Did you use a user/password or did you try anonymous service? Maybe it failed due to some wrong PW or something. Unless you try to access a network share or iTunes start running the service anonymously. Or just do this as a first try, adding login/password once it's running in anonymous mode.

The permissions issue in your comment sound like there's probably a AV scanner over protective. What about write permissions on that folder? Or disk full?

And please remove all 3rd party plugins until SC is able to be run. Once this is ok, you can add them back. I just want to be sure we're not seeing some oddness due to some plugin.
Comment 5 James Richardson 2008-09-16 15:54:47 UTC
Ross:  are you using Windows XP - HOME or PRO or MCE?

Do you have a Password set for the system login account?

Does the account you are associating with the service have Admin or Limited privileges?
Comment 6 Ross Duckworth 2008-09-17 00:16:54 UTC
Hi.
I am not actually running it as a Windows Service, it is being run in user mode, starting when I log in. I will change it to service mode and see if that makes any difference. 
Comment 7 James Richardson 2008-09-18 08:59:21 UTC
Ross:

Try deleting your Cache folder.  Let me know if that allows SC to "auto" start on a windows reboot.
Comment 8 Ross Duckworth 2008-09-20 13:54:30 UTC
I have full uninstalled, then re-installed SqueezeCenter 7.2. Still set to run in user mode, not as a service. So far, two days in a row, it has started successfully.
Comment 9 James Richardson 2008-09-20 15:36:26 UTC

*** This bug has been marked as a duplicate of bug 8108 ***
Comment 10 Michael Herger 2008-09-22 12:22:36 UTC
While I'm glad the issue is gone, I don't understand why this should be a dupe of 8108. James - did you accidentally close the wrong bug?
Comment 11 James Richardson 2008-09-22 12:51:59 UTC
IMHO, this appeared to be the same issue as 8108.  I.E. corrupted cache
Comment 12 Chris Owens 2009-07-31 10:29:46 UTC
Reduce number of active targets for SC
Comment 13 James Richardson 2012-02-27 17:18:53 UTC
Closing resolved bugs - if you feel this bug still exists please first re-test with the latest SW/FW version.  If you are able to reproduce then feel free to reopen and attach new logs / steps to reproduce.