Bugzilla – Bug 2011
6.2.1 2005-08-23 could not connect to SB2, and caused player to freeze.
Last modified: 2005-08-30 08:49:47 UTC
After the 6.2.1 2005-08-23 nightly was installed, Slimserver could not connect to the player. The player was not detected by Slimserver, and the player itself froze up, requiring a hard resets in order to respond to remote commands...Several reinstalls were attempted, and I even tried starting Slimserver from slimserver.pl. No change, no improvement. Reinstalling 6.1.2 immediately fixed the problem. y. Windows XP MCE 2005 Wireless SB2 (G only network) Linksys router (WRT54G latest firmware) Microsoft wireless USB card (on Slimserver PC)
A couple things to try: 1. See if you can connect via the web interface. (This will tell us if the server is running and not locked up.) 2. Press and hold the LEFT button on the remote to see if you can go back to setup (this indicates that the player firmware is locked up or if it's just the server.) 3. Check the Task Manager and see if Slim.exe is using an inordinate amount of memory or CPU cycles. 4. Stop the server and move aside your prefs file and your db file. Restart the server. If it comes up, we'd love to see those files.
the error mesage posted to the forum about this seems to indicate a db upgrade problem: Event Type: Error Event Source: Application Event Category: None Event ID: 0 Date: 8/23/2005 Time: 6:07:01 PM User: N/A Computer: MEDIA_CENTER Description: 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: DBD::SQLite::db prepare_cached failed: no such column: remote(1) at dbdimp.c line 268 at /PerlApp/Ima/DBI.pm line 391, <DATA> line 1.
Okay... Here's what I did. I copied slimserver.pref, slimserversql.db, and slimserver-convert.conf to my desktop. Then deleted most of the files in my slimserver directory except for a few related to Alien BBC. Next I installed a steaming fresh copy of the 8.24.05 6.2b1 exe, and installed it over my old install. Setup appeared to run correctly... so I clicked on the slimtray icon to start up the web ui. Long pause.... longer pause... 5 minutes later still nothing. Right clicking on the slimtray icon shows "starting slimserver" still greyed out. Task manager only shows slimtray...=no= slim.exe. The Event viewer shows the following new error: Event Type: Error Event Source: Application Event Category: None Event ID: 0 Date: 8/24/2005 Time: 9:24:06 PM User: N/A Computer: MEDIA_CENTER Description: 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: CreateService failed: The specified service already exists . So... No connection through Web UI. Check. The player is blank. LEFT button brings me back to setup. No freeze.... yet. RIGHT brings "attempting to connect", then a blank screen again. Task manager still shows no instance of Slim.exe. Next I stopped slimtray.exe via the Task Manager, and attempted to start slim.exe directly from it's location in .../slimserver/server. Command line DOS prompt window appears, but remains blank. No text. No nuthin. Slim.exe now appears in Task Manager and appears to be consuming around 50% of my CPU cycles (which is pretty high for my Intel 2.4Ghz HT chip). Mem usage stabalizes around 33,760k. Eventually, Slimtray vanishes from the taskbar... where it had appeared when Slim.exe was activated. The DOS prompt window remains open. No new errors have been logged in the event viewer at this point. Clicking on Slim.exe again brings up another DOS prompt window briefly, and the CPU usage spikes to over 80% for a few seconds before the new DOS window automatically closes. Again, no new errors logged in event viewer. I close the DOS window and noticed that slim.exe no longer shows in task manager.Next I tried to start Slimserver via slimserver.pl. ActivePerl Command prompt window pops up.... and remains blank. No new error logged in the EventViewer, no instance of Slim.exe in Task Manager... only perl.exe consuming 0 CPU cycles. Player still responds to remote. No player freeze this time... and diffrent errors.
Okay... Here's what I did. I copied slimserver.pref, slimserversql.db, and slimserver-convert.conf to my desktop. Then deleted most of the files in my slimserver directory except for a few related to Alien BBC. Next I installed a steaming fresh copy of the 8.24.05 6.2b1 exe, and installed it over my old install. Setup appeared to run correctly... so I clicked on the slimtray icon to start up the web ui. Long pause.... longer pause... 5 minutes later still nothing. Right clicking on the slimtray icon shows "starting slimserver" still greyed out. Task manager only shows slimtray...=no= slim.exe. The Event viewer shows the following new error: Event Type: Error Event Source: Application Event Category: None Event ID: 0 Date: 8/24/2005 Time: 9:24:06 PM User: N/A Computer: MEDIA_CENTER Description: 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: CreateService failed: The specified service already exists . So... No connection through Web UI. Check. The player is blank. LEFT button brings me back to setup. No freeze.... yet. RIGHT brings "attempting to connect", then a blank screen again. Task manager still shows no instance of Slim.exe. Next I stopped slimtray.exe via the Task Manager, and attempted to start slim.exe directly from it's location in .../slimserver/server. Command line DOS prompt window appears, but remains blank. No text. No nuthin. Slim.exe now appears in Task Manager and appears to be consuming around 50% of my CPU cycles (which is pretty high for my Intel 2.4Ghz HT chip). Mem usage stabalizes around 33,760k. Eventually, Slimtray vanishes from the taskbar... where it had appeared when Slim.exe was activated. The DOS prompt window remains open. No new errors have been logged in the event viewer at this point. Clicking on Slim.exe again brings up another DOS prompt window briefly, and the CPU usage spikes to over 80% for a few seconds before the new DOS window automatically closes. Again, no new errors logged in event viewer. I close the DOS window and noticed that slim.exe no longer shows in task manager.Next I tried to start Slimserver via slimserver.pl. ActivePerl Command prompt window pops up.... and remains blank. No new error logged in the EventViewer, no instance of Slim.exe in Task Manager... only perl.exe consuming 0 CPU cycles. Player still responds to remote.
Created attachment 769 [details] Old slimserversql.db and slimserver.pref
Before heading to bed... I ran the install once again. Just for fun. But this time the default web UI showed up! And lo! The player was asking for a firmware update. A miracle! After the firmware upgrade... everything appears to work. So far so good. Note: My preferences have been reset to default. Copying my old pref file over the new, and stopping/restarting slimserver doesn't appear to make any difference.
6.2 changes the format of the prefs file. copying the old over the new will simply trigger the server to convert them again. It seems there is something in there that the server doesnt like, and you end up with defaults instead. If you find that the defaults are being reset more than jsut this first time, I have an open bug 2009 on this issue. A fix is in, but I'd be interested in knowing if there are cases that this fix might miss.
This bug is resolved as far as I'm concerned.