PDA

View Full Version : Last, Best Hope for getting SlimServer to work??



Shep
2007-06-05, 17:59
1st post here but been successfully using SB2&3 / SS for nearly 2 years. Here from despair at SlimServer crashing on 2 computers and inablility to get it working after over 2 months of troubleshooting and working with Slim Support group (email & telephone). Summary of failure follows:
*No problem w/SlimServer until downloading ver.6.5.1 end of March.
*Shortly after downloading new version, unable to connect to SS (no localhost 9000)
*Downloaded SS to another PC (laptop) & it failed in the same manner (could not connect via localhost 9000)
*Searched these forums for localhost 9000 problems and tried fixes; no luck.
*PCs use different virus protection & Windows firewall
*Tried with & w/o virus protection & firewall; no change
*Desktop has Windows Media Center; Lap Windows XP w/SP2 (all current updates)
*De-installed & re-installed more times than I can count& gone back to SS ver 3._ and none work.
*Networked w/Linksys router(wired) & broadband Internet (Comcast)

All that to say I'm out of ideas and on the verge of abandoning my Squeezeboxes unless I can get help here. Any ideas or suggestions most appreciated....Please!!

mswlogo
2007-06-05, 19:00
Have you considered reinstalling XP?

You might get away with a repair install. You won't lose any data but you will have to reinstall applications.

My guess is it's remnants of the Anti Virus Programs you had installed. Sometimes they are very hard to remove because they need to protect themselves from virus programs. You may think you removed it or disabled it but you may not have.

I'm sure it's solvable but sometimes it's easier to just reinstall. You server shouldn't have much junk on it anyway.

Windows Firewall is ok and when I install AntiVirus I always leave out the additional firewall, spyware, IE plugins, mail watch. Just the core virus protection is all I want. New virus programs are a bit out of control.

Good luck

JJZolx
2007-06-05, 19:02
Do you know whether the server is actually running?

erland
2007-06-05, 22:02
All that to say I'm out of ideas and on the verge of abandoning my Squeezeboxes unless I can get help here. Any ideas or suggestions most appreciated....Please!!
Could you try to:
1. Open up a Command Prompt window
2. Goto the "server" directory below the SlimServer installation directory, for example: cd "C:\Program Files\SlimServer\server"
3. Run: Slim.exe --d_startup

If you are returned to the command prompt, post the log from the Command Prompt window here.

tyler_durden
2007-06-06, 00:06
If you don't do any web surfing via the server computer, after reinstalling windoze, disable automatic updates. All you need is for it to run- you don't need all the updates. I can't count the number of problems that stopped happening after I disabled auto updates in my win2k machine. M$ OSes are just riddled with holes and they produce so many band-aids for them I doubt anyone at M$ knows what is going on any more.

Switch to linux - ubuntu has easy install and slimserver works.

TD

oreillymj
2007-06-06, 00:27
Have you looked in the Windows event log for Slimserver related errors?

Did you empty or rename your plugin directory before doing an upgrade? If you upgraded from 3.x to 6.5.x, then I suspect that any plugin's you had installed will no longer work.

You don't mention what browser your using.
You also don't mention what error (if any) you're getting. Can't open localhost:9000 doesn't give anyone enough information to make informed suggestions.

Supply as much information as possible, no matter how irrelevant it my seem.

mherger
2007-06-06, 03:01
> *No problem w/SlimServer until downloading ver.6.5.1 end of March.
> *Shortly after downloading new version, unable to connect to SS (no
> localhost 9000)

Is there something running on port 9000? Do a "netstat -an" in a DOS
window. Do you see something on port 9000?

Shut down SlimServer and do the same test again. Is the port still open?

> *Desktop has Windows Media Center; Lap Windows XP w/SP2 (all current
> updates)

I think one of the Media Player extensions is using port 9000, too. If the
above test is positive, I fear there's a port conflict. But then you've
had it running in an earlier version?

--

Michael

-----------------------------------------------------------------
http://www.herger.net/SlimCD - your SlimServer on a CD
http://www.herger.net/slim - AlbumReview, Biography, MusicInfoSCR

Shep
2007-06-06, 08:37
Could you try to:
1. Open up a Command Prompt window
2. Goto the "server" directory below the SlimServer installation directory, for example: cd "C:\Program Files\SlimServer\server"
3. Run: Slim.exe --d_startup

If you are returned to the command prompt, post the log from the Command Prompt window here.

You should know before I get in too deep, I'm no PC guru!! Guess this will serve as a test of how to post within a reply...Here's what I get back. I confirmed SS was stopped prior to running the command (but it's been stopped for over 2 months :(

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Owner>cd "C:\Program Files\SlimServer\server"

C:\Program Files\SlimServer\server>Slim.exe --d_startup
Got @INC containing:
C:/Program Files/SlimServer/server
C:\Program Files\SlimServer\server

Extended @INC to contain:
C:\Program Files\SlimServer\server\CPAN\arch\5.8\MSWin32-x86-multi-thread
C:\Program Files\SlimServer\server\CPAN\arch\5.8\MSWin32-x86-multi-thread\auto
C:\Program Files\SlimServer\server\CPAN\arch\5.8.8\MSWin32-x86-multi-thread
C:\Program Files\SlimServer\server\CPAN\arch\5.8.8\MSWin32-x86-multi-thread\auto

C:\Program Files\SlimServer\server\CPAN\arch\5.8\MSWin32-x86-multi-thread
C:\Program Files\SlimServer\server\CPAN\arch\5.8\MSWin32-x86-multi-thread\auto
C:\Program Files\SlimServer\server\CPAN\arch\MSWin32-x86-multi-thread
C:\Program Files\SlimServer\server\lib
C:\Program Files\SlimServer\server\CPAN
C:/Program Files/SlimServer/server
C:/Program Files/SlimServer/server
C:\Program Files\SlimServer\server

Loaded module: [Time::HiRes] ok!
Loaded module: [DBD::mysql] ok!
Loaded module: [DBI] ok!
Loaded module: [XML::Parser::Expat] ok!
Loaded module: [HTML::Parser] ok!
Loaded module: [Compress::Zlib] ok!
Loaded module: [Digest::SHA1] ok!
Loaded module: [YAML::Syck] ok!
Loaded module: [GD] ok!
Loaded module: [Locale::Hebrew] ok!
The following modules are loaded after the first attempt:
YAML/Syck.pm => /PerlApp/YAML/Syck.pm
IO/Handle.pm => /PerlApp/IO/Handle.pm
re.pm => /PerlApp/re.pm
HTML/Parser.pm => /PerlApp/HTML/Parser.pm
File/Spec/Functions.pm => /PerlApp/File/Spec/Functions.pm
List/Util.pm => /PerlApp/List/Util.pm
POSIX.pm => /PerlApp/POSIX.pm
SelectSaver.pm => /PerlApp/SelectSaver.pm
ActiveState/Path.pm => /PerlApp/ActiveState/Path.pm
Getopt/Long.pm => /PerlApp/Getopt/Long.pm
GD/Polygon.pm => /PerlApp/GD/Polygon.pm
Compress/Zlib.pm => /PerlApp/Compress/Zlib.pm
Locale/Hebrew.pm => /PerlApp/Locale/Hebrew.pm
DBD/mysql.pm => /PerlApp/DBD/mysql.pm
Cwd.pm => /PerlApp/Cwd.pm
warnings.pm => /PerlApp/warnings.pm
Slim/Utils/OSDetect.pm => /PerlApp/Slim/Utils/OSDetect.pm
B.pm => /PerlApp/B.pm
Digest/base.pm => /PerlApp/Digest/base.pm
Fcntl.pm => /PerlApp/Fcntl.pm
/PerlApp/auto/Compress/Zlib/autosplit.ix => /PerlApp/auto/Compress/Zlib/
autosplit.ix
Symbol.pm => /PerlApp/Symbol.pm
Scalar/Util.pm => /PerlApp/Scalar/Util.pm
Exporter.pm => /PerlApp/Exporter.pm
Win32.pm => /PerlApp/Win32.pm
File/Spec.pm => /PerlApp/File/Spec.pm
File/Spec/Win32.pm => /PerlApp/File/Spec/Win32.pm
FindBin.pm => /PerlApp/FindBin.pm
warnings/register.pm => /PerlApp/warnings/register.pm
XSLoader.pm => /PerlApp/XSLoader.pm
Slim/bootstrap.pm => /PerlApp/Slim/bootstrap.pm
Digest/SHA1.pm => /PerlApp/Digest/SHA1.pm
Time/HiRes.pm => /PerlApp/Time/HiRes.pm
IO/Seekable.pm => /PerlApp/IO/Seekable.pm
XML/Parser/Expat.pm => /PerlApp/XML/Parser/Expat.pm
B/Deparse.pm => /PerlApp/B/Deparse.pm
PerlApp/DATA.pm => /PerlApp/PerlApp/DATA.pm
DBI.pm => /PerlApp/DBI.pm
GD/Image.pm => /PerlApp/GD/Image.pm
Config.pm => /PerlApp/Config.pm
File/Basename.pm => /PerlApp/File/Basename.pm
/PerlApp/auto/POSIX/autosplit.ix => /PerlApp/auto/POSIX/autosplit.ix
ActivePerl/Config.pm => /PerlApp/ActivePerl/Config.pm
Win32/FileSecurity.pm => /PerlApp/Win32/FileSecurity.pm
IO.pm => /PerlApp/IO.pm
Carp.pm => /PerlApp/Carp.pm
FileHandle.pm => /PerlApp/FileHandle.pm
Exporter/Heavy.pm => /PerlApp/Exporter/Heavy.pm
File/Spec/Unix.pm => /PerlApp/File/Spec/Unix.pm
auto/POSIX/load_imports.al => /PerlApp/auto/POSIX/load_imports.al
vars.pm => /PerlApp/vars.pm
strict.pm => /PerlApp/strict.pm
constant.pm => /PerlApp/constant.pm
Config_heavy.pl => /PerlApp/Config_heavy.pl
IO/File.pm => /PerlApp/IO/File.pm
overload.pm => /PerlApp/overload.pm
AutoLoader.pm => /PerlApp/AutoLoader.pm
HTML/Entities.pm => /PerlApp/HTML/Entities.pm
lib.pm => /PerlApp/lib.pm
GD.pm => /PerlApp/GD.pm
DynaLoader.pm => /PerlApp/DynaLoader.pm

The following modules are loaded after the second attempt:
YAML/Syck.pm => /PerlApp/YAML/Syck.pm
IO/Handle.pm => /PerlApp/IO/Handle.pm
re.pm => /PerlApp/re.pm
HTML/Parser.pm => /PerlApp/HTML/Parser.pm
File/Spec/Functions.pm => /PerlApp/File/Spec/Functions.pm
List/Util.pm => /PerlApp/List/Util.pm
POSIX.pm => /PerlApp/POSIX.pm
SelectSaver.pm => /PerlApp/SelectSaver.pm
ActiveState/Path.pm => /PerlApp/ActiveState/Path.pm
Getopt/Long.pm => /PerlApp/Getopt/Long.pm
GD/Polygon.pm => /PerlApp/GD/Polygon.pm
Compress/Zlib.pm => /PerlApp/Compress/Zlib.pm
Locale/Hebrew.pm => /PerlApp/Locale/Hebrew.pm
DBD/mysql.pm => /PerlApp/DBD/mysql.pm
Cwd.pm => /PerlApp/Cwd.pm
warnings.pm => /PerlApp/warnings.pm
Slim/Utils/OSDetect.pm => /PerlApp/Slim/Utils/OSDetect.pm
B.pm => /PerlApp/B.pm
Digest/base.pm => /PerlApp/Digest/base.pm
Fcntl.pm => /PerlApp/Fcntl.pm
/PerlApp/auto/Compress/Zlib/autosplit.ix => /PerlApp/auto/Compress/Zlib/
autosplit.ix
Symbol.pm => /PerlApp/Symbol.pm
Scalar/Util.pm => /PerlApp/Scalar/Util.pm
Exporter.pm => /PerlApp/Exporter.pm
Win32.pm => /PerlApp/Win32.pm
File/Spec.pm => /PerlApp/File/Spec.pm
File/Spec/Win32.pm => /PerlApp/File/Spec/Win32.pm
FindBin.pm => /PerlApp/FindBin.pm
warnings/register.pm => /PerlApp/warnings/register.pm
XSLoader.pm => /PerlApp/XSLoader.pm
Slim/bootstrap.pm => /PerlApp/Slim/bootstrap.pm
Digest/SHA1.pm => /PerlApp/Digest/SHA1.pm
Time/HiRes.pm => /PerlApp/Time/HiRes.pm
IO/Seekable.pm => /PerlApp/IO/Seekable.pm
XML/Parser/Expat.pm => /PerlApp/XML/Parser/Expat.pm
B/Deparse.pm => /PerlApp/B/Deparse.pm
PerlApp/DATA.pm => /PerlApp/PerlApp/DATA.pm
DBI.pm => /PerlApp/DBI.pm
GD/Image.pm => /PerlApp/GD/Image.pm
Config.pm => /PerlApp/Config.pm
File/Basename.pm => /PerlApp/File/Basename.pm
/PerlApp/auto/POSIX/autosplit.ix => /PerlApp/auto/POSIX/autosplit.ix
ActivePerl/Config.pm => /PerlApp/ActivePerl/Config.pm
Win32/FileSecurity.pm => /PerlApp/Win32/FileSecurity.pm
IO.pm => /PerlApp/IO.pm
Carp.pm => /PerlApp/Carp.pm
FileHandle.pm => /PerlApp/FileHandle.pm
Exporter/Heavy.pm => /PerlApp/Exporter/Heavy.pm
File/Spec/Unix.pm => /PerlApp/File/Spec/Unix.pm
auto/POSIX/load_imports.al => /PerlApp/auto/POSIX/load_imports.al
vars.pm => /PerlApp/vars.pm
strict.pm => /PerlApp/strict.pm
constant.pm => /PerlApp/constant.pm
Config_heavy.pl => /PerlApp/Config_heavy.pl
IO/File.pm => /PerlApp/IO/File.pm
overload.pm => /PerlApp/overload.pm
AutoLoader.pm => /PerlApp/AutoLoader.pm
HTML/Entities.pm => /PerlApp/HTML/Entities.pm
lib.pm => /PerlApp/lib.pm
GD.pm => /PerlApp/GD.pm
DynaLoader.pm => /PerlApp/DynaLoader.pm

Loaded module: [Slim::Utils::PerlRunTime] ok!
2007-06-06 11:31:22.3682 ERROR: There is already another copy of the SlimServer
running on this machine. (Unknown error)


C:\Program Files\SlimServer\server>

Shep
2007-06-06, 08:42
Have you considered reinstalling XP?

You might get away with a repair install. You won't lose any data but you will have to reinstall applications.

My guess is it's remnants of the Anti Virus Programs you had installed. Sometimes they are very hard to remove because they need to protect themselves from virus programs. You may think you removed it or disabled it but you may not have.

I'm sure it's solvable but sometimes it's easier to just reinstall. You server shouldn't have much junk on it anyway.

Windows Firewall is ok and when I install AntiVirus I always leave out the additional firewall, spyware, IE plugins, mail watch. Just the core virus protection is all I want. New virus programs are a bit out of control.

Good luck

Thanks for the reply. I research how to reinstall XP as a last resort if it comes to that. I'd like to get SS to work on this laptop & it would be pretty much dedicated to SS / SB activity along with the external hard drive with all my music.
Thanks again.

Shep
2007-06-06, 08:47
Do you know whether the server is actually running?

Hey Jim,
My PC chops aren't all that strong so not sure what you mean by "server is actually running". I have a wired home network with 3 PCs but not a 'server' per se. Does that make any sense?

Shep
2007-06-06, 08:51
If you don't do any web surfing via the server computer, after reinstalling windoze, disable automatic updates. All you need is for it to run- you don't need all the updates. I can't count the number of problems that stopped happening after I disabled auto updates in my win2k machine. M$ OSes are just riddled with holes and they produce so many band-aids for them I doubt anyone at M$ knows what is going on any more.

Switch to linux - ubuntu has easy install and slimserver works.

TD

Thanks TD,
Did some research last nite about Linux and what would be easiest to use with SlimServer...will check out ubuntu. This might be an option if I can't get it to work w/XP.

Thanks for the suggestion.

snarlydwarf
2007-06-06, 08:52
Loaded module: [Slim::Utils::PerlRunTime] ok!
2007-06-06 11:31:22.3682 ERROR: There is already another copy of the SlimServer
running on this machine. (Unknown error)



Most likely that means that Windows Media Player has stolen port 9000, which SlimServer wants.

I don't do Windows, so no clue how to make WMP stop doing that.

mherger
2007-06-06, 08:55
> Loaded module: [Slim::Utils::PerlRunTime] ok!
> 2007-06-06 11:31:22.3682 ERROR: There is already another copy of the
> SlimServer
> running on this machine. (Unknown error)

This means there's already something running and listening on port 9000
(see my other mail regarding netstat). Make sure you've shut down
SlimServer before you run the above test.

--

Michael

-----------------------------------------------------------------
http://www.herger.net/SlimCD - your SlimServer on a CD
http://www.herger.net/slim - AlbumReview, Biography, MusicInfoSCR

Shep
2007-06-06, 09:00
Have you looked in the Windows event log for Slimserver related errors?

I sent the Windows to Slim Support and they indicated there were no anomilies with it. I'm not versed in what the event log means so it's Greek to me.

Did you empty or rename your plugin directory before doing an upgrade? If you upgraded from 3.x to 6.5.x, then I suspect that any plugin's you had installed will no longer work.

I've never used plugins with SS, so nothing going on there

You don't mention what browser your using.
You also don't mention what error (if any) you're getting. Can't open localhost:9000 doesn't give anyone enough information to make informed suggestions.

Generally, I use Firefox but have tried IE to see if that was an issue. Same results with either browser. IE is currently installed on the laptop and Firefox on the desktop.

Supply as much information as possible, no matter how irrelevant it my seem.

Please see reply to 'erland' for results of 'Slim.exe --d_startup' command at c prompt. I'm willing to execute any other suggestions that would yield useful info.
Thanks.

JJZolx
2007-06-06, 09:13
Ok, from the error we know that either slim.exe is already running or another process is listening on port 9000.

Open Windows Task Manager. I believe this should work on all versions of XP:

Hit <Ctrl><Alt><Del> and in the dialogue box select 'Task Manager'. Go to the 'Processes' tab. Tick 'Show processes from all users'. Click on the 'Image Name' column header to sort by name. Look through the list for slim.exe. If it's showing, then SlimServer is currently running.

oreillymj
2007-06-06, 10:37
According to the Windows Media player help file, Windows Media sharing does not use port 9000.

The following table shows the firewall ports that must be opened if you want to share media to other devices.
Port
Protocol
Scope

1900
UDP
local subnet only

2869
TCP
local subnet only

10243
TCP
local subnet only

10280-10284
UDP
local subnet only


From the Windows Start Menu, goto Run

Type eventvwr, and look in the Application section of Event Viewer. Look through any errors listed for mention of Slimserver or Application errors.

Shep
2007-06-06, 10:42
Thanks Michael,

I'm sure it's a stupid question but what do you mean "make sure SS is shut down" since it won't start? Slim Tray says "stopped".

Here's the result...

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Owner>netstat -an

Active Connections

Proto Local Address Foreign Address State
TCP 0.0.0.0:135 0.0.0.0:0 LISTENING
TCP 0.0.0.0:445 0.0.0.0:0 LISTENING
TCP 0.0.0.0:641 0.0.0.0:0 LISTENING
TCP 0.0.0.0:2869 0.0.0.0:0 LISTENING
TCP 127.0.0.1:1035 0.0.0.0:0 LISTENING
TCP 127.0.0.1:10110 0.0.0.0:0 LISTENING
TCP 192.168.1.104:139 0.0.0.0:0 LISTENING
TCP [::]:135 [::]:0 LISTENING 0
TCP [::]:2869 [::]:0 LISTENING 0
UDP 0.0.0.0:445 *:*
UDP 0.0.0.0:1025 *:*
UDP 0.0.0.0:1070 *:*
UDP 0.0.0.0:1147 *:*
UDP 0.0.0.0:1222 *:*
UDP 127.0.0.1:123 *:*
UDP 127.0.0.1:1104 *:*
UDP 127.0.0.1:1457 *:*
UDP 127.0.0.1:1459 *:*
UDP 127.0.0.1:1676 *:*
UDP 127.0.0.1:1900 *:*
UDP 192.168.1.104:123 *:*
UDP 192.168.1.104:137 *:*
UDP 192.168.1.104:138 *:*
UDP 192.168.1.104:1900 *:*

C:\Documents and Settings\Owner>
> Loaded module: [Slim::Utils::PerlRunTime] ok!
> 2007-06-06 11:31:22.3682 ERROR: There is already another copy of the
> SlimServer
> running on this machine. (Unknown error)

This means there's already something running and listening on port 9000
(see my other mail regarding netstat). Make sure you've shut down
SlimServer before you run the above test.

--

Michael

-----------------------------------------------------------------
http://www.herger.net/SlimCD - your SlimServer on a CD
http://www.herger.net/slim - AlbumReview, Biography, MusicInfoSCR

Shep
2007-06-06, 10:49
> Loaded module: [Slim::Utils::PerlRunTime] ok!
> 2007-06-06 11:31:22.3682 ERROR: There is already another copy of the
> SlimServer
> running on this machine. (Unknown error)

This means there's already something running and listening on port 9000
(see my other mail regarding netstat). Make sure you've shut down
SlimServer before you run the above test.

--

Michael

-----------------------------------------------------------------
http://www.herger.net/SlimCD - your SlimServer on a CD
http://www.herger.net/slim - AlbumReview, Biography, MusicInfoSCR


Ok, from the error we know that either slim.exe is already running or another process is listening on port 9000.

Open Windows Task Manager. I believe this should work on all versions of XP:

Hit <Ctrl><Alt><Del> and in the dialogue box select 'Task Manager'. Go to the 'Processes' tab. Tick 'Show processes from all users'. Click on the 'Image Name' column header to sort by name. Look through the list for slim.exe. If it's showing, then SlimServer is currently running.

SlimTray.exe is on the list w/almost 11K mem usage & 60 handles but that's the only Slim entry. Does that help?

Mark Lanctot
2007-06-06, 10:57
Two things:

1. WMP (Windows Media Player) 11 uses port 9000. Do you have WMP 11?

2. There was some obscure fix for the "service already running" error which was out there 2 years ago or so. It used to be in the FAQ, can't find it now. Unfortunately the forum search function isn't working for me at the moment - it keeps trying to download "search.php" rather than actually searching. This is a pain as it's an extremely obscure fix which you could never stumble into by accident, involving some little-used command on the command line. Hopefully I'm jogging someone else's memory here, because I can't find it.

Shep
2007-06-06, 10:57
According to the Windows Media player help file, Windows Media sharing does not use port 9000.

The following table shows the firewall ports that must be opened if you want to share media to other devices.
Port
Protocol
Scope

1900
UDP
local subnet only

2869
TCP
local subnet only

10243
TCP
local subnet only

10280-10284
UDP
local subnet only


From the Windows Start Menu, goto Run

Type eventvwr, and look in the Application section of Event Viewer. Look through any errors listed for mention of Slimserver or Application errors.

Lots (dozens) of 'Information' entries in the Event Viewer related to MySQL and the following 'Warning' related to MySQL..."Can't open and lock time zone table: Table 'mysql.time_zone_leap_second' doesn't exist trying to live without them". But I don't see any entries w/SlimSerer.

oreillymj
2007-06-06, 16:05
The time zone entry is fine. It's more informational than a warning. Slimserver works just fine without it.

So it appears you don't have Slim.exe running, but when run from the command prompt it detects a previously rnning instance.

Very weird.

Try opening a command window. Start->Run->cmd

Cd "C:\Program Files\SlimServer\server"

Type slim.exe -remove
slim.exe -install

Then run slim.exe, see if it stay's running.

oreillymj
2007-06-06, 16:19
BTW - This thread mentions WMP11 using port 9000, but I cannot find a mention of this in the help file or in the list of ports that the "Windows Media Player Network Sharing Service" adds to the Windows firewall rules. However I have found that Twonkyviosion uses port 9000 if free.

From the Twonky FAQ

FAQ Network Config The server ports

The ports used by the server are:
UDP 1030, 1900, 9080
TCP starting at 9000 until a free port is found.

To rule out WMP, go to Start->Run ->Services.msc
Scroll down the list to "Windows Media Player Network Sharing Service" and double click on it. If started, click stop and set the Startup type to Manual, then click Ok.

Are you running Twonky?

bpa
2007-06-06, 16:45
Alternatively start slim.exe with --httpport 9001 and use http://localhost:9001

There are some minor bugs with using port other than 9000 and so use 6.5.2 or better 6.5.3

MrStan
2007-06-07, 00:41
BTW - This thread mentions WMP11 using port 9000, but I cannot find a mention of this in the help file or in the list of ports that the "Windows Media Player Network Sharing Service" adds to the Windows firewall rules.

By default Windows Media Player 11 does not use port 9000. I am using it at the moment with Vista. But other users have discovered this problem in the past therefore I suspect it is a plugin or option that causes this.

You can check this by setting Server Settings - Network - Web Server Port Number to 9001 then use the URL http://127.0.0.1:9001/ to view.

JJZolx
2007-06-07, 00:56
By default Windows Media Player 11 does not use port 9000. I am using it at the moment with Vista. But other users have discovered this problem in the past therefore I suspect it is a plugin or option that causes this.

You can check this by setting Server Settings - Network - Web Server Port Number to 9001 then use the URL http://127.0.0.1:9001/ to view.

If the server isn't starting up, he won't be able to set that on the Server Settings > Network page. :-)

It would have to be done by editing slimserver.pref in the server folder. Open the file using Wordpad and search for the 9000 and change it.

Then try starting up SlimServer again from the Windows Services applet (Start > Settings > Control Panel > Administrative Tools > Services, then look for SlimServer). BTW, going to the services applet would be another way to check if the SlimServer service is currently running. If it is, then the Status will show as 'Started'.

Probably just easier using bpa's suggestion of trying to start SlimServer from the command-line using the --httpport 9001 option. Once it's running on that port and the web interface is accessible, then the port could be changed permanently to 9001 using the Server Settings > Network page.

Don't forget that if you run on port 9001 that you'll also have to open this port in any firewalls that are running on the same machine. Until things are going, though, I'd disable any firewalls.

chiphart
2007-06-07, 03:53
Shep wrote:
> Thanks for the reply. I research how to reinstall XP as a last resort
> if it comes to that. I'd like to get SS to work on this laptop & it
> would be pretty much dedicated to SS / SB activity along with the
> external hard drive with all my music.

I'll be the first to say it, I guess:

It might be easier to download the slimCD and toss it in this
laptop. It certainly won't have the problem you're having
and it's pretty bulletproof.

Or you can just load Ubuntu/Fedora/whatever on your machine :-)

--
Chip Hart - Pediatric Solutions * Physician's Computer Company
chip @ pcc.com * 1 Main St. #7, Winooski, VT 05404
800-722-7708 * http://www.pcc.com/~chip
f.802-846-8178 * Pediatric Software Just Got Smarter.
Your Practice Just Got Healthier.

Shep
2007-06-07, 07:10
Just wanted to offer my thanks & appreciation for the many suggestions so far. Give me a little time to understand and implement your suggestions and I'll get back w/the results. Maybe there's hope for getting SlimServer up & running again.

Shep
2007-06-07, 07:19
The time zone entry is fine. It's more informational than a warning. Slimserver works just fine without it.

So it appears you don't have Slim.exe running, but when run from the command prompt it detects a previously rnning instance.

Very weird.

Try opening a command window. Start->Run->cmd

Cd "C:\Program Files\SlimServer\server"

Type slim.exe -remove
slim.exe -install

Then run slim.exe, see if it stay's running.

Thanks,not sure this is what u wanted but here's what I got.

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Owner>Cd "C:\Program Files\SlimServer\server"

C:\Program Files\SlimServer\server>slim.exe -remove
SlimServer removed.

C:\Program Files\SlimServer\server>slim.exe -install
slimsvc installed as SlimServer.

C:\Program Files\SlimServer\server>run slim.exe
'run' is not recognized as an internal or external command,
operable program or batch file.

C:\Program Files\SlimServer\server>slim.exe
2007-06-07 10:16:32.9598 ERROR: There is already another copy of the SlimServer
running on this machine. (Unknown error)


C:\Program Files\SlimServer\server>

Shep
2007-06-07, 07:34
BTW - This thread mentions WMP11 using port 9000, but I cannot find a mention of this in the help file or in the list of ports that the "Windows Media Player Network Sharing Service" adds to the Windows firewall rules. However I have found that Twonkyviosion uses port 9000 if free.

From the Twonky FAQ

FAQ Network Config The server ports

The ports used by the server are:
UDP 1030, 1900, 9080
TCP starting at 9000 until a free port is found.

To rule out WMP, go to Start->Run ->Services.msc
Scroll down the list to "Windows Media Player Network Sharing Service" and double click on it. If started, click stop and set the Startup type to Manual, then click Ok.

Are you running Twonky?


I have Win Media Player 10.0 installed.

I am not running Twonky.

After adjusting the settings for WMP in Services.msc as suggested I tried starting SlimServer from Services.msc without success. Got the error message that says in effect 'SlimServer stared then stopped...this happens when there's not work to do'. This has been the case since SS originally falied.

Shep
2007-06-07, 07:48
Alternatively start slim.exe with --httpport 9001 and use http://localhost:9001

There are some minor bugs with using port other than 9000 and so use 6.5.2 or better 6.5.3

Thanks bpa,
I'm gonna need additional help to follow your suggestion as I don't know what "Alternatively start slim.exe with --httpport 9001 and use http://localhost:9001" requires. I clicked on the link above and got:

Internet Explorer cannot display the webpage

Most likely causes:
You are not connected to the Internet.
The website is encountering problems.
There might be a typing error in the address.

Do I need to change the port designation that is used by SS? How do I do it?

bpa
2007-06-07, 08:19
I don't know if MCE is different but the following is XP.

You should have 6.5.2 or 6.5.3 installed as SlimTray of 6.5.1 or earlier does not save the changed port address in the web link and will always try to open browser on port 9000.

1. Goto Run menu under the Start button enter "cmd" in the open box and press OK
2. You should now have a command window open
3. change directory to the won with slim.exe. If yoiu hgave used default the following command will work
cd "\Program Files\SlimServer\server"
4. Then type (the d_startup is to check what is happening)
slim --httpport 9001 --d_startup
5. If slim starts up OK - try accessing with the browser with the URL http://127.0.0.1:9001
6. Slimserver will remember the new port address on subsequent startups so you can stop slimserver and then try to start using the system tray app.

Shep
2007-06-07, 08:22
If the server isn't starting up, he won't be able to set that on the Server Settings > Network page. :-)

It would have to be done by editing slimserver.pref in the server folder. Open the file using Wordpad and search for the 9000 and change it.

Then try starting up SlimServer again from the Windows Services applet (Start > Settings > Control Panel > Administrative Tools > Services, then look for SlimServer). BTW, going to the services applet would be another way to check if the SlimServer service is currently running. If it is, then the Status will show as 'Started'.

Probably just easier using bpa's suggestion of trying to start SlimServer from the command-line using the --httpport 9001 option. Once it's running on that port and the web interface is accessible, then the port could be changed permanently to 9001 using the Server Settings > Network page.

Don't forget that if you run on port 9001 that you'll also have to open this port in any firewalls that are running on the same machine. Until things are going, though, I'd disable any firewalls.

OK, first I disabled Windows firewall. Next edited slimserver.pref in the server folder and changed port to 9001 & saved. Then started up SlimServer from the Windows Services applet and got the error message:
"SlimServer service on Local Computer started then stopped. Some services stop automatically if they have no work to do."

For what it's worth, when Services applet was opened there was no status indicated for SlimServer (i.e. it was blank).

Shep
2007-06-07, 08:38
I don't know if MCE is different but the following is XP.

You should have 6.5.2 or 6.5.3 installed as SlimTray of 6.5.1 or earlier does not save the changed port address in the web link and will always try to open browser on port 9000.

1. Goto Run menu under the Start button enter "cmd" in the open box and press OK
2. You should now have a command window open
3. change directory to the won with slim.exe. If yoiu hgave used default the following command will work
cd "\Program Files\SlimServer\server"
4. Then type (the d_startup is to check what is happening)
slim --httpport 9001 --d_startup
5. If slim starts up OK - try accessing with the browser with the URL http://127.0.0.1:9001
6. Slimserver will remember the new port address on subsequent startups so you can stop slimserver and then try to start using the system tray app.

bpa, Here's results of instructions above. Seen this before right? Did I execute correctly?

C:\Program Files\SlimServer\server>slim --httpport 9001 --d_startup
Got @INC containing:
C:/Program Files/SlimServer/server
C:\Program Files\SlimServer\server

Extended @INC to contain:
C:\Program Files\SlimServer\server\CPAN\arch\5.8\MSWin32-x86-multi-thread
C:\Program Files\SlimServer\server\CPAN\arch\5.8\MSWin32-x86-multi-thread\auto
C:\Program Files\SlimServer\server\CPAN\arch\5.8.8\MSWin32-x86-multi-thread
C:\Program Files\SlimServer\server\CPAN\arch\5.8.8\MSWin32-x86-multi-thread\auto

C:\Program Files\SlimServer\server\CPAN\arch\5.8\MSWin32-x86-multi-thread
C:\Program Files\SlimServer\server\CPAN\arch\5.8\MSWin32-x86-multi-thread\auto
C:\Program Files\SlimServer\server\CPAN\arch\MSWin32-x86-multi-thread
C:\Program Files\SlimServer\server\lib
C:\Program Files\SlimServer\server\CPAN
C:/Program Files/SlimServer/server
C:/Program Files/SlimServer/server
C:\Program Files\SlimServer\server

Loaded module: [Time::HiRes] ok!
Loaded module: [DBD::mysql] ok!
Loaded module: [DBI] ok!
Loaded module: [XML::Parser::Expat] ok!
Loaded module: [HTML::Parser] ok!
Loaded module: [Compress::Zlib] ok!
Loaded module: [Digest::SHA1] ok!
Loaded module: [YAML::Syck] ok!
Loaded module: [GD] ok!
Loaded module: [Locale::Hebrew] ok!
The following modules are loaded after the first attempt:
YAML/Syck.pm => /PerlApp/YAML/Syck.pm
IO/Handle.pm => /PerlApp/IO/Handle.pm
re.pm => /PerlApp/re.pm
HTML/Parser.pm => /PerlApp/HTML/Parser.pm
File/Spec/Functions.pm => /PerlApp/File/Spec/Functions.pm
List/Util.pm => /PerlApp/List/Util.pm
POSIX.pm => /PerlApp/POSIX.pm
SelectSaver.pm => /PerlApp/SelectSaver.pm
ActiveState/Path.pm => /PerlApp/ActiveState/Path.pm
Getopt/Long.pm => /PerlApp/Getopt/Long.pm
GD/Polygon.pm => /PerlApp/GD/Polygon.pm
Compress/Zlib.pm => /PerlApp/Compress/Zlib.pm
Locale/Hebrew.pm => /PerlApp/Locale/Hebrew.pm
DBD/mysql.pm => /PerlApp/DBD/mysql.pm
Cwd.pm => /PerlApp/Cwd.pm
warnings.pm => /PerlApp/warnings.pm
Slim/Utils/OSDetect.pm => /PerlApp/Slim/Utils/OSDetect.pm
B.pm => /PerlApp/B.pm
Digest/base.pm => /PerlApp/Digest/base.pm
Fcntl.pm => /PerlApp/Fcntl.pm
/PerlApp/auto/Compress/Zlib/autosplit.ix => /PerlApp/auto/Compress/Zlib/
autosplit.ix
Symbol.pm => /PerlApp/Symbol.pm
Scalar/Util.pm => /PerlApp/Scalar/Util.pm
Exporter.pm => /PerlApp/Exporter.pm
Win32.pm => /PerlApp/Win32.pm
File/Spec.pm => /PerlApp/File/Spec.pm
File/Spec/Win32.pm => /PerlApp/File/Spec/Win32.pm
FindBin.pm => /PerlApp/FindBin.pm
warnings/register.pm => /PerlApp/warnings/register.pm
XSLoader.pm => /PerlApp/XSLoader.pm
Slim/bootstrap.pm => /PerlApp/Slim/bootstrap.pm
Digest/SHA1.pm => /PerlApp/Digest/SHA1.pm
Time/HiRes.pm => /PerlApp/Time/HiRes.pm
IO/Seekable.pm => /PerlApp/IO/Seekable.pm
XML/Parser/Expat.pm => /PerlApp/XML/Parser/Expat.pm
B/Deparse.pm => /PerlApp/B/Deparse.pm
PerlApp/DATA.pm => /PerlApp/PerlApp/DATA.pm
DBI.pm => /PerlApp/DBI.pm
GD/Image.pm => /PerlApp/GD/Image.pm
Config.pm => /PerlApp/Config.pm
File/Basename.pm => /PerlApp/File/Basename.pm
/PerlApp/auto/POSIX/autosplit.ix => /PerlApp/auto/POSIX/autosplit.ix
ActivePerl/Config.pm => /PerlApp/ActivePerl/Config.pm
Win32/FileSecurity.pm => /PerlApp/Win32/FileSecurity.pm
IO.pm => /PerlApp/IO.pm
Carp.pm => /PerlApp/Carp.pm
FileHandle.pm => /PerlApp/FileHandle.pm
Exporter/Heavy.pm => /PerlApp/Exporter/Heavy.pm
File/Spec/Unix.pm => /PerlApp/File/Spec/Unix.pm
auto/POSIX/load_imports.al => /PerlApp/auto/POSIX/load_imports.al
vars.pm => /PerlApp/vars.pm
strict.pm => /PerlApp/strict.pm
constant.pm => /PerlApp/constant.pm
Config_heavy.pl => /PerlApp/Config_heavy.pl
IO/File.pm => /PerlApp/IO/File.pm
overload.pm => /PerlApp/overload.pm
AutoLoader.pm => /PerlApp/AutoLoader.pm
HTML/Entities.pm => /PerlApp/HTML/Entities.pm
lib.pm => /PerlApp/lib.pm
GD.pm => /PerlApp/GD.pm
DynaLoader.pm => /PerlApp/DynaLoader.pm

The following modules are loaded after the second attempt:
YAML/Syck.pm => /PerlApp/YAML/Syck.pm
IO/Handle.pm => /PerlApp/IO/Handle.pm
re.pm => /PerlApp/re.pm
HTML/Parser.pm => /PerlApp/HTML/Parser.pm
File/Spec/Functions.pm => /PerlApp/File/Spec/Functions.pm
List/Util.pm => /PerlApp/List/Util.pm
POSIX.pm => /PerlApp/POSIX.pm
SelectSaver.pm => /PerlApp/SelectSaver.pm
ActiveState/Path.pm => /PerlApp/ActiveState/Path.pm
Getopt/Long.pm => /PerlApp/Getopt/Long.pm
GD/Polygon.pm => /PerlApp/GD/Polygon.pm
Compress/Zlib.pm => /PerlApp/Compress/Zlib.pm
Locale/Hebrew.pm => /PerlApp/Locale/Hebrew.pm
DBD/mysql.pm => /PerlApp/DBD/mysql.pm
Cwd.pm => /PerlApp/Cwd.pm
warnings.pm => /PerlApp/warnings.pm
Slim/Utils/OSDetect.pm => /PerlApp/Slim/Utils/OSDetect.pm
B.pm => /PerlApp/B.pm
Digest/base.pm => /PerlApp/Digest/base.pm
Fcntl.pm => /PerlApp/Fcntl.pm
/PerlApp/auto/Compress/Zlib/autosplit.ix => /PerlApp/auto/Compress/Zlib/
autosplit.ix
Symbol.pm => /PerlApp/Symbol.pm
Scalar/Util.pm => /PerlApp/Scalar/Util.pm
Exporter.pm => /PerlApp/Exporter.pm
Win32.pm => /PerlApp/Win32.pm
File/Spec.pm => /PerlApp/File/Spec.pm
File/Spec/Win32.pm => /PerlApp/File/Spec/Win32.pm
FindBin.pm => /PerlApp/FindBin.pm
warnings/register.pm => /PerlApp/warnings/register.pm
XSLoader.pm => /PerlApp/XSLoader.pm
Slim/bootstrap.pm => /PerlApp/Slim/bootstrap.pm
Digest/SHA1.pm => /PerlApp/Digest/SHA1.pm
Time/HiRes.pm => /PerlApp/Time/HiRes.pm
IO/Seekable.pm => /PerlApp/IO/Seekable.pm
XML/Parser/Expat.pm => /PerlApp/XML/Parser/Expat.pm
B/Deparse.pm => /PerlApp/B/Deparse.pm
PerlApp/DATA.pm => /PerlApp/PerlApp/DATA.pm
DBI.pm => /PerlApp/DBI.pm
GD/Image.pm => /PerlApp/GD/Image.pm
Config.pm => /PerlApp/Config.pm
File/Basename.pm => /PerlApp/File/Basename.pm
/PerlApp/auto/POSIX/autosplit.ix => /PerlApp/auto/POSIX/autosplit.ix
ActivePerl/Config.pm => /PerlApp/ActivePerl/Config.pm
Win32/FileSecurity.pm => /PerlApp/Win32/FileSecurity.pm
IO.pm => /PerlApp/IO.pm
Carp.pm => /PerlApp/Carp.pm
FileHandle.pm => /PerlApp/FileHandle.pm
Exporter/Heavy.pm => /PerlApp/Exporter/Heavy.pm
File/Spec/Unix.pm => /PerlApp/File/Spec/Unix.pm
auto/POSIX/load_imports.al => /PerlApp/auto/POSIX/load_imports.al
vars.pm => /PerlApp/vars.pm
strict.pm => /PerlApp/strict.pm
constant.pm => /PerlApp/constant.pm
Config_heavy.pl => /PerlApp/Config_heavy.pl
IO/File.pm => /PerlApp/IO/File.pm
overload.pm => /PerlApp/overload.pm
AutoLoader.pm => /PerlApp/AutoLoader.pm
HTML/Entities.pm => /PerlApp/HTML/Entities.pm
lib.pm => /PerlApp/lib.pm
GD.pm => /PerlApp/GD.pm
DynaLoader.pm => /PerlApp/DynaLoader.pm

Loaded module: [Slim::Utils::PerlRunTime] ok!
2007-06-07 11:31:41.5428 ERROR: There is already another copy of the SlimServer
running on this machine. (Unknown error)


C:\Program Files\SlimServer\server>

snarlydwarf
2007-06-07, 08:43
Okay, this message is generated in Networking/UDP.pm:


$udpsock = IO::Socket::INET->new(
Proto => 'udp',
LocalPort => SERVERPORT,
LocalAddr => $main::localClientNetAddr

) or do {

errorMsg("There is already another copy of the SlimServer running on this machine. ($!)\n");
# XXX - exiting in a deep sub is kinda bad. should propagate
# up. Too bad perl doesn't have real exceptions.
exit 1;


In short, if it can't open the UDP port (3483) it gives this.

Your netstat doesn't show 3483 being used, so something else is breaking that: it still sounds like you have a firewall turned on.

bpa
2007-06-07, 08:46
Port 9000 problem are a red herring.

That error message appears when Slimsserver tries to open port 3483 UDP and find someody else is using it or Slim.exe is not allowed to open it (e.g. firewall).

What firewall are you using and has slim.exe been marked as a trusted app. When you re-install slim.exe it is a different "slim.exe" so sometimes it is good to delete the old entry and make a new one.

also check "netstat -an" for anybody using port 3483.

mswlogo
2007-06-07, 09:39
Shep wrote:
> Thanks for the reply. I research how to reinstall XP as a last resort
> if it comes to that. I'd like to get SS to work on this laptop & it
> would be pretty much dedicated to SS / SB activity along with the
> external hard drive with all my music.

I'll be the first to say it, I guess:

It might be easier to download the slimCD and toss it in this
laptop. It certainly won't have the problem you're having
and it's pretty bulletproof.

Or you can just load Ubuntu/Fedora/whatever on your machine :-)

--
Chip Hart - Pediatric Solutions * Physician's Computer Company
chip @ pcc.com * 1 Main St. #7, Winooski, VT 05404
800-722-7708 * http://www.pcc.com/~chip
f.802-846-8178 * Pediatric Software Just Got Smarter.
Your Practice Just Got Healthier.

That is a pretty cool idea !!!

mswlogo
2007-06-07, 09:42
If you don't do any web surfing via the server computer, after reinstalling windoze, disable automatic updates. All you need is for it to run- you don't need all the updates. I can't count the number of problems that stopped happening after I disabled auto updates in my win2k machine. M$ OSes are just riddled with holes and they produce so many band-aids for them I doubt anyone at M$ knows what is going on any more.

Switch to linux - ubuntu has easy install and slimserver works.

TD

Bad idea, even if you don't surf you want most of the udates.
I run about 40 XP machines at work and we install every update. We have a problem now and then with an update but it's pretty rare.

mswlogo
2007-06-07, 10:29
My advice to Shep is find a freind that can help him that knows this stuff. Even for an expert it can take a few long hours to sort it out. Even reinstalling XP is not trvial for a novice.

If you have a recovery CD or you may have a recovery image on the laptop itself that is the simplest for the novice. Normally I don't recommend this but since it's a Music Server and your music is on a seperate drive, I'd do it anyway for nice clean server.

I respect anyone who wants to sort this out and learn though and there are some great tips here.

Things I would check is

Windows XP Firewall Exceptions (Like to see Dialog showing it is off or Exceptions added).
Network Stack (Often Virus Programm will add to the Network Stack to add Port Blocking) Screen Shot of Network Stack.
You might try turning the Windows Firewall ON and it might tell you another is running. Then show screen show with exceptions.
I'd uninstall SlimServer and after that I would

Show Screen Shot of all services (to see it's completely removed)
Show List of tasks running to show no remnants left
Show List of Program Files (Just Folders to be sure it's removed).
Show List of Installed Applications might help to.
Show List from netstat as described above to be sure all ports are free that should be

Again this is a fair amount of work to do posting screen shots on this forum. And it still may fail when you install, in that there is a well hidden firewall still there.

Mark Lanctot
2007-06-07, 11:48
Two links to check:

http://wiki.slimdevices.com/index.cgi?ServerIsAlreadyRunning

and

http://forums.slimdevices.com/showthread.php?t=33516

Shep
2007-06-07, 20:20
In the end it took a Windows reinstall to get SlimServer working again. So, 2 months and 14 hours later I've got music again!!

Thanks to all for your patience and assistance. I appreciate your willingness to help a mostly incompetent computer person get SS back on track again. Best regards to all.

pfarrell
2007-06-07, 20:29
Shep wrote:
> Thanks to all for your patience and assistance. I appreciate your
> willingness to help a mostly incompetent computer person get SS back on
> track again. Best regards to all.

Great to hear you are hearing music again.

Ready to install Linux?

--
Pat
http://www.pfarrell.com/music/slimserver/slimsoftware.html

mswlogo
2007-06-07, 20:33
Awesome at least you got it up.

Shep
2007-06-08, 11:28
Shep wrote:
> Thanks to all for your patience and assistance. I appreciate your
> willingness to help a mostly incompetent computer person get SS back on
> track again. Best regards to all.

Great to hear you are hearing music again.

Ready to install Linux?

--
Pat
http://www.pfarrell.com/music/slimserver/slimsoftware.html

Hey Pat,
It's hard to love Windows ain't it!!! As soon as I recover from yesterday's marathon I'm gonna start the Linux experimentation.
Thanks again.