LMS 7.7.0 and Windows Server 2003 SP2

[giupemiche]

Hi everybody,
this is my first request (and last one, I hope) in this forum.

My problem is that LMS 7.7 does not start in my Windows Server 2003 SP2 operating system.

These are some notes:

- No error messages during installation
- No active Firewalls
- Net connection ports oing out are OK
- LMS says that there is a software conflict but It gives no details about this.
- Server can't be contacted through 9000 ,38?? and ???? ports (sorry I don't remember correct numbers but probably you know what I mean)
- no "Logitech Media server" in Services.msc list (but I don't know if this is required)

Does anybody have the same problem?

I will appreciate any help.
Thanks very much in advance

Giupemiche

[JPKaro]

Try starting the application as an administrator. Press and hold down the SHIFT key while you right-click the .exe file or icon for the program, and then click Run as.

[sachadog]

I use this system. First of all, did you download the program to your "Home Computer" and not directly to the W.H.S. I don't know why but it makes a difference! I keep my downloads in a specified place on the home computer, making access at a later time, easy.
I download to my computer and I use Xplorer2 Lite to drag and drop the program to the Add-Ins on the W.H.S. Console. Having done this I access the console, go to settings, add-ins and "available to install", where the L.M.S. should be shown waiting to be installed.
Having installed L.M.S. the console should close automatically.
I go further and carry out a restart of the home server. I then check under the heading W.H.S. security, which should bring up the link for the Task Manager. I then check to ensure that the L.M.S. has started on system start.
Having started, it will take a short time before the L.M.S. is ready to work. I have a Tranquil T7 unit with 2Gb of RAM, but the server does take time to settle down after the install.
On my system, sometimes after adding new music, the L.M.S. for some reason just will not start automatically. It will start manually, but obviously the automatic start is what is required.
The only way out of this, as far as I have found, is to uninstall L.M.S., remove it completely from the W.H.S. Use CCleaner to ensure anything left over, is removed safely. Use Xplorer2 Lite to check the add-ins on the W.H.S. to ensure the program has been removed and then repeat the above sequence.
I don't know why L.M.S. ceases to work as designed, I think it is probably the W.H.S. more than the L.M.S.
Anyway, try the system as above and see if that irons out your problems.
As for being an administrator, you should access the W.H.S. via connector, as administrator with your password.

[mike_zandvliet]

I had the same problem yesterday, and was able to fix it. Just posting here in case it helps anyone else in the future.

The error (from the Windows Application Event Log) was:
"Undefined subroutine &main::main called at slimserver.pl line 101."

This occurred when installing 7.7.2 on a brand new, clean, fresh, untouched install of Windows Server 2003 R2 Standard Edition with SP2 included.

I tried many different things, including reinstalling about 20 times in different ways.

But in the end, the only thing that worked for me was to install 6.7.1, which worked perfectly, and then updated to 7.7.2, which now works fine.

Hopefully this saves someone the 2 hours of pain I went thro

Regards,
Mike


.

[JJZolx]

I see something similar, although I couldn't say whether it's the same problem. I have 40 different instances of SqueezeCenter/Squeezebox Server/LMS installed on my Win2k3 SP2 server (although seldom more than six or seven are running at a time). They're all installed as Windows services, but can be run either as a service or user process. Except for one of them, they all run the Perl code. There is one instance installed of the 'compiled' EXE running on the server. This is the only one that has trouble starting up as a service. About 1/2 of the time, when it attempts to start, it times out. Usually attempting to start it a second time will be successfull.

When it doesn't start, I see the following error in the server.log, and a similar error in the Windows Application event log.:

[12-04-18 17:51:39.5337] main::init (354) Starting Logitech Media Server (v7.7.2, r33760, Thu Dec 22 02:05:03 PST 2011) perl 5.014001
[12-04-18 17:51:45.0652] Slim::Schema::Storage::throw_exception (122) Error: IO::Socket::INET: connect: No connection could be made because the target machine actively refused it.
[12-04-18 17:51:45.0655] Slim::Schema::Storage::throw_exception (122) Backtrace:

   frame 0: Slim::Utils::Log::logBacktrace (/<C:\Program Files\Squeezebox\server\SqueezeSvr.exe>Slim/Schema/Storage.pm line 122)
   frame 1: Slim::Schema::Storage::throw_exception (/<C:\Program Files\Squeezebox\server\SqueezeSvr.exe>Slim/Schema/Storage.pm line 47)
   frame 2: Slim::Schema::Storage::dbh (/<C:\Program Files\Squeezebox\server\SqueezeSvr.exe>Slim/Schema.pm line 2125)
   frame 3: Slim::Schema::forceCommit (slimserver.pl line 1118)
   frame 4: main::cleanup (slimserver.pl line 1093)
   frame 5: main::stopServer (slimserver.pl line 61)
   frame 6: PerlSvc::Startup (/<C:\Program Files\Squeezebox\server\SqueezeSvr.exe>PerlSvc.pm line 95)
   frame 7: PerlSvc::_startup (slimserver.pl line 0)
   frame 8: (eval) (slimserver.pl line 0)