Squeezebox Server 7.5 is giving me some issues.

Yesterday I installed 7.5, upgrading from 7.3.3 . All went well, apparently, and both my Squeezebox Boom and Squeezebox Classic worked well for hours.

Today I had to reboot my music server (Windows Server 2003, 32bits) and when reboot was completed I noticed that none of my players were finding/connecting to the squeezebox server.

On my server machine, I see that Squeezebox Server service stops immediately after starting, and this is the error message I am getting:




So, I can't understand how can another copy of the SBS be running on the machine. There is no task running named squeezesvr.exe in the task list. Service is stopped. The SBS control panel also tells me that the service is stopped.

What is that SBS is looking at to decide there's another copy running? Some flag file on the HDD, maybe?

Since it's reporting the error in "Networking::UDP::init", I bet some other process already has a port open that Slimserver wants. Uh, if it were a Unix machine, I'd use lsof to find that program; I think one of the Sysinternals tools will map network connections back to the program that opened them. Alternately, you could try just changing Slimserver's port. (I think you can do that.)

Also, it's not SBS that's preventing it from running. It's the application itself that is bailing out.

I agree that it's likely to be a port conflict and I'm sure one of the Sysinternals tools (now MS) will tell which one it is.

Thank you Bitt. Good point. I overlooked ht UDP part.

NETSTAT -O will tell you what process is owning what port. But I can't figure out what porit SBS wants, instead. I know the HTTP interface will use port 9000, and that is free. I don;t know instead what port is being used by SBS to connect to the players.

Also, what has changed in terms of ports from 7.3.3?

And, I can't find where to change SBS port...

I think the problem is with MS-SQL running on my sever and MySQL that comes with SBS. I am guessing that SBS tries to connect to MYSQL, and it finds instead MS-SQL. At least, TCPView (Sysinternals) seems to show that a connection between SBS and MSSQL is attmpted and soon after SBS stops again...

Does it make sense to you?

FOUND IT!

Here is a Microsoft Knowledge Base:
http://support.microsoft.com/default.aspx?scid=kb;en-us;299357

The TCP/IP protocol of Windows Server was messed up and needed to be reset.

"NETSH int ip reset c:\path\resetlog.txt"
and a REBOOT.

Squeezebox Server is now running again.

It HAD to be something deeper than just a cfg issue... I never needed to reset the TCPIP in Win Server before. But, this may even explain one more strange thing I was experiencing with AV in Exchange not being able to update after reboot, in several occasions...

Ok, hopefully this is useful for somebody else.

.. and now, an unrelated question:

is there a portable player (Zune or IPod style) that syncs with Squeezebox server and copies on local memory your music?

Not* that I'm aware of.

By why would you need it to get its data from Squeezebox Server ? All the data in Squeezebox Server comes from the tags in the music files, so I don't see what benefit you'd get compared to just syncing with the music files themselves.


* actually that isn't quite true, I believe there is an Android app that as well as controlling Squeezeboxes can also download music files from Squeezebox Server to the Android device

I was mostly curious of wether that had been attempted.

Also, what do you mean by "just synching with the music files themselves?"

I was actually thinking of a competing solution to the Zune / Ipod-Itunes packages, where the PC-based software component could be Squeezebox Server and the portable device... the one that maybe does not exist. I could not find any such thing either.