Bug 3349 - SlimServer service fails to start after upgrade
: SlimServer service fails to start after upgrade
Status: CLOSED FIXED
Product: Logitech Media Server
Classification: Unclassified
Component: Windows Service
: 6.2.2
: PC Windows XP
: P2 blocker with 1 vote (vote)
: ---
Assigned To: Chris Owens
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2006-04-30 06:05 UTC by zuluend
Modified: 2008-09-15 14:38 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 zuluend 2006-04-30 06:05:20 UTC
I upgraded from 6.2.1 to the GA release of 6.2.2 and am experiencing the following problem. After installation, the SlimServer service fails with the following errors in the event log:

The description for Event ID ( 0 ) in Source ( Application ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: Can't call method "PushSelf" on an undefined value at /PerlApp/Slim/Utils/Misc.pm line 132.

Attempting to manually start the service via the services control panel or the tray tool experience the same problem.

Obviously I cannot increase the logging level in the SlimServer to help diagnose as the service never starts.

I uninstalled 6.2.2 and installed the latest nightly (04/28) of 6.3.0. It also experienced the problem. Backing off to 6.2.1 solved the problem. SlimServer is once again functioning normally on the GA of 6.2.1.
Comment 1 KDF 2006-04-30 11:52:55 UTC
*** Bug 3347 has been marked as a duplicate of this bug. ***
Comment 2 KDF 2006-04-30 11:53:14 UTC
*** Bug 3348 has been marked as a duplicate of this bug. ***
Comment 3 KDF 2006-04-30 12:19:41 UTC
I can only guess that something is wrong here with Win32:API, and the process priority setting. there is no use of "PushSelf" in Slim::Utils::Misc that I can find.
Comment 4 zuluend 2006-05-01 16:46:45 UTC
(In reply to comment #3)
> I can only guess that something is wrong here with Win32:API, and the process
> priority setting. there is no use of "PushSelf" in Slim::Utils::Misc that I can
> find.

I have been watching the forums and there are quite a few postings for the 6.2.2 SlimServer not starting. They do not include the event log entries unfortunately.
Comment 5 KDF 2006-05-01 23:13:14 UTC
yes, I've read them too.  Please be patient.  This is a developers tool, and as such, developers like myself will be leaving notes to share ideas.  This is not always a direction for the user or any suggestion of a bad setup.  Bad setups are, in fact a support, issue and would be thus directed to support.  If you wish for a more one-on-one type of help with the problem, please do contact support@slimdevices.com and they will help you dig further to help diagnose the problem and can copy the results to this report.
Comment 6 KDF 2006-05-02 16:05:40 UTC
just noticed, target should be 6.3 since that is the next possible release.
Comment 7 Greg Dowling 2006-05-03 12:46:14 UTC
I have this one too.

Here is my event log:-

The description for Event ID ( 0 ) in Source ( Application ) cannot be found. The local computer may not have the necessary registry information or message DLL files to display messages from a remote computer. You may be able to use the /AUXSOURCE= flag to retrieve this description; see Help and Support for details. The following information is part of the event: Can't call method "PushSelf" on an undefined value at /PerlApp/Slim/Utils/Misc.pm line 132.
Comment 8 Dan Sully 2006-05-04 16:16:40 UTC
Fixed in change 7294 for the 6.3 branch - it will be in the 2006-05-05 nightly.
Comment 9 Chris Owens 2006-06-16 11:37:53 UTC
Verified fixed in SlimServer Version: 6.3.0 - 8002 - Windows XP - EN - cp1252
Comment 10 Chris Owens 2006-06-27 14:21:03 UTC
This bug fix is now part of a released version, and so has been marked closed. If you are still experiencing this problem, please reopen the bug.