PDA

View Full Version : Installed 6.5 and now nothing works...



David Lawrence
2006-11-30, 04:12
I installed 6.5 on XP/SP2 and everything stopped working.

If I run slim from CMD I get:

Canít set up the listening port 9000 for the HTTP server: unknown error at PerlApp/Slim/Web/HTTP.pm line 170

If I start the slimserver service manually from system management it simply opens and shuts down.

Looking at the localhost page with the browser, all I get is:

.NETŃSystem.Runtime.Remoting.RemotingExce ption: Tcp channel protocol violation: expecting preamble. at System.Runtime.Remoting.Channels.Tcp.TcpSocketHand ler.ReadVersionAndOperation(UInt16& operation) at System.Runtime.Remoting.Channels.Tcp.TcpServerSock etHandler.ReadHeaders() at System.Runtime.Remoting.Channels.Tcp.TcpServerTran sportSink.ServiceRequest(Object state) at System.Runtime.Remoting.Channels.SocketHandler.Pro cessRequestNow()

McAfee installed but all turned off - no difference in behaviour.

Any advice appreciated - musicless home at the present.

David L

ceejay
2006-11-30, 04:24
Start by completely removing any old slimserver installations.

Then get the 6.5.1 nightly (not 6.5.0) and install. Don't install any plugins to start with.

Only when this works, go and get updated versions of any plugins you use and then install them.

If it doesn't work, ask again here...

HTH
Ceejay

David Lawrence
2006-11-30, 05:27
Thanks for the reply.

I'm afraid I've uninstalled multiple times, the current version I have installed is 6.5.1 and as far as I know, I don't have any plug-ins at all.

David L

mherger
2006-11-30, 06:02
> I'm afraid I've uninstalled multiple times, the current version I have
> installed is 6.5.1 and as far as I know, I don't have any plug-ins at
> all.

I guess you have something else listening on port 9000. The message you
get when connecting on that port contains quite some information about
..Net stuff.

To be sure shutdown everything slimserver related, open a DOS box (command
window) and run "netstat -b" and see if there's anything in the list with
:9000 at the end.

--

Michael

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

David Lawrence
2006-11-30, 08:55
Sorry about the length of this but I don't know enough to understand whiat is important.


If I close slimserver down I get:

Proto Local Address Foreign Address State PID
TCP DELL2006:1174 localhost:1175 ESTABLISHED 4480
[MsnMsgr.Exe]

TCP DELL2006:1175 localhost:1174 ESTABLISHED 1864
[mcproxy.exe]

TCP DELL2006:2540 localhost:2541 ESTABLISHED 4704
[FolderShare.exe]

TCP DELL2006:2541 localhost:2540 ESTABLISHED 1864
[mcproxy.exe]

TCP DELL2006:2670 localhost:2671 ESTABLISHED 6044
[iexplore.exe]

TCP DELL2006:2671 localhost:2670 ESTABLISHED 1864
[mcproxy.exe]

TCP DELL2006:2673 localhost:2674 ESTABLISHED 6044
[iexplore.exe]

TCP DELL2006:2674 localhost:2673 ESTABLISHED 1864
[mcproxy.exe]

TCP DELL2006:1176 by1msg2145213.phx.gbl:1863 ESTABLISHED 1864
[mcproxy.exe]

TCP DELL2006:2542 216-166-75-16.fwd.datafoundry.com:https ESTABLI
SHED 1864
[mcproxy.exe]

TCP DELL2006:2672 66.102.9.104:http ESTABLISHED 1864
[mcproxy.exe]

TCP DELL2006:2675 66.102.9.147:http ESTABLISHED 1864
[mcproxy.exe]

TCP DELL2006:1168 localhost:1169 CLOSE_WAIT 4548
[GoogleToolbarNotifier.exe]

TCP DELL2006:1136 84.53.135.168:http CLOSE_WAIT 1716
[mcupdmgr.exe]

TCP DELL2006:2680 localhost:2681 TIME_WAIT 0
TCP DELL2006:2683 localhost:2684 TIME_WAIT 0
TCP DELL2006:2682 66.102.9.104:http TIME_WAIT 0

================================================== =======

With slimserver just starting up (before it shuts itself down again) I get

Proto Local Address Foreign Address State PID
TCP DELL2006:1174 localhost:1175 ESTABLISHED 4480
[MsnMsgr.Exe]

TCP DELL2006:1175 localhost:1174 ESTABLISHED 1864
[mcproxy.exe]

TCP DELL2006:2540 localhost:2541 ESTABLISHED 4704
[FolderShare.exe]

TCP DELL2006:2541 localhost:2540 ESTABLISHED 1864
[mcproxy.exe]

TCP DELL2006:2619 localhost:2621 ESTABLISHED 1476
[slim.exe]

TCP DELL2006:2620 localhost:9092 ESTABLISHED 1864
[mcproxy.exe]

TCP DELL2006:2621 localhost:2619 ESTABLISHED 1864
[mcproxy.exe]

TCP DELL2006:9092 localhost:2620 ESTABLISHED 3544
[mysqld.exe]

TCP DELL2006:1176 by1msg2145213.phx.gbl:1863 ESTABLISHED 1864

[mcproxy.exe]

TCP DELL2006:2542 216-166-75-16.fwd.datafoundry.com:https ESTABLI
SHED 1864
[mcproxy.exe]

TCP DELL2006:1168 localhost:1169 CLOSE_WAIT 4548
[GoogleToolbarNotifier.exe]

TCP DELL2006:1136 84.53.135.168:http CLOSE_WAIT 1716
[mcupdmgr.exe]

TCP DELL2006:2570 localhost:2572 TIME_WAIT 0
TCP DELL2006:2571 localhost:1145 TIME_WAIT 0
TCP DELL2006:2573 localhost:2574 TIME_WAIT 0
TCP DELL2006:2576 localhost:2577 TIME_WAIT 0
TCP DELL2006:2579 localhost:2581 TIME_WAIT 0
TCP DELL2006:2580 localhost:9000 TIME_WAIT 0
TCP DELL2006:2584 localhost:2582 TIME_WAIT 0
TCP DELL2006:2585 localhost:2587 TIME_WAIT 0
TCP DELL2006:2588 localhost:2590 TIME_WAIT 0
TCP DELL2006:2591 localhost:2593 TIME_WAIT 0
TCP DELL2006:2595 localhost:2597 TIME_WAIT 0
TCP DELL2006:2600 localhost:2602 TIME_WAIT 0
TCP DELL2006:2601 localhost:1145 TIME_WAIT 0
TCP DELL2006:2607 localhost:2614 TIME_WAIT 0
TCP DELL2006:2609 localhost:2610 TIME_WAIT 0
TCP DELL2006:2612 localhost:2615 TIME_WAIT 0
TCP DELL2006:2613 localhost:9000 TIME_WAIT 0
TCP DELL2006:2616 localhost:2617 TIME_WAIT 0
TCP DELL2006:2622 localhost:2624 TIME_WAIT 0
TCP DELL2006:9000 localhost:2583 TIME_WAIT 0
TCP DELL2006:9092 localhost:2596 TIME_WAIT 0
TCP DELL2006:9092 localhost:2608 TIME_WAIT 0
TCP DELL2006:9092 localhost:2623 TIME_WAIT 0
TCP DELL2006:9092 localhost:2589 TIME_WAIT 0
TCP DELL2006:9092 localhost:2586 TIME_WAIT 0
TCP DELL2006:9092 localhost:2592 TIME_WAIT 0
TCP DELL2006:2575 66.102.9.104:http TIME_WAIT 0
TCP DELL2006:2611 66.102.9.104:http TIME_WAIT 0

Mitch Harding
2006-11-30, 09:33
I believe you need to not just uninstall, but also manually delete the
SlimServer directory (usually C:\Program Files\SlimServer).

When I updated to 6.5 the first time I had a lot of problems until I did the
following:
1) Uninstall SlimServer
2) Manually deleted the directory
3) Rebooted (probably not needed, but in Windows I always feel happier after
a reboot)
4) Install 6.5

Skipping step 2 will cause problems (or did for me anyway, and for others
who've posted here).

On 11/30/06, David Lawrence <
David.Lawrence.2i353z1164889801 (AT) no-mx (DOT) forums.slimdevices.com> wrote:
>
>
> Thanks for the reply.
>
> I'm afraid I've uninstalled multiple times, the current version I have
> installed is 6.5.1 and as far as I know, I don't have any plug-ins at
> all.
>
> David L
>
>
> --
> David Lawrence
> ------------------------------------------------------------------------
> David Lawrence's Profile:
> http://forums.slimdevices.com/member.php?userid=4352
> View this thread: http://forums.slimdevices.com/showthread.php?t=30169
>
>

David Lawrence
2006-11-30, 11:08
OK - I uninstalled, deleted the directory, ran Registry Booster, rebooted, deactivated McAfee virus, system guard, firewall and script protections and finally reinstalled 6.5.1.

Result is exactly the same, I'm afraid. A web page full of (the same) garbage.

My little Slimboxes are sitting there staring at me accusingly.

MrSinatra
2006-11-30, 11:12
one thing i had to do recently was "factory reset" the SB.

unfortunately i forget how, i think u unplug it, plug it back in, and on bootup hold the add button, or brightness, or one of those.

it fixed my issues with getting SS to connect to my SB locally, however i really don't think factory resets should be SOP.

David Lawrence
2006-12-01, 00:03
Thanks but I'm afraid it's not the Squeezeboxes' fault. There simply is no longer a Slimserver for them to contact.

bpa
2006-12-01, 00:53
Are running any uPNP servers such as Twonkyvision, or WMP11 - these can use port 9000 ?

To confirm it is a port 9000 clash - why not start slimserver using a different port with the command line option "--httpport" using say "--httpport 9080"

David Lawrence
2006-12-01, 02:00
That solved it - now running happily on 9079.

One question left - the server now seems to start always on 9079 and I have checked that it is registered in the settings but the web browser interface still opens on 9000. How do I tell it about the change?

David Lawrence
2006-12-01, 04:26
The change of port did the trick for the starting problem but, as other people have noted, the library scanning is a nightmare.

I've reinstalled 6.3.1 - still have to use the new port but I assume thats WMP11 - and everything sems to be fine again.

I'll look forward to installing the new version when it actually works. Still it introduced me to Radiotime, so every cloud has a silver lining.

ejm1385
2007-01-03, 09:03
How is it that you change the port for which SlimServer starts up with? I believe I am having a port 9000 conflict and wish to change it, but I don't know the process for doing so. Thanks.