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

**Tom Hutcheson** · 2010-01-06, 18:16

No it's not. Shall I remove it and retry install?

Originally Posted by bpa

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?

Originally Posted by bpa

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/Prog..._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/i...0765/Proxy.txt

**Tom Hutcheson** · 2010-01-06, 18:54

I'll take a look - thanks a lot.

Originally Posted by bpa

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/Prog..._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/i...0765/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.

Originally Posted by bpa

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.

Originally Posted by bpa

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.

Code:

	$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.

Thread: FATAL: There is already another copy of the SqueezeboxServerrunning on this machine

Thread Tools

Search Thread

Display