PDA

View Full Version : Cannot connect to the slimserver



Phil Thien
2004-12-31, 23:01
I upgraded to 5.4.0 this evening. Unfortunately, I don't remember the previous version I was using. It was installed about a year ago, and has worked flawlessly.

Anyway, since upgrading, I get the message "Cannot connect to the SlimServer. Is a server running at x.x.x.x?" messages from the SLIMP3 unit. If I go to my PC, I can see that the slimserver service has stopped. I can restart it, and the SLIMP3 starts to function again, but only for a little while (a few minutes to maybe half an hour). I upgraded to the latest (2.3, I think) firmware version, which hasn't helped.

What would be the best way to debug a problem like this? BTW, the slimserver is starting using the system account, there is no firewall on the machine on which it is running, I have scanned for viruses (none). I did install the 5.4.0 software "over the top" of the old version. I received no errors during installation. I have created a live365 account and provided my user name and password to slimserver. That was about the extent of the changes I made.

Thanks!
Phil Thien (phil (AT) cgallery (DOT) com)
Computer Gallery (http://www.cgallery.com)
414/963-6336 (extension 22)
414/963-6338 (fax)

kdf
2005-01-01, 00:09
Quoting Phil Thien <jpt (AT) cgallery (DOT) com>:

> I upgraded to 5.4.0 this evening. Unfortunately, I don't remember the
> previous version I was using. It was installed about a year ago, and has
> worked flawlessly.
>
> Anyway, since upgrading, I get the message "Cannot connect to the SlimServer.
> Is a server running at x.x.x.x?" messages from the SLIMP3 unit. If I go to
> my PC, I can see that the slimserver service has stopped. I can restart it,
> and the SLIMP3 starts to function again, but only for a little while (a few
> minutes to maybe half an hour). I upgraded to the latest (2.3, I think)
> firmware version, which hasn't helped.

When you experience a crash, look in the event viewer for some information.
start->settings->control panel
administration tools->event viewer.

if the service is crashing or stopping, it should have a message there. if not,
then you can try opening a dos window:
start->programs->accessories->command prompt.

type:
c:\program files\slimserver\server\slim.exe --d_server

then the server will start in the dos box, and you will see the progress of the
server starting up, and any messages as it shuts down.

-kdf

Phil Thien
2005-01-01, 21:32
Thank you for your help.

Got about eight of the "line 176" errors (below), and one of the "line 187"
errors (also below).

Now, when I turn off the RSS News Ticker, the problem of the errors/exiting
server goes away. After figuring this out I searched the archive and found
a message from another user that said when he removed Yahoo from the RSS
listing that his problem cleared-up. So I removed Yahoo but the problem
seems to remain, although I only tried it once after removing Yahoo and I
didn't reboot the PC or anything.

I've also noticed that when using the Live365 radio stations, I get a rather
loud pop when switching Live365 radio stations. I have the SLIMP3 directly
driving a Carver 200-WPC amp (no preamp, I use the volume control built into
the SLIMP3). So I'd like to keep the loud transient spikes to a minimum,
they aren't good for my fillings. :-).

The pop doesn't seem to happen with non-Live365 radio stations, but this is
the first time I've done any radio on the SLIMP3, so my information is
early, incomplete, and maybe just wrong. I need to experiment more.

Thanks,
Phil


Got about seven or eight of these:
***
Event Type: Error
Event Source: Application
Event Category: None
Event ID: 0
Date: 1/1/2005
Time: 8:42:01 AM
User: N/A
Computer: BASEMENT
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: Wide
character in send at /PerlApp/Slim/Player/SLIMP3.pm line 176.
***

And just one of these:
***
Event Type: Error
Event Source: Application
Event Category: None
Event ID: 0
Date: 12/31/2004
Time: 11:35:34 PM
User: N/A
Computer: BASEMENT
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:
syntax error at line 1, column 61, byte 61 at /PerlApp/XML/Parser.pm
line 187
***




----- Original Message -----
From: "kdf" <slim-mail (AT) deane-freeman (DOT) com>
To: "Slim Devices Discussion" <discuss (AT) lists (DOT) slimdevices.com>
Sent: Saturday, January 01, 2005 1:09 AM
Subject: [slim] Cannot connect to the slimserver


> Quoting Phil Thien <jpt (AT) cgallery (DOT) com>:
>
>> I upgraded to 5.4.0 this evening. Unfortunately, I don't remember the
>> previous version I was using. It was installed about a year ago, and has
>> worked flawlessly.
>>
>> Anyway, since upgrading, I get the message "Cannot connect to the
>> SlimServer.
>> Is a server running at x.x.x.x?" messages from the SLIMP3 unit. If I go
>> to
>> my PC, I can see that the slimserver service has stopped. I can restart
>> it,
>> and the SLIMP3 starts to function again, but only for a little while (a
>> few
>> minutes to maybe half an hour). I upgraded to the latest (2.3, I think)
>> firmware version, which hasn't helped.
>
> When you experience a crash, look in the event viewer for some
> information.
> start->settings->control panel
> administration tools->event viewer.
>
> if the service is crashing or stopping, it should have a message there.
> if not,
> then you can try opening a dos window:
> start->programs->accessories->command prompt.
>
> type:
> c:\program files\slimserver\server\slim.exe --d_server
>
> then the server will start in the dos box, and you will see the progress
> of the
> server starting up, and any messages as it shuts down.
>
> -kdf
>
>
>