PDA

View Full Version : FATAL: There is already another copy of the SqueezeboxServerrunning on this machine



Tom Hutcheson
2010-01-01, 14:25
Hi dsdreamer -

First - thanks. I did what you suggested (I think). I ran the netstat -ab's
but don't see anything that might be intefering (but I'm not very good with
interpreting the results). I ran a pre-install and a post-install. I
reviewed all start-up entries but don't see anything unusual. Same with the
installed programs - they look reasonable. I googled a few that I wasn't
familiar with but they seem ok. Could you taka a look at the new info if you
get a chance? You may see something that I don't. I posted to [url]
http://www.scurvydog.us/slimproblem/index.htm (start-ups and installed
programs are at the bottom).
Thanks -
Hutch


--You have done all the obvious things and them some. My suggestion would
be to work on the theory that some other program has opened a critical port
that SBS needs.
--
--running
---Code:

netstat -ab

--from a cmd shell can give you additional clues about what programs are
opening which ports on the machine. I would be interested in how that looks
when all the Squeeze related stuff is uninstalled, and again when installed.
Take a closer a look at any processes that have ports open that you don't
recognize.

I would further suggest running MSCONFIG and running a diagnostic startup
with as few startup items and services running as possible. Does this make
SBS installation possible?

Take a good look at the list of installed programs, are then any additional
security related apps still lurking? (prevx, spybot S&D, etc?) Are there any
resident portions of such programs still lurking after an uninstall
(immunize, tea timer etc)?
__________________
----------------------
"Dreamer, easy in the chair that really fits you..."

dsdreamer
2010-01-01, 16:25
Tom,

I looked at the outputs of netstat that you posted. I notice that the name of the server executable was SqueezeboxServer-7.4.1.tmp, which I think is a symptom of being stuck half way through an installation.

I also noticed that lsass.exe had attempted 3 connections to the MySQL port of 9092 and also had one connection attempt to nat.dc.squeezenetwork.com:3483. This could be normal behavior.

You might try creating a new user with Admin privileges and try the install logged in as that user.

Also, consider finding and removing any detritus left behind by previous install attempts (even though you expect REVO to work perfectly), and especially make sure that the MySQL cache is really gone.

Finally, try using a non-default location for a new install attempt when you get to the "Select Destination Location" screen.

(Frankly, you are probably smarter at this kind of thing than I am, but I am doing my best to help.)

Tom Hutcheson
2010-01-01, 17:40
dsdreamer -

Thanks - good suggestions here.

SqueezeboxServer-7.4.1.tmp does seem to be a symptom of the incomplete install - agreed.

I created new admin account but same results. Also, same results using different install location.

Re cleaning up the detritus of prior installs - is there something specific that I can search for? I verified that the program files folder gets removed as well as the "\Documents and Settings\All Users\Application Data\SqueezeCenter" folders - this guy has a cache subfolder - is that the MySQL cache that your speaking of or is there somewhere else that I should be looking?

I'm really out of my element with the netstats and didn't actually see the lsass connections to Slim ports.

I didn't mention before but I also ran a full virus scan (Avast) as well as a MalwareBytes scan.

I really apreciate your help. Keep the ideas coming. Thanks -

Tom



Tom,

I looked at the outputs of netstat that you posted. I notice that the name of the server executable was SqueezeboxServer-7.4.1.tmp, which I think is a symptom of being stuck half way through an installation.

I also noticed that lsass.exe had attempted 3 connections to the MySQL port of 9092 and also had one connection attempt to nat.dc.squeezenetwork.com:3483. This could be normal behavior.

You might try creating a new user with Admin privileges and try the install logged in as that user.

Also, consider finding and removing any detritus left behind by previous install attempts (even though you expect REVO to work perfectly), and especially make sure that the MySQL cache is really gone.

Finally, try using a non-default location for a new install attempt when you get to the "Select Destination Location" screen.

(Frankly, you are probably smarter at this kind of thing than I am, but I am doing my best to help.)

Tom Hutcheson
2010-01-04, 09:10
Hi - I'm the original poster and I'm still very stuck on this. I was wondering if it might be possible for one of the developers or code contributors to scan the code for the above message (not sure how difficult that is obviously)? The message seems to be coming directly from the Squeezebox Server install routine and if that is the case it may be possible to tell what condition is specifically triggering the error.

Also, another potential clue that someone just may recognize from their own past debugging is from the Squeezebox Server Control Panel on the Diagnostics tab - the Squeezebox Server ports show that they've failed but the MySqueezebox.com ports report that they're OK.

logs and control panel screenshots at http://www.scurvydog.us/slimproblem/index.htm

Thanks for any help.-
Tom

bpa
2010-01-04, 09:26
IIRC there is only one source for this message and it is the inability of SBS/SC to open port 3483 in UDP. This is usually because

1. Another copy of Squeezecenter
2. Security permissions
3. A SB player is trying to communicate with PC and port 3483 is opened by another handler.

Tom Hutcheson
2010-01-04, 10:25
Thanks, bpa.

Can you help me walk through this please?

1. Another copy of Squeezecenter - I wish I could find another copy of SqueezeCenter cause that would be the easiest solution. I've scanned the folders and the registry and don't find anything.

2. Security permissions - I know that this is often a windows culprit. The machine is running under an admin account in XP. I followed dsdreamer's advice and created another admin account and attempted to install to a different default location but neither attempt was successful (same error).

3. A SB player is trying to communicate with PC and port 3483 is opened by another handler. How do I try to detect this (am not very knowledgeable about any aspect of this). Would a netstat show this (a pre-install netstat has no reference to 3483 at all and a post-install (install failed) has a 3483 TCP as follows (lsass.exe - TCP, Vostro:1378, nat.dc.squeezenetwork.com:3483, TIME_WAIT, 0)?

Last few bits of possibly related info - machine is connected to a router; I've tried the installs after uninstalling ZoneAlarm and with Windows Firewall enabled and disabled. I have several players in the house but they are powered off and the machine that I normally run my server from doesn't have the software running right now.

Thank you very much for any help.
Tom







IIRC there is only one source for this message and it is the inability of SBS/SC to open port 3483 in UDP. This is usually because

1. Another copy of Squeezecenter
2. Security permissions
3. A SB player is trying to communicate with PC and port 3483 is opened by another handler.

Tom Hutcheson
2010-01-04, 10:31
bpa -

Sorry - one more thing. The Squeeze Control Panel (under diagnostics) shows an Alert as follows: Possible software conflict found. We were not able to successfully communicate with mysqueezebox.com. This might be a temporary internet issue, etc.

Is this pertinent to problem?

Thanks -
Tom

bpa
2010-01-04, 10:37
Another copy of Squeezecenter running not installed on a disk - so you need to look at task manager.

A better way is to check whether port 3483 is in use by running netstat - if it is not then security is the problem. You seem to indicate there is something using it - can copy copy complete output to a text file, zip and attach to post. I think if lassass.exe is running on port 3483 then something is trying to communicate with PC.

ZoneAlarm still interfere with apps even when disabled - the only way to be sure is to uninstall.

What version of Windows ?

Tom Hutcheson
2010-01-04, 13:05
bpa -

Looked at TaskManager before and after. "Before" shows nothing, "During" shows squeezebox-server-7.4.1 exe and tmp, and "After" shows squeezeboxcp and squeezetray

Windows version is XP Home Edition SP3.

I uninstalled ZoneAlarm (using Windows Firewall) and had the same issue. Then I disabled Windows Firewall but same error.

I posted my logs, netstats, and various screenprints to a webpage at:
http://www.scurvydog.us/slimproblem/index.htm - could you take a look to see if you see anything pertinent there please?

Thanks for the help. Please let me know if you see anything strange.

PS - I screwed up with my 2nd post and seperated it inadvertently from the thread that you're reading now. For clarity, my original post was a follows:

=============
Hi All -

First time poster. Happy Slimp3/Squeezebox user since 2003. Best things in
life - wife, kids, Squeezeboxes (not necessarily in that order). Have turned
on a bunch of friends over the years and that is the occasion of this post.

Trying to set-up a friend with a new Classic but can't get the server
software installed on their desktop no matter what I try (v7.4.1, but same
results with v7.3.1). The error is always "FATAL: There is already another
copy of the Squeezebox Server running on this machine" (even the 1st attempt
at installing when there couldn't possibly have been any prior versions).
Searched the forums and saw a few NAS related entries during a debug phase
but nothing else really. One of the posts had suggested that the problem is
really related to one of the Slim ports being in use by something else so
that the install thinks the server is already installed but can't figure
anything out. The machine is a Dell Vostro 200 with XP SP3. Tried
the expected steps: uninstalled ZoneAlarm; shutdown the AV software,
CCleaner purge and registry clean, and utilize Revo Uninstaller for the
uninstalls. After working for hours at my friend's house I temporarily
installed the server software (in minutes, as expected) on her laptop
without issue (different machine obviously but her same network). Brought
her desktop to my house but exact same results.

I've put up all pertinent screenshots (firewall, control panel, etc. and the
slim logs at this address - http://www.scurvydog.us/slimproblem/index.htm

Sure could use your help. Thanks -
Hutch
=============



Another copy of Squeezecenter running not installed on a disk - so you need to look at task manager.

A better way is to check whether port 3483 is in use by running netstat - if it is not then security is the problem. You seem to indicate there is something using it - can copy copy complete output to a text file, zip and attach to post. I think if lassass.exe is running on port 3483 then something is trying to communicate with PC.

ZoneAlarm still interfere with apps even when disabled - the only way to be sure is to uninstall.

What version of Windows ?

bpa
2010-01-04, 14:41
There is something wrong with the installation.

* There are no Squeezebox Server entries for TCP 3483 and UDP 3483 - ther only entries are for SqueezeCenter which is 7.3.x

* the executable running is SqueezeboxServer-7.4.1.exe which is the program run for installation not the actual squeezeserver application.

The log file are of the SqueezeServer install and not Squeezeserver running as SqueezeBoxServer-7.4.1.exe is the install program whereas SqueezeSvr.exe is the actual squeezeserver application.

I think you have a number of problem - one of which is the posted file are misleading.

I suggest
* uninstall SqueezeServer and remove all prefs and delete the Squeezebox directory and delete all log files.
* delete all SqueezeboxServer and SqueezeCenter entries in Windows firewall
* install SqueezeBoxServer-7.4.1.exe and then shutdown SqueezeServer from control panel and stop control pane and systrap apps.
* check there is a copy of SqueezeSvr.exe in the Squeezebox directory.
* start systray app and then start Squeezeserver from Systray app.

Wait a few minutes and then check and copy Task manager and netstat as before.

Tom Hutcheson
2010-01-04, 15:56
--There is something wrong with the installation.

Yes you're right - the installation never completes - ever - no matter what I do. That's what the problem is. The Control Panel always shows "Status: The server is stopped". Any attempt to start the server ends with the "FATAL: There is already another copy of the SqueezeboxServerrunning on this machine" on the server.log file. I can never start the server because of this message.

The netstats and task manager screenshots that I posted are all from that point of view - the install is crashing. I took it to mean from your prior posts that perhaps the 3483 port is busy or owned or whatever while the install is proceeding. I was hoping that the Before install, During install, and After install netstat "views" of the install process would have a few clues.

I appreciate your help and want to be clear about the problem - the install always shows the above fatal error message and the server can never be started. So from that perspective, do the netstats that I posted show any clues re the necessary Slim ports? I was hoping you would see a problem there.

Any time I attempt an install all Slim folders (in Program Folders and also AllUsers\ApplicationData\Squeezebox and all registry entries (at least for SqueezeCenter and Squeezebox) are blown away beforehand.

The Event Viewer Security log shows no warnings or errors during installation.

After a failed install I tried to run the SqueezeSvr.exe from a cmd window and get the usual error as follows:

C:\>"C:\Program Files\Squeezebox2\server\SqueezeSvr.exe"
[10-01-04 17:42:55.0156] main::init (320) Starting Squeezebox Server (v7.4.1, r28947, Tue Oct 20 08:13:15 PDT 2009) perl
5.010000
[10-01-04 17:43:02.2812] Slim::Networking::UDP::init (39) FATAL: There is already another copy of the Squeezebox Server
running on this machine. (Unknown error)
[10-01-04 17:43:02.2823] Slim::Utils::Misc::msg (1165) Warning: [17:43:02.2821] FATAL: There is already another copy of
the Squeezebox Server running on this machine. (Unknown error) at /<C:\Program Files\Squeezebox2\server\SqueezeSvr.exe>L
og/Log4perl/Logger.pm line 901

* uninstall SqueezeServer and remove all prefs and delete the Squeezebox directory and delete all log files.
-- Done

* delete all SqueezeboxServer and SqueezeCenter entries in Windows firewall
-- haven't done this but I've disabled the Windows firewall, Windows Defender (and uninstalled ZoneAlarm).

* install SqueezeBoxServer-7.4.1.exe and then shutdown SqueezeServer from control panel and stop control pane and systrap apps.
-- The install never completes without the fatal error so server never starts

* check there is a copy of SqueezeSvr.exe in the Squeezebox directory.
-- in PF\Squeezebox there is SqueezeTray.exe
-- in PF\Squeezebox\server there is scanner.exe, squeezeboxcp.exe, and squeezesvr.exe

* start systray app and then start Squeezeserver from Systray app.
-- same error every time

Going crazy. Hoping you folks out there can see something.

Starting to worry -
Tom


There is something wrong with the installation.

* There are no Squeezebox Server entries for TCP 3483 and UDP 3483 - ther only entries are for SqueezeCenter which is 7.3.x

* the executable running is SqueezeboxServer-7.4.1.exe which is the program run for installation not the actual squeezeserver application.

The log file are of the SqueezeServer install and not Squeezeserver running as SqueezeBoxServer-7.4.1.exe is the install program whereas SqueezeSvr.exe is the actual squeezeserver application.

I think you have a number of problem - one of which is the posted file are misleading.

I suggest
* uninstall SqueezeServer and remove all prefs and delete the Squeezebox directory and delete all log files.
* delete all SqueezeboxServer and SqueezeCenter entries in Windows firewall
* install SqueezeBoxServer-7.4.1.exe and then shutdown SqueezeServer from control panel and stop control pane and systrap apps.
* check there is a copy of SqueezeSvr.exe in the Squeezebox directory.
* start systray app and then start Squeezeserver from Systray app.

Wait a few minutes and then check and copy Task manager and netstat as before.

bpa
2010-01-04, 18:17
The point I was making is the Fatal message comes from SqueezeSvr.exe - yet your dumps do not show SqueezeSvr.exe running and port 3483 comms are to a port 3483 on a different system. It is necessary to get relevant logs.

The point about deleting the entries is that the install process may be looking at the firewall entries and if it sees an existing SqueezeServer entry it may not redo the firewall setup - deletion of the entries will give a better handle on how far the install is getting. Also Windows Firewall associates an entry with an "exe" signature - sometimes the signature is not updated so that although the entry is there. From past experience I don't trust "disabling" as truly nullifying the firewall. I personally prefer to delete entries and then reboot PC.

After a new install - check firewall. Make sure there are SqueezeSvr.exe entries for port 3483 UDP & TCP. IF they are not there add all four entries manually and reboot.

Then, I would stop Squeezetray, set network.logging and server to DEBUG for startup so that logging is maximised from the start (usually by editing the prefs/log.conf file). Then run SqueezeSvr from a command prompt (whose window has been set to somehting like 300x5000)

Tom Hutcheson
2010-01-04, 19:05
Great idea about the firewall entries - I will do that shortly but wanted to ask a couple of questions first and to clarify a point about the situation.

What is it that you see that makes you say that the 3483 comms are to a port 3483 on a different system? Which log of mine do you see that? Are you referring to the ip of 66.150.114.115:3483 (the local machine is 192.168.1.51)? If you are that is the ip of nat.dc.squeezenetwork.com:3483 which from my ping is mysqueezebox.com. If you're not referring to that then I'm not sure what. I only want to make sure we're looking at the same thing and if I have a wrong log to figure out why. Actually this is the only reference I ever see to 3483 - could the call to mysqueezebox be always blocking the port? (sorry I don't know what I'm talking about).

There is no log.conf file in the prefs folder - could this be because the server has never actually started? On my "main" server I run 7.3.1 and I see this file so I see what you mean but it isn't there at all. Is this file editable anyway - header says that "This file is autogenerated by Slim::Utils::Log". I would need more help / instructions on doing this step anyway (sorry I'm so needy).

Also, just to reiterate - the server never ever starts - it gets shortcircuited by the fatal error.

I will proceed with a reinstall after dumping the firewall entries and your subsequent steps except I don't know how to add the degug entires.

Thanks -
Tom



The point I was making is the Fatal message comes from SqueezeSvr.exe - yet your dumps do not show SqueezeSvr.exe running and port 3483 comms are to a port 3483 on a different system. It is necessary to get relevant logs.

The point about deleting the entries is that the install process may be looking at the firewall entries and if it sees an existing SqueezeServer entry it may not redo the firewall setup - deletion of the entries will give a better handle on how far the install is getting. Also Windows Firewall associates an entry with an "exe" signature - sometimes the signature is not updated so that although the entry is there. From past experience I don't trust "disabling" as truly nullifying the firewall. I personally prefer to delete entries and then reboot PC.

After a new install - check firewall. Make sure there are SqueezeSvr.exe entries for port 3483 UDP & TCP. IF they are not there add all four entries manually and reboot.

Then, I would stop Squeezetray, set network.logging and server to DEBUG for startup so that logging is maximised from the start (usually by editing the prefs/log.conf file). Then run SqueezeSvr from a command prompt (whose window has been set to somehting like 300x5000)

Tom Hutcheson
2010-01-04, 19:44
Deleted all the firewall entries but unfortunately exactly the same outcome.

Do wish there was a way to set debugging on.


[QUOTE=I will proceed with a reinstall after dumping the firewall entries and your subsequent steps except I don't know how to add the degug entires.[/QUOTE]

bpa
2010-01-05, 01:56
Do wish there was a way to set debugging on.


Is there a log.conf file in the prefs directory ?

If so then edit the file using Wordpad and change the following entries - change "ERROR" to "DEBUG"
log4perl.logger.server = ERROR
log4perl.logger.network.protocol = ERROR

If there is no prefs file then when running squeezesvr.exe from the command line use the following after cd to the right directory.

SqueezeSvr.exe --debug server=DEBUG,network.protocol=DEBUG

contrary to help "--debug" gives log message not "--logging".

If the problem is a inaccessible port 3483 then logging will give no additional info but please post the complete log as earlier message may show something. Post the complete log as sometimes missing messages are the symptom.

bpa
2010-01-05, 02:06
What my log looks like when SBS is already running


C:\Program Files\Squeezebox\server>SqueezeSvr.exe --debug server=DEBUG,network.protocol=DEBUG
[10-01-05 08:51:53.4557] main::init (320) Starting Squeezebox Server (v7.4.1, r28947, Tue Oct 20 08:13:15 PDT 2009) perl 5.010000
[10-01-05 08:51:53.4638] main::init (337) Squeezebox Server OS Specific init...
[10-01-05 08:51:53.4644] main::init (398) Squeezebox Server binary search path init...
[10-01-05 08:51:53.4663] main::init (402) Squeezebox Server PluginManager init...
[10-01-05 08:51:53.8189] main::init (405) Squeezebox Server strings init...
[10-01-05 08:51:53.8668] Slim::Utils::Strings::loadStrings (122) Retrieving string data from string cache: C:\Documents and Settings\All Users\Application Data\Squeezebox\Cache\strings.586.bin
[10-01-05 08:51:53.8747] Slim::Utils::Strings::loadStrings (159) String cache contains old data - reparsing string files
[10-01-05 08:51:53.8753] Slim::Utils::Strings::loadStrings (178) Loading string file: C:\Program Files\Squeezebox\server\strings.txt
[10-01-05 08:51:54.2468] Slim::Utils::Strings::loadStrings (178) Loading string file: C:\Program Files\Squeezebox\server\Slim\Plugin\DateTime\strin gs.txt
[10-01-05 08:51:54.2499] Slim::Utils::Strings::loadStrings (178) Loading string file: C:\Program Files\Squeezebox\server\Slim\Plugin\DigitalInput\s trings.txt
[10-01-05 08:51:54.2534] Slim::Utils::Strings::loadStrings (178) Loading string file: C:\Program Files\Squeezebox\server\Slim\Plugin\Podcast\string s.txt
[10-01-05 08:51:54.2576] Slim::Utils::Strings::loadStrings (178) Loading string file: C:\Program Files\Squeezebox\server\Slim\Plugin\Pandora\string s.txt
[10-01-05 08:51:54.2778] Slim::Utils::Strings::loadStrings (178) Loading string file: C:\Program Files\Squeezebox\server\Slim\Plugin\MP3tunes\strin gs.txt
[10-01-05 08:51:54.2799] Slim::Utils::Strings::loadStrings (178) Loading string file: C:\Program Files\Squeezebox\server\Slim\Plugin\Queen\strings. txt
[10-01-05 08:51:54.2815] Slim::Utils::Strings::loadStrings (178) Loading string file: C:\Program Files\Squeezebox\server\Slim\Plugin\Snow\strings.t xt
[10-01-05 08:51:54.3078] Slim::Utils::Strings::loadStrings (178) Loading string file: C:\Program Files\Squeezebox\server\Slim\Plugin\AppGallery\str ings.txt
[10-01-05 08:51:54.3094] Slim::Utils::Strings::loadStrings (178) Loading string file: C:\Program Files\Squeezebox\server\Slim\Plugin\RadioTime\stri ngs.txt
[10-01-05 08:51:54.3115] Slim::Utils::Strings::loadStrings (178) Loading string file: C:\Program Files\Squeezebox\server\Slim\Plugin\Extensions\str ings.txt
[10-01-05 08:51:54.3181] Slim::Utils::Strings::loadStrings (178) Loading string file: C:\Program Files\Squeezebox\server\Slim\Plugin\Mediafly\strin gs.txt
[10-01-05 08:51:54.3205] Slim::Utils::Strings::loadStrings (178) Loading string file: C:\Program Files\Squeezebox\server\Slim\Plugin\Flickr\strings .txt
[10-01-05 08:51:54.3224] Slim::Utils::Strings::loadStrings (178) Loading string file: C:\Program Files\Squeezebox\server\Slim\Plugin\LMA\strings.tx t
[10-01-05 08:51:54.3250] Slim::Utils::Strings::loadStrings (178) Loading string file: C:\Program Files\Squeezebox\server\Slim\Plugin\LineOut\string s.txt
[10-01-05 08:51:54.3266] Slim::Utils::Strings::loadStrings (178) Loading string file: C:\Program Files\Squeezebox\server\Slim\Plugin\Favorites\stri ngs.txt
[10-01-05 08:51:54.3352] Slim::Utils::Strings::loadStrings (178) Loading string file: C:\Program Files\Squeezebox\server\Slim\Plugin\MyApps\strings .txt
[10-01-05 08:51:54.3366] Slim::Utils::Strings::loadStrings (178) Loading string file: C:\Program Files\Squeezebox\server\Slim\Plugin\LineIn\strings .txt
[10-01-05 08:51:54.3402] Slim::Utils::Strings::loadStrings (178) Loading string file: C:\Program Files\Squeezebox\server\Slim\Plugin\InfoBrowser\st rings.txt
[10-01-05 08:51:54.3428] Slim::Utils::Strings::loadStrings (178) Loading string file: C:\Program Files\Squeezebox\server\Slim\Plugin\Deezer\strings .txt
[10-01-05 08:51:54.3458] Slim::Utils::Strings::loadStrings (178) Loading string file: C:\Program Files\Squeezebox\server\Slim\Plugin\SongScanner\st rings.txt
[10-01-05 08:51:54.3488] Slim::Utils::Strings::loadStrings (178) Loading string file: C:\Program Files\Squeezebox\server\Slim\Plugin\Amazon\strings .txt
[10-01-05 08:51:54.3504] Slim::Utils::Strings::loadStrings (178) Loading string file: C:\Program Files\Squeezebox\server\Slim\Plugin\Live365\string s.txt
[10-01-05 08:51:54.3525] Slim::Utils::Strings::loadStrings (178) Loading string file: C:\Program Files\Squeezebox\server\Slim\Plugin\InternetRadio\ strings.txt
[10-01-05 08:51:54.3538] Slim::Utils::Strings::loadStrings (178) Loading string file: C:\Program Files\Squeezebox\server\Slim\Plugin\AudioScrobbler \strings.txt
[10-01-05 08:51:54.3632] Slim::Utils::Strings::loadStrings (178) Loading string file: C:\Program Files\Squeezebox\server\Slim\Plugin\Rescan\strings .txt
[10-01-05 08:51:54.3684] Slim::Utils::Strings::loadStrings (178) Loading string file: C:\Program Files\Squeezebox\server\Slim\Plugin\OPMLGeneric\st rings.txt
[10-01-05 08:51:54.3698] Slim::Utils::Strings::loadStrings (178) Loading string file: C:\Program Files\Squeezebox\server\Slim\Plugin\NetTest\string s.txt
[10-01-05 08:51:54.3723] Slim::Utils::Strings::loadStrings (178) Loading string file: C:\Program Files\Squeezebox\server\Slim\Plugin\Visualizer\str ings.txt
[10-01-05 08:51:54.3742] Slim::Utils::Strings::loadStrings (178) Loading string file: C:\Program Files\Squeezebox\server\Slim\Plugin\RSSNews\string s.txt
[10-01-05 08:51:54.3819] Slim::Utils::Strings::loadStrings (178) Loading string file: C:\Program Files\Squeezebox\server\Slim\Plugin\CLI\strings.tx t
[10-01-05 08:51:54.3846] Slim::Utils::Strings::loadStrings (178) Loading string file: C:\Program Files\Squeezebox\server\Slim\Plugin\PreventStandby \strings.txt
[10-01-05 08:51:54.3876] Slim::Utils::Strings::loadStrings (178) Loading string file: C:\Program Files\Squeezebox\server\Slim\Plugin\Sirius\strings .txt
[10-01-05 08:51:54.3907] Slim::Utils::Strings::loadStrings (178) Loading string file: C:\Program Files\Squeezebox\server\Slim\Plugin\Facebook\strin gs.txt
[10-01-05 08:51:54.3927] Slim::Utils::Strings::loadStrings (178) Loading string file: C:\Program Files\Squeezebox\server\Slim\Plugin\Classical\stri ngs.txt
[10-01-05 08:51:54.3956] Slim::Utils::Strings::loadStrings (178) Loading string file: C:\Program Files\Squeezebox\server\Slim\Plugin\RhapsodyDirect \strings.txt
[10-01-05 08:51:54.4023] Slim::Utils::Strings::loadStrings (178) Loading string file: C:\Program Files\Squeezebox\server\Slim\Plugin\SavePlaylist\s trings.txt
[10-01-05 08:51:54.4059] Slim::Utils::Strings::loadStrings (178) Loading string file: C:\Program Files\Squeezebox\server\Slim\Plugin\RandomPlay\str ings.txt
[10-01-05 08:51:54.4160] Slim::Utils::Strings::loadStrings (178) Loading string file: C:\Program Files\Squeezebox\server\Slim\Plugin\Napster\string s.txt
[10-01-05 08:51:54.4200] Slim::Utils::Strings::loadStrings (178) Loading string file: C:\Program Files\Squeezebox\server\Slim\Plugin\Slacker\string s.txt
[10-01-05 08:51:54.4243] Slim::Utils::Strings::loadStrings (178) Loading string file: C:\Program Files\Squeezebox\server\Slim\Plugin\JiveExtras\str ings.txt
[10-01-05 08:51:54.4274] Slim::Utils::Strings::loadStrings (178) Loading string file: C:\Program Files\Squeezebox\server\Slim\Plugin\SlimTris\strin gs.txt
[10-01-05 08:51:54.4290] Slim::Utils::Strings::loadStrings (178) Loading string file: C:\Program Files\Squeezebox\server\Slim\Plugin\xPL\strings.tx t
[10-01-05 08:51:54.4327] Slim::Utils::Strings::loadStrings (178) Loading string file: C:\Program Files\Squeezebox\server\Slim\Plugin\LastFM\strings .txt
[10-01-05 08:51:54.4363] Slim::Utils::Strings::loadStrings (178) Loading string file: C:\Program Files\Squeezebox\server\Slim\Plugin\iTunes\strings .txt
[10-01-05 08:51:54.4458] Slim::Utils::Strings::loadStrings (178) Loading string file: C:\Program Files\Squeezebox\server\Slim\Plugin\Sounds\strings .txt
[10-01-05 08:51:54.4475] Slim::Utils::Strings::loadStrings (178) Loading string file: C:\Program Files\Squeezebox\server\Slim\Plugin\MusicMagic\str ings.txt
[10-01-05 08:51:54.4610] Slim::Utils::Strings::loadStrings (178) Loading string file: C:\Program Files\Squeezebox\server\Slim\Plugin\RS232\strings. txt
[10-01-05 08:51:54.4632] Slim::Utils::Strings::loadStrings (185) Storing string cache: C:\Documents and Settings\All Users\Application Data\Squeezebox\Cache\strings.586.bin
[10-01-05 08:51:54.4730] main::init (409) Squeezebox Server SQL init...
[10-01-05 08:51:56.3098] main::init (413) Async DNS init...
[10-01-05 08:51:56.3105] main::init (416) Async HTTP init...
[10-01-05 08:51:56.3117] main::init (420) Firmware init...
[10-01-05 08:51:56.3144] main::init (423) Squeezebox Server Info init...
[10-01-05 08:52:01.7677] main::init (438) Squeezebox Server IR init...
[10-01-05 08:52:01.8042] main::init (441) Squeezebox Server Request init...
[10-01-05 08:52:01.8130] main::init (444) Squeezebox Server Buttons init...
[10-01-05 08:52:01.8208] main::init (452) UDP init...
[10-01-05 08:52:01.8231] Slim::Networking::UDP::init (39) FATAL: There is already another copy of the Squeezebox Server running on this machine. (Unknown error)
[10-01-05 08:52:01.8240] Slim::Utils::Misc::msg (1165) Warning: [08:52:01.8239] FATAL: There is already another copy of the Squeezebox Server running on this machine. (Unknown error) at /<C:\Program Files\Squeezebox\server\SqueezeSvr.exe>Log/Log4perl/Logger.pm line 901
[10-01-05 08:52:01.8250] Slim::bootstrap::theEND (462) Got to the END
[10-01-05 08:52:01.8255] Slim::bootstrap::sigint (426) Got sigint

C:\Program Files\Squeezebox\server>

bpa
2010-01-05, 02:17
As a test to see firewall logging - I unchecked the Windows Firewall entries for port 3483 both TCP & UDP and SBS still booted OK so Windows Firewall will not prevent startup - it just prevents packet coming in from network.

Tom Hutcheson
2010-01-05, 08:48
Hi bpa -

Thanks for staying with this.

There's no log.conf file but I was able to run the "SqueezeSvr.exe --debug server=DEBUG,network.protocol=DEBUG" statement and I posted the output (http://www.scurvydog.us/slimproblem/index.htm).

It's more verbose but ultimately ends abruptly with the Fatal message but I'm hoping that it at least affords you a clue.

Thanks!
Tom



Is there a log.conf file in the prefs directory ?

If so then edit the file using Wordpad and change the following entries - change "ERROR" to "DEBUG"
log4perl.logger.server = ERROR
log4perl.logger.network.protocol = ERROR

If there is no prefs file then when running squeezesvr.exe from the command line use the following after cd to the right directory.

SqueezeSvr.exe --debug server=DEBUG,network.protocol=DEBUG

contrary to help "--debug" gives log message not "--logging".

If the problem is a inaccessible port 3483 then logging will give no additional info but please post the complete log as earlier message may show something. Post the complete log as sometimes missing messages are the symptom.

bpa
2010-01-05, 10:56
In the past after using ZoneAlarm it sometimes messes up the TCP/IP stack. Have you tried the solution in the FAQ
http://www.slimdevices.com/su_faq.html#troubleshooting-anothercopy

If yes then the next thing to try is resetting the Winsock stack.

Tom Hutcheson
2010-01-05, 11:42
bpa -

No I hadn't seen this faq solution but I tried it and still have the exact same failure. Certain things did get reset when I ran it - I posted the reset.log to the ususal place so that you can see it. I then googled about your suggestion to next reset the Winsock stack and ran this command: "netsh winsock reset catalog" - it successfully completed, I rebooted, but SAME ERROR.

Thanks so much for all the ideas. Are you running out of bullets?
Tom



In the past after using ZoneAlarm it sometimes messes up the TCP/IP stack. Have you tried the solution in the FAQ
http://www.slimdevices.com/su_faq.html#troubleshooting-anothercopy

If yes then the next thing to try is resetting the Winsock stack.

Tom Hutcheson
2010-01-05, 12:18
An observation...

Anytime I start the server (either during install or from tray) what I see in task manager is SQUEEZ~3.EXE (there are no other SQUEEZ~ tasks running). On my main machine I see SQUEEZ~1.EXE. Of course the ~3 always ends in the FATAL another copy is running. Does this mean anything?

Tom

bpa
2010-01-05, 13:10
The "3" file is probably the SqueezeSvr.exe and so the "3" name is the MSDOS 8.3 form of the SqueezeSvr.exe name. The names are assigned as the files are created so the "1" and "2" files are the tray or control panel exe.

Only SqueezeSvr.exe (i.e. the "3" file) is the SBS which has the code to open the 3483 UDP port - the other exe are just apps which start, stop and monitor the SqueezeSvr.exe program and so you should only ever get Fatal message whenever "3" is running.

Tom Hutcheson
2010-01-05, 13:22
Understood. But SqueezeTray.exe and squeezeboxcp.exe are listed by name (not in 8.3 mode). It just seems to be the only clue that the server thinks that there could be another version running when there are no other versions running. If you don't think it's significant though ok.

There are no other task manager references and from what I see there are no 3843 udp netstat references indicating that something is using the port. Very strange.


The "3" file is probably the SqueezeSvr.exe and so the "3" name is the MSDOS 8.3 form of the SqueezeSvr.exe name. The names are assigned as the files are created so the "1" and "2" files are the tray or control panel exe.

Only SqueezeSvr.exe (i.e. the "3" file) is the SBS which has the code to open the 3483 UDP port - the other exe are just apps which start, stop and monitor the SqueezeSvr.exe program and so you should only ever get Fatal message whenever "3" is running.

bpa
2010-01-05, 13:24
To be sure what is running install Process Explorer ( http://technet.microsoft.com/en-us/sysinternals/bb896653.aspx )

It is waaaay better than Task Manager and you can ghet the full image path name and the commandline which started the exe.

You might also like TCPview
http://technet.microsoft.com/en-us/sysinternals/bb897437.aspx

bpa
2010-01-05, 13:30
Can you get a log of the output of "netsh winsock show catalog" - this will show if there is any strange s/w installed usually malware or security.

You can probably do something like
netsh winsock show catalog >catalog.txt

Tom Hutcheson
2010-01-05, 13:54
I downloaded both of the utilities. The ProcessViewer shows the squeezesvr.exe pop into existence for about 8 seconds and then die. I also see mysqld.exe starting and ending.

The TCPView shows activity for squeezesvr in the local 1350 range (I think but it moves very fast). I don't see any attempt at 3483 (but maybe I missed it but I don't think so) MySQL entries for 9092.



To be sure what is running install Process Explorer ( http://technet.microsoft.com/en-us/sysinternals/bb896653.aspx )

It is waaaay better than Task Manager and you can ghet the full image path name and the commandline which started the exe.

You might also like TCPview
http://technet.microsoft.com/en-us/sysinternals/bb897437.aspx

bpa
2010-01-05, 14:04
How about the catalog dump ?

Tom Hutcheson
2010-01-05, 14:20
Ooh sorry didn't see you're post. I put it on the web http://www.scurvydog.us/slimproblem/index.htm

It's the Winsock Catalog lsp.txt.


How about the catalog dump ?

bpa
2010-01-05, 14:38
Any idea what app are you using that requires RSVP ? It looks like it has a UDP listener which might be clashing ?

Tom Hutcheson
2010-01-05, 14:42
No I don't know what that is. Is there a way to figure that out?


Any idea what app are you using that requires RSVP ? It looks like it has a UDP listener which might be clashing ?

Tom Hutcheson
2010-01-05, 14:45
There's a screenprint on the bottom of my webpage that shows all the conventional programs that are installed.


Any idea what app are you using that requires RSVP ? It looks like it has a UDP listener which might be clashing ?

bpa
2010-01-05, 14:47
RSVP is when you enable QoS on your TCP/IP interface - is it enabled on your system ? if so did you do it ?

Tom Hutcheson
2010-01-05, 14:54
I don't know what QoS is and don't know how to turn it on.


RSVP is when you enable QoS on your TCP/IP interface - is it enabled on your system ? if so did you do it ?

bpa
2010-01-05, 15:38
RSVP may be a red herring but it is enmabled on your system and I feel it is better to chase it down before doing the "nuclear" option of deleting and re-installing the network interface. If you delete a network interface you have to be confident that you have all the drivers necessary to bring it up again otherwise the PC is left stranded.

RSVP is typically used for media operations so if you have or had Windows MCE installed, RSVP would be enabled.

One place to check is Control Panel/Admin/Services/QoS RSVP - you could try and turn it off or disable it and then see if it makes a difference.

Tom Hutcheson
2010-01-05, 15:42
Unfortunately the service is set to manual and is not running.

Can I tell you again that I appreciate how much you've stayed with this? Well, there I said it. Thanks - really.


RSVP may be a red herring but it is enmabled on your system and I feel it is better to chase it down before doing the "nuclear" option of deleting and re-installing the network interface. If you delete a network interface you have to be confident that you have all the drivers necessary to bring it up again otherwise the PC is left stranded.

RSVP is typically used for media operations so if you have or had Windows MCE installed, RSVP would be enabled.

One place to check is Control Panel/Admin/Services/QoS RSVP - you could try and turn it off or disable it and then see if it makes a difference.

bpa
2010-01-05, 18:16
I don't think it is RSVP as I started the QoS service on my XP system and it made no difference to my SBS. However it is a bit odd that the rsvp dll are in the catalog yet not started as a service.

It's an interesting problem and worthwhile trying to find a solution - your setup seems to be different to the majority of users who get this symptom and it is good that you're willing to spend time to resolve it.

Tom Hutcheson
2010-01-05, 18:54
Well I sure would like to be able to get this machine to run. I mentioned in my initial post that my friend bought herself a Classic for Christmas (after seeing mine for the last 6 years) so I'm working on getting SlimServer installed on her machine (this is her machine we're working on that I've moved to my house for now). I've alerted her to the possibility though that I don't see a light at the end of the tunnel yet and there may be no solution. I'm out of my debugging realm at this point but game and very happy to follow any and all leads you (or anyone) may have for me but at some point even you may be out of ideas. Knowing what you know and what we've seen so far, what are your best thoughts on what's going on? Seeing as how I'm thinking that you think that this is a low-levek software conflict, would you venture to say that if I reformatted the drive and started over that that would handle the issue? Obviously that's extreme and I would like to avoid that but I guess the question is - would it work?

Thanks so much and hoping to hear your ideas-
Tom


I don't think it is RSVP as I started the QoS service on my XP system and it made no difference to my SBS. However it is a bit odd that the rsvp dll are in the catalog yet not started as a service.

It's an interesting problem and worthwhile trying to find a solution - your setup seems to be different to the majority of users who get this symptom and it is good that you're willing to spend time to resolve it.

gizek
2010-01-05, 20:44
If you're so into reformatting. Why not to try install of another instance of clean system. If you have enough space on your HDD, use partition software and go from there.
What about Windows in safe mode ?

mherger
2010-01-05, 23:41
> Anytime I start the server (either during install or from tray) what I
> see in task manager is SQUEEZ~3.EXE (there are no other SQUEEZ~ tasks


That's SqueezeSvr.exe (as of SBS 7.4)

> running). On my main machine I see SQUEEZ~1.EXE.

And this most likely is squeezecenter.exe (SC 7.0-7.3).

I don't know how Windows decides to shorten those names, but that's the schema I've seen.

--

Michael

bpa
2010-01-06, 02:06
Well I sure would like to be able to get this machine to run. I mentioned in my initial post that my friend bought herself a Classic for Christmas (after seeing mine for the last 6 years) so I'm working on getting SlimServer installed on her machine (this is her machine we're working on that I've moved to my house for now). I've alerted her to the possibility though that I don't see a light at the end of the tunnel yet and there may be no solution. I'm out of my debugging realm at this point but game and very happy to follow any and all leads you (or anyone) may have for me but at some point even you may be out of ideas. Knowing what you know and what we've seen so far, what are your best thoughts on what's going on? Seeing as how I'm thinking that you think that this is a low-levek software conflict, would you venture to say that if I reformatted the drive and started over that that would handle the issue? Obviously that's extreme and I would like to avoid that but I guess the question is - would it work?

Thanks so much and hoping to hear your ideas-
Tom

Because your log file looks like your are using a standard English Windows system and the directories look normal, I've made the assumption that the problem is not in SBS or where it is installed and that it just as a result of SBS trying to do is open a port.

I've spent time on some Slimserver problems where supporting app socketwrapper was prevented from running by various security s/w, malware and corrupted installations so I'm drawing on this knowledge.

This problem is odd in that AFAICT internet usage is OK except for trying to open a UDP port. The actual code is


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

) or do {

# XXX - exiting in a deep sub is kinda bad. should propagate up.
logger('')->logdie("FATAL: There is already another copy of the Squeezebox Server running on this machine. ($!)");
};


It is important to try and identify theproblem because if it is because of a software settings or another s/w package rather than some sort of corruption, then after reformatting the problem is likely to recur.

However, you're right that we should try to resolve the issue even if it means the problem is not identified and taking drastic action such as a reformat & reinstall.

I suggest that bring the issue to a close by this evening with the following steps.

1. Test that IP address is OK by running these commands and copy logged output. The first one should fail but the log output might be interesting. The second one needs the actual IP address of the PC (something like 192.168.1.120) - use ipconfig if necessary
SqueezeSvr.exe --debug server=DEBUG,network.protocol=DEBUG --playeraddr=127.0.0.2
SqueezeSvr.exe --debug server=DEBUG,network.protocol=DEBUG --playeraddr=PCIPADDR

These might test the possibility of the hosts file being corrupted.

2. Run LSPFix (found here http://www.cexx.org/lspfix.htm ) - to stop LSPFix you use the "close window x" in top right. Report list shown by LSPFix - I don't expect it to show anything new as Windows "netsh reset Winsock" more or less does the same thing.
3. Assuming you are confident that either you have Windows disks or Windows drivers are already on harddrive, delete all the network interface and re-install.
4. If all else fails - reinstall Windows. Get SBS working as part of early packages (e.g. after standard Windows apps) and then install other user preferred packages.

Tom Hutcheson
2010-01-06, 07:27
Thanks for the analysis - this sounds like a plan. I need to be away for about three hours but will execute these steps when I return. I'm also very glad that you were able to take a peek at the code as there's no substitute for what the code actually says.



Because your log file looks like your are using a standard English Windows system and the directories look normal, I've made the assumption that the problem is not in SBS or where it is installed and that it just as a result of SBS trying to do is open a port.

I've spent time on some Slimserver problems where supporting app socketwrapper was prevented from running by various security s/w, malware and corrupted installations so I'm drawing on this knowledge.

This problem is odd in that AFAICT internet usage is OK except for trying to open a UDP port. The actual code is


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

) or do {

# XXX - exiting in a deep sub is kinda bad. should propagate up.
logger('')->logdie("FATAL: There is already another copy of the Squeezebox Server running on this machine. ($!)");
};


It is important to try and identify theproblem because if it is because of a software settings or another s/w package rather than some sort of corruption, then after reformatting the problem is likely to recur.

However, you're right that we should try to resolve the issue even if it means the problem is not identified and taking drastic action such as a reformat & reinstall.

I suggest that bring the issue to a close by this evening with the following steps.

1. Test that IP address is OK by running these commands and copy logged output. The first one should fail but the log output might be interesting. The second one needs the actual IP address of the PC (something like 192.168.1.120) - use ipconfig if necessary
SqueezeSvr.exe --debug server=DEBUG,network.protocol=DEBUG --playeraddr=127.0.0.2
SqueezeSvr.exe --debug server=DEBUG,network.protocol=DEBUG --playeraddr=PCIPADDR

These might test the possibility of the hosts file being corrupted.

2. Run LSPFix (found here http://www.cexx.org/lspfix.htm ) - to stop LSPFix you use the "close window x" in top right. Report list shown by LSPFix - I don't expect it to show anything new as Windows "netsh reset Winsock" more or less does the same thing.
3. Assuming you are confident that either you have Windows disks or Windows drivers are already on harddrive, delete all the network interface and re-install.
4. If all else fails - reinstall Windows. Get SBS working as part of early packages (e.g. after standard Windows apps) and then install other user preferred packages.

Tom Hutcheson
2010-01-06, 07:31
Not so into reformatting just looking for solution. You may be right but it seems to me that while partitioning may be helpful it may not be definitive. I think I would need to save off all valuable data first anyway before a partition attempt and that would be half the battle anyway. Thanks.


If you're so into reformatting. Why not to try install of another instance of clean system. If you have enough space on your HDD, use partition software and go from there.
What about Windows in safe mode ?

Tom Hutcheson
2010-01-06, 07:35
Windows just being Windows, huh? I copied and renamed the exe to SlimTom.exe and that showed up correctly (of course it's less that < 8.3 anyway) but it failed with same message. Thanks.


> Anytime I start the server (either during install or from tray) what I
> see in task manager is SQUEEZ~3.EXE (there are no other SQUEEZ~ tasks


That's SqueezeSvr.exe (as of SBS 7.4)

> running). On my main machine I see SQUEEZ~1.EXE.

And this most likely is squeezecenter.exe (SC 7.0-7.3).

I don't know how Windows decides to shorten those names, but that's the schema I've seen.

--

Michael

bpa
2010-01-06, 07:51
I don't know how Windows decides to shorten those names, but that's the schema I've seen.

See
http://support.microsoft.com/kb/142982

If you have a command prompt window open and have CD to the directory - use "dir /X" this will show long filename and short filename together for each file in the directory.

Tom Hutcheson
2010-01-06, 12:31
I ran the two debug statements and the LSFix - still in the same boat. The server failed with the same erro both times. The LSFix shows no problems. According to your prior post the next recommendation is to delete all the network interface and re-install. I've never done that before and wonder if you could just clarify how / where I'm doing that (I can google steps but I want to be sure I'm doing what you recommend). OH - I posted the logs and the LSFix screenprint to http://www.scurvydog.us/slimproblem/index.htm. Thansk again.


1. Test that IP address is OK by running these commands and copy logged output. The first one should fail but the log output might be interesting. The second one needs the actual IP address of the PC (something like 192.168.1.120) - use ipconfig if necessary
SqueezeSvr.exe --debug server=DEBUG,network.protocol=DEBUG --playeraddr=127.0.0.2
SqueezeSvr.exe --debug server=DEBUG,network.protocol=DEBUG --playeraddr=PCIPADDR

These might test the possibility of the hosts file being corrupted.

2. Run LSPFix (found here http://www.cexx.org/lspfix.htm ) - to stop LSPFix you use the "close window x" in top right. Report list shown by LSPFix - I don't expect it to show anything new as Windows "netsh reset Winsock" more or less does the same thing.
3. Assuming you are confident that either you have Windows disks or Windows drivers are already on harddrive, delete all the network interface and re-install.
4. If all else fails - reinstall Windows. Get SBS working as part of early packages (e.g. after standard Windows apps) and then install other user preferred packages.

bpa
2010-01-06, 12:42
The run with the test with 127.0.0.2 should have had extra messages about 127.0.0.2 not being valid and then trying with 127.0.0.1.

Not sure what it means but it may indicate a more serious problem which means deleting the interface looks like the right strategy.

I'll check up on exactly needs to be done to delete the interface. Due to bad weather here - I'm can't get back to this for about 2 hrs.

Tom Hutcheson
2010-01-06, 12:55
Sorry I screwed up then. I ran the first with the correct loacl address but I ran the second just as the line said. I will rerun as 127.... and repost.


The run with the test with 127.0.0.2 should have had extra messages about 127.0.0.2 not being valid and then trying with 127.0.0.1.

Not sure what it means but it may indicate a more serious problem which means deleting the interface looks like the right strategy.

I'll check up on exactly needs to be done to delete the interface. Due to bad weather here - I'm can't get back to this for about 2 hrs.

Tom Hutcheson
2010-01-06, 13:09
Sorry about that. I reread what you had written and reran the debugs and reposted the results. The 127.0.0.2 has a message "Warning: Couldn't call connect() - falling back to 127.0.0.1" whick sounds like what you may have expected. Thanks.

Tom



Sorry I screwed up then. I ran the first with the correct loacl address but I ran the second just as the line said. I will rerun as 127.... and repost.

bpa
2010-01-06, 15:58
OK - thanks for that update - at least the problem is still well defined.

The only way I can see of removing an interface is via Control Panel / System/ Device Manager/Network Adapter

Select the interface and then right-click uninstall.

Then reboot PC and Windows should find the unused network interface and ask to reinstall drivers and TCP etc.

Read below before doing the uninstall.

If it is a relatively new PC then Windows drivers etc are probably on the hard drive - if it is old then a separate Windows XP CD may be necessary to install the drivers.

Before doing this make sure you note the TCP/IP interface details such as Use DHCP or not, IP address, gateway, mask and DNS in case these need to be entered by hand.

Tom Hutcheson
2010-01-06, 16:28
Still the same error. The machine is a couple of years old and my friend assures me that she has the disks (even though I don't have them yet). But I felt pretty sure that Dell has their drivers out there on the drive so I proceeded and uninstalled the network adaptor vis device manager and rebooted. Sure enough Windows detected new hardware and reinstalled drivers. I'm using dns on this machine and I guess the tcp/ip properties just default to that anyway (hardwired to router). I should mention that I've been getting the same Fatal error both on my wired ethernet as well as originally at my friend's house on her wireless adaptor. Thanks.


OK - thanks for that update - at least the problem is still well defined.

The only way I can see of removing an interface is via Control Panel / System/ Device Manager/Network Adapter

Select the interface and then right-click uninstall.

Then reboot PC and Windows should find the unused network interface and ask to reinstall drivers and TCP etc.

Read below before doing the uninstall.

If it is a relatively new PC then Windows drivers etc are probably on the hard drive - if it is old then a separate Windows XP CD may be necessary to install the drivers.

Before doing this make sure you note the TCP/IP interface details such as Use DHCP or not, IP address, gateway, mask and DNS in case these need to be entered by hand.

bpa
2010-01-06, 16:35
I should mention that I've been getting the same Fatal error both on my wired ethernet as well as originally at my friend's house on her wireless adaptor.


The fact that it is happening on a number of different system make me believe there is a simpler explanation to this problem.

Tom Hutcheson
2010-01-06, 16:40
What I mean is this same Vostro desktop originally had the same fatal error at her house (wireless network) and then I've now taken the machine home to my house to figure this out (wired).


The fact that it is happening on a number of different system make me believe there is a simpler explanation to this problem.

bpa
2010-01-06, 17:10
OK - only one system just different places and interfaces - that's better.

Getting a bit desperate now.

The Windows Firewall is mainly aimed at blocking incoming connections.

The Firewall will also block outgoing comms from any application that is not in the exception list. In your logs I don't see SqueezeSvr.exe or SqueezeCp.exe in the exceptions list. It may be worth trying adding these apps as Program to Firewall Exceptions list.

What model router is being used ?
Is it the same model used in different locations ?

Tom Hutcheson
2010-01-06, 17:23
I set these exceptions in Windows Firewall on the machine in question but same error.

My main machine (a Dell Vostro 220s) runs SlimServer 7.3.1 and is wired to same router. Since experiencing this problem I have subsequently installed 7.4.1 on two other machines in my house without issue (same router but both of them wireless). When I was at my friend's house last week I installed 7.4.1 on her daughter's laptop without issue (same wireless network as the unsuccessful desktop). We both have Linksys routers but different models.



OK - only one system just different places and interfaces - that's better.

Getting a bit desperate now.

The Windows Firewall is mainly aimed at blocking incoming connections.

The Firewall will also block outgoing comms from any application that is not in the exception list. In your logs I don't see SqueezeSvr.exe or SqueezeCp.exe in the exceptions list. It may be worth trying adding these apps as Program to Firewall Exceptions list.

What model router is being used ?
Is it the same model used in different locations ?

bpa
2010-01-06, 17:45
I only just noticed that NWLink/IPX/SPX/NetBIOS is installed on interface of the problem system.

Any reason for this ?
Do the other systems which work have these protocols installed ?

Tom Hutcheson
2010-01-06, 17:49
Sorry - where do I look to confirm that?


I only just noticed that NWLink/IPX/SPX/NetBIOS is installed on interface of the problem system.

Any reason for this ?
Do the other systems which work have these protocols installed ?

bpa
2010-01-06, 17:52
Open Network Connections
Right click the interface and select Properties and you should see an line with this in the scroll box which has "Client for Microsoft Networks".

I noticed the entry from the output of LspFix.

Tom Hutcheson
2010-01-06, 17:59
My main guy has these: Client for MS, Virtual Machine Network Services, File & Print Sharing, QoS packet scheduler, Realtek VLAN Intermediate, Realtek VLAN Protocol, TCP/IP. Fatal machine has Client for MS, File & Print Sharing, QoS packet scheduler, AEGIS Protocol, TCP/IP (of course this is after the uninstall / reinstall). I could rerun the LSPFix on both machines if you need it.



Open Network Connections
Right click the interface and select Properties and you should see an line with this in the scroll box which has "Client for Microsoft Networks".

I noticed the entry from the output of LspFix.

Tom Hutcheson
2010-01-06, 18:11
I ran an LSPFix on my good machine and it does not have the same protocols. I posted the results (http://www.scurvydog.us/slimproblem/index.htm).


I only just noticed that NWLink/IPX/SPX/NetBIOS is installed on interface of the problem system.

Any reason for this ?
Do the other systems which work have these protocols installed ?

bpa
2010-01-06, 18:14
I think NWLInk/IPX/SPX/NetBIOS could be removed using LspFix as it should also appear in the Properties scroll box even if it is unchecked but I'm not sure as it could be part of Print & File sharing - IIRC there is a choice for protocol.

NWLink, IPX and SPX relate to Novell Netware. These are old protocols but sometimes people use these and NetBIOS for Windows workgroups. IS the PC part of a workgroup ?

Tom Hutcheson
2010-01-06, 18:16
No it's not. Shall I remove it and retry install?


I think NWLInk/IPX/SPX/NetBIOS could be removed using LspFix as it should also appear in the Properties scroll box even if it is unchecked but I'm not sure as it could be part of Print & File sharing - IIRC there is a choice for protocol.

NWLink, IPX and SPX relate to Novell Netware. These are old protocols but sometimes people use these and NetBIOS for Windows workgroups. IS the PC part of a workgroup ?

bpa
2010-01-06, 18:29
I think remove using LspFix and then reboot.

If printing or Filesharing fails - then uninstall and reinstall that component.

Tom Hutcheson
2010-01-06, 18:36
Still same fatal error. I removed using LSPFix, rebooted, and then reran LSPFix and the reference is gone.

Have you ever seen an instance like this where the server could not be installed?



I think remove using LspFix and then reboot.

If printing or Filesharing fails - then uninstall and reinstall that component.

bpa
2010-01-06, 18:52
I've seen users report this problem but usually it is solved.

I can't do much more tonight but I just googled "IO::Socket::INET unknown error" and I got this reference http://www.experts-exchange.com/Programming/Languages/Scripting/Perl/Q_23741539.html which looks like a similar problem but to test you would need to install ActiveState Perl so that the source code can be changed.

This file has the suggested fix but I haven't had time to check it out: http://filedb.experts-exchange.com/incoming/2008/09_w38/60765/Proxy.txt

Tom Hutcheson
2010-01-06, 18:54
I'll take a look - thanks a lot.


I've seen users report this problem but usually it is solved.

I can't do much more tonight but I just googled "IO::Socket::INET unknown error" and I got this reference http://www.experts-exchange.com/Programming/Languages/Scripting/Perl/Q_23741539.html which looks like a similar problem but to test you would need to install ActiveState Perl so that the source code can be changed.

This file has the suggested fix but I haven't had time to check it out: http://filedb.experts-exchange.com/incoming/2008/09_w38/60765/Proxy.txt

bpa
2010-01-07, 02:45
I don't think the suggested fix is applicable to your problem. However it did show up a bug in error handling in Perl on Windows so that I think with a small code change we can get a real error message and not the "unknown error".

The real error message may also give a better idea as to the cause of the failure but code change will require ActiveState Perl to be installed. I'll come back with details - if I can get better error message from my Windows systems.

Tom Hutcheson
2010-01-07, 07:21
That sounds great. The existing message is not very helpful. I downloaded ActiveState Perl and also I acquired the Dell rebuild disks. Thanks.


I don't think the suggested fix is applicable to your problem. However it did show up a bug in error handling in Perl on Windows so that I think with a small code change we can get a real error message and not the "unknown error".

The real error message may also give a better idea as to the cause of the failure but code change will require ActiveState Perl to be installed. I'll come back with details - if I can get better error message from my Windows systems.

bpa
2010-01-07, 07:56
Getting SBS running from source code using ActiveState is a bit ocmplex so first try with just the UDP opening port code as I think that is all that matters.

Attached is a simple Perl file - download and rename to testudp.pm. Once Activestate Perl is installed, to run just type at a command prompt
perl testudp.pm

Can you also dump the contents of the "services" and "hosts" file in \Windows\system32\drivers\etc

Tom Hutcheson
2010-01-07, 08:35
The perl script ran and result was "Success: Opened UDP port". There are no Windows\system32\drivers\etc entries except for a hosts.ics which contains only comments). On my main machine my hosts file is empty (comments only) but I have a services file with many entries. My machine is XPPro - fatal machine is XPHome.


Getting SBS running from source code using ActiveState is a bit ocmplex so first try with just the UDP opening port code as I think that is all that matters.

Attached is a simple Perl file - download and rename to testudp.pm. Once Activestate Perl is installed, to run just type at a command prompt
perl testudp.pm

Can you also dump the contents of the "services" and "hosts" file in \Windows\system32\drivers\etc

bpa
2010-01-07, 09:05
Interesting about no hosts file.

I made one change from the SBS source code as it was the only way I could reproduce SBS behaviour on my PC. I'd like you to try two different code changes and see if the "FATAL" error message appears.



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


Can you edit (e.g. use Notepad or Wordpad) testudp.pm and make the following changes to the line in red
1. remove the leading "#", save the file and try running testudp.pm
2. Now change 127.0.0.1 to localhost, save the file and rerun.

Tom Hutcheson
2010-01-07, 09:15
All 3 tests show the same "Success: Opened UDP port". Aside from making the changes as you specifed and resaving was there any other reinitialization required?


Interesting about no hosts file.

I made one change from the SBS source code as it was the only way I could reproduce SBS behaviour on my PC. I'd like you to try two different code changes and see if the "FATAL" error message appears.



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


Can you edit (e.g. use Notepad or Wordpad) testudp.pm and make the following changes to the line in red
1. remove the leading "#", save the file and try running testudp.pm
2. Now change 127.0.0.1 to localhost, save the file and rerun.

bpa
2010-01-07, 09:32
Sigh - it looks like it may be necessary to get SBS running with ActiveState. This has got more complicated with 7.4 and I haven't tried it but the starting point would be the instructions here http://wiki.slimdevices.com/index.php/InstallSVNTrunkAsService

It were last updated in Nov 2009 by ralphy so I think it is probably correct or very close. Not all the steps are necessary for our test (i.e. no need for SVN or registry changes). I won't be able to test this out to get a shortened version (i.e. no svn, no registry changes, no srvany etc) for our test until later this evening.

Once a standard SBS is running - then a change can be made to get the proper error message displayed.

Tom Hutcheson
2010-01-07, 10:02
First - thanks for all your hard work, bpa.

You mention that the process is more complicated with 7.4 - I get the same fatal error with 7.3.1 - does that matter how you think about this?

I don't know perl and obviously have never installed the environment but after looking I'm comfortable with most things I see there (including reg stuff and srvany) as long as the instructions actually work. Of course that only recreates the environment and I would have no idea about actual debugging.

Did it give you any new clues the fact that the port opened successfully in the small debug tests? Is it starting to look possible that the execution is dropping through some code unexpectedly and hitting this error?

Thanks -
Tom


Sigh - it looks like it may be necessary to get SBS running with ActiveState. This has got more complicated with 7.4 and I haven't tried it but the starting point would be the instructions here http://wiki.slimdevices.com/index.php/InstallSVNTrunkAsService

It were last updated in Nov 2009 by ralphy so I think it is probably correct or very close. Not all the steps are necessary for our test (i.e. no need for SVN or registry changes). I won't be able to test this out to get a shortened version (i.e. no svn, no registry changes, no srvany etc) for our test until later this evening.

Once a standard SBS is running - then a change can be made to get the proper error message displayed.

bpa
2010-01-07, 10:10
Did it give you any new clues the fact that the port opened successfully in the small debug tests? Is it starting to look possible that the execution is dropping through some code unexpectedly and hitting this error?


I don't think the code is doing something odd by falling through - I think the Open port parameters may trigger a strange response as LocalAddr is not setup normally (but is when using --playeraddr) but I can't be sure until the error code is shown.

Tom Hutcheson
2010-01-07, 14:10
bpa -

Good news I think (or at least progress?).

I followed the instructions you pointed me to to InstallSVNTrunkAsService and was able to launch the http://localhost:9000 page and see whatever music she has loaded in her itunes folder.

Not exactly sure what this means but I know you will know. Will post the netstats soon.

Thanks -
Tom


Sigh - it looks like it may be necessary to get SBS running with ActiveState. This has got more complicated with 7.4 and I haven't tried it but the starting point would be the instructions here http://wiki.slimdevices.com/index.php/InstallSVNTrunkAsService

It were last updated in Nov 2009 by ralphy so I think it is probably correct or very close. Not all the steps are necessary for our test (i.e. no need for SVN or registry changes). I won't be able to test this out to get a shortened version (i.e. no svn, no registry changes, no srvany etc) for our test until later this evening.

Once a standard SBS is running - then a change can be made to get the proper error message displayed.

snarlydwarf
2010-01-07, 14:16
bpa -

Good news I think (or at least progress?).

I followed the instructions you pointed me to to InstallSVNTrunkAsService and was able to launch the http://localhost:9000 page and see whatever music she has loaded in her itunes folder.

Not exactly sure what this means but I know you will know. Will post the netstats soon.


Oooh, so your SVN checkout worked, but the stock pre-compiled download didn't?

I wonder if there is some odd DLL conflict which is seen with the compiled version and 'something' else on your machine... but not with the perl.exe dll's.

What a mystery, I applaud you, sir, in your investigation of this.

Tom Hutcheson
2010-01-07, 14:22
bpa -

You're applauding the wrong person. I would've quit (reluctantly in desperation several days ago.

To my point - so what does that mean and what do I do now?

Tom :-)



Oooh, so your SVN checkout worked, but the stock pre-compiled download didn't?

I wonder if there is some odd DLL conflict which is seen with the compiled version and 'something' else on your machine... but not with the perl.exe dll's.

What a mystery, I applaud you, sir, in your investigation of this.

Tom Hutcheson
2010-01-07, 14:28
SnarlyDwarf - my reply should've been directed to you. Thanks but I just really needed to get Slim (old habit - still call it Slim) running for my friend. The Community (large applause for bpa) got things turned around.


bpa -

You're applauding the wrong person. I would've quit (reluctantly in desperation several days ago.

To my point - so what does that mean and what do I do now?

Tom :-)

bpa
2010-01-07, 14:47
Mutual backslapping all round - solving problems like this need a determined user as much as somebody to offer suggestions to test.

Strangely, I have not been able to get a tarball version of 7.4.1 to run on my test Windows systems which is now Vista.

I think Snarlydwarf might have the right idea that somehting is bundled in the SqueezeSvr.exe that clashes with the target system as SqueezeSvr.exe is some sort of compressed file with perl.exe, libraries and precompiled SBS source.

You now have a workaround but the underlying problem is not really solved. So what to do next ? I think check ActiveState forums to see if another user has a similar symptom and also possibly using Process Explorer on a good running SBS to see what DLLs are being used.

bpa
2010-01-07, 16:41
The possibility of library files causing a problem made me recall an old problem about the temporary files that are created when SqueezeSvr.exe is run and sometimes old version was installed.

You check in \Documents and Settings\YOURUSERNAME\Local Settings\Temp for directories that begin "par-" and "pdk-" . If there is more than one "pdk-" then old directories are being kept. I think all the "par-" and "pdk-" should be deleted, expunged and PC rebooted.

Tom Hutcheson
2010-01-07, 17:11
Good thought but I didn't find any at all (I eyeballed but I also use "Everything Search" and searched all of Docs and Settings).

I hooked up a Classic and it was good to hear some music but I don't think that I can leave the machine with this setup (it might be ok if it were mine) but too much could go wrong sometime in the future and then I (she) would be back to square one. I realize we've pushed the ball farther down the field and I know there's no right answer still about where a solution may lie but I again need to assess what the options are at this point. I know (now) that SlimServer can run on this machine. What do you recommend?

Tom



The possibility of library files causing a problem made me recall an old problem about the temporary files that are created when SqueezeSvr.exe is run and sometimes old version was installed.

You check in \Documents and Settings\YOURUSERNAME\Local Settings\Temp for directories that begin "par-" and "pdk-" . If there is more than one "pdk-" then old directories are being kept. I think all the "par-" and "pdk-" should be deleted, expunged and PC rebooted.

bpa
2010-01-07, 17:53
I agree, this is not the most satisfactory way to run SBS mainly because it would be hard to keep up to date.

The fact the script version runs but the executable fails makes it likely to be a problem with how the exe was built or possibly even the ActiveState apps rather than SBS code.

I found no similar reports in ActiveState forums so I think the problem is either
(i) how the SqueezeSvr.exe is decompressed and run
(ii) some support library clash or mismatch.

For (i) - If SqueezeSvr.exe runs OK then there should be one "pdk-*" directory - if there is no pdk directory then I would look for some sort of permission issue preventing file writing of the directory.

For (ii) - since SqueezeSvr.exe doesn't run - it is necessary to look at what DLLs are used by SqueezeSvr.exe on a similar XP system and then check versions on the "faulty" system. One way is to use Process Explorer and open the lower Pane and from the menu select DLLs to be shown in lower pane.

Tom Hutcheson
2010-01-07, 19:23
Thanks for your analysis as always. I investigated a bit more what you said about the pdk's ("there should be one "pdk-*" directory - if there is no pdk directory then I would look for some sort of permission issue preventing file writing of the directory"). I have them on my main server but no trace on the fatal machine. The OS is XP Home and it doesn't really support folder permissions from what I can tell (at least not like XPPro). I did though for goofs share the main user folder on the network (share folder / and / allow network users to change files) and I got a couple of pdk's. That seemed promising so I went through various iterations of uninstall and install but am still getting the fatal message. I also shared the allusers/applicationdata folder and post-install the pf/squeeze folder but same result. So while permissions still seem a potential I don't know what else I can give (I had tried the other day to create and run under a new admin account and different default location but to no avail). Possibility (ii) is still a possibility but I'm afraid that that's like looking for a needle in a haystack. Am back to considering blowing away the drive and reinstalling windows tomorrow (XPPro if I can find a legit copy but XPHome again if not - I have disks for that). I've saved off all personal folders already. Obviously I don't want to do this for the heck of it - what do you think about that? If SlimServer won't run after that then I don't think it ever will.

Thanks -
Tom





I agree, this is not the most satisfactory way to run SBS mainly because it would be hard to keep up to date.

The fact the script version runs but the executable fails makes it likely to be a problem with how the exe was built or possibly even the ActiveState apps rather than SBS code.

I found no similar reports in ActiveState forums so I think the problem is either
(i) how the SqueezeSvr.exe is decompressed and run
(ii) some support library clash or mismatch.

For (i) - If SqueezeSvr.exe runs OK then there should be one "pdk-*" directory - if there is no pdk directory then I would look for some sort of permission issue preventing file writing of the directory.

For (ii) - since SqueezeSvr.exe doesn't run - it is necessary to look at what DLLs are used by SqueezeSvr.exe on a similar XP system and then check versions on the "faulty" system. One way is to use Process Explorer and open the lower Pane and from the menu select DLLs to be shown in lower pane.

Tom Hutcheson
2010-01-08, 15:07
Backslapping and beerdrinking - drinks around for everyone in the world!

Got a late start today but reformatted the drive, installed XPPro, took all the Windows updates, installed Revo Uninstaller, then SlimServer 7.4.1.

Installed like in my dreams (as I expected when the saga began). I do regret that after all that time that ultimately there is no root cause but my friend was starting to miss her computer.

I'll raise a glass tonight to Sean and Dean, their corporate descendents, the loyal community, and especially bpa (man - can't thank you enough - you went above and beyond the call).

Yeah, yeah, yeah (that's the music playing)
Tom

bpa
2010-01-08, 16:11
I've had that sort of Windows fault before - where after years of operation, the accumulated crud of multiple installs, uninstall and updates seems to end up with a mixed up systems - this is verified by a clean install.

I think you have characterised the problem - it was some sort of Windows problem which is probably unreproducible.

However I will file a bug report to get the SBS code changed to fix the "unknown error" bug and produce a proper error message.

Tom Hutcheson
2010-01-08, 16:21
Hey man -

You spent almost as much time on my problem as I did. Thanks so much. I'd like to send you a couple of beers. What's the best way to do that - can I email you off list?

You taught me a few things to boot.

Tom




I've had that sort of Windows fault before - where after years of operation, the accumulated crud of multiple installs, uninstall and updates seems to end up with a mixed up systems - this is verified by a clean install.

I think you have characterised the problem - it was some sort of Windows problem which is probably unreproducible.

However I will file a bug report to get the SBS code changed to fix the "unknown error" bug and produce a proper error message.