Bug 6391 - Slimserver server does not start
: Slimserver server does not start
Status: RESOLVED FIXED
Product: Logitech Media Server
Classification: Unclassified
Component: Windows Service
: 6.5.4
: PC Windows Vista
: P2 blocker (vote)
: ---
Assigned To: Unassigned bug - please assign me!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2007-12-17 13:56 UTC by francis deweirdt
Modified: 2007-12-17 14:37 UTC (History)
0 users

See Also:
Category: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description francis deweirdt 2007-12-17 13:56:42 UTC
Have been running Slimserver 6.5.4 without a glitch on XP SP2 for about 3 weeks now.
When installing Vista on a new Dell for a friend , I decided to give it a try on that OS.
Gave up after a couple of hours - reading and applying all known Vista fixes.
Also disabled all possible interfering programs ( Windows firewall, ZoneAlarm, AVAST antivirus )
From windows services the slim service always appeared "starting", never "running".

Reality is that starting slim.exe from dos box the following error message appears :

15/08/2007  18:24         6.635.605 slim.exe
15/08/2007  18:23            30.708 slimserver.pl
17/12/2007  18:53    <DIR>          SQL
15/08/2007  18:24           682.720 strings.txt
15/08/2007  18:24             3.708 types.conf
              17 bestand(en)       14.111.030 bytes
              14 map(pen)  284.287.488.000 bytes beschikbaar

C:\Program Files\SlimServer\server>slim
2007-12-17 22:44:07.8431 Use of uninitialized value in transliteration (tr///) a
t /<C:\Program Files\SlimServer\server\slim.exe>File/Spec/Win32.pm line 103, <DA
TA> line 164.
2007-12-17 22:44:07.8442 Use of uninitialized value in pattern match (m//) at /<
C:\Program Files\SlimServer\server\slim.exe>File/Spec/Win32.pm line 105, <DATA>
line 164.

Francis Deweirdt
Belgium

PS. Thanks for a very nice product ( at least under XP ) and keep up the good work.
Comment 1 francis deweirdt 2007-12-17 14:37:55 UTC
OOPS - reading the latest postings on the forum someone suggested to uninstall ZoneAlarm - not just shutdown - and
this solved the problem.
You can close this bug report now - sorry for inconvenience.