PDA

View Full Version : 6.2 Woes



bishopdonmiguel
2005-10-28, 07:42
Building a replacement file server so I decided to take the plunge to 6.2.1 from 5.4.1. Pentium D 2.8, 1GB RAM, Windows 2000 SP4 (clean install)... 6.2.1 installs fine but only scans 90 songs then crashes (I've got about 4,000 tracks). A restart brings SlimServer to a stable state but it quickly consumes about 210MB of RAM. A rescan causes another crash with the same number of tracks... 90. MP3s play but WMAs do not (perhaps a second then client loses contact with SS although the service doesn't crash, just uses high CPU). Checking the list of 90 tracks, some are repeated as "Unknown" even though they are also listed corrected under artist and album. Tried 6.2.0 with same results. Tried 6.1.1 with same results. Tried 5.4.1... works perfectly as it always has.

Same system, same tracks, same file structure, same service settings but 6.x doesn't work and 5.4.1 does. Any ideas what might be causing this? 6.2 looks promising but something is amiss.

Dan Sully
2005-10-28, 09:16
* bishopdonmiguel shaped the electrons to say...

>Same system, same tracks, same file structure, same service settings
>but 6.x doesn't work and 5.4.1 does. Any ideas what might be causing
>this? 6.2 looks promising but something is amiss.

What does the System Event Log say?

Can you run it from the command line?

-D
--
<noah> I used to be indecisive, but now I'm not sure.

bishopdonmiguel
2005-10-30, 08:22
> What does the System Event Log say?

Not much. Lots of...

Perl interpreter failed.

And one of...

DBD::SQLite::db prepare_cached failed: no such column:
contributors(1) at dbdimp.c line 268 at /PerlApp/Ima/DBI.pm
line 391.

But this was near the end of my trails and might have been related to 6.1.1, which I installed last.

bishopdonmiguel
2005-10-31, 12:50
> Perl interpreter failed.

Anyone know what causes this error to be reported in the Event Log under Windows 2000 when running 6.2.1?