See this thread:

 http://forums.slimdevices.com/showthread.php?t=27906

SlimServer complains:

Error executing 'SELECT LEFT(album.titlesort, 1), COUNT( DISTINCT(album.id) ) FROM contributors me LEFT JOIN contributor_album contributorAlbums ON ( contributorAlbums.contributor = me.id )  JOIN albums album ON ( album.id = contributorAlbums.album ) WHERE ( ( ( contributorAlbums.role IN ( ?, ? ) AND me.id = ? ) ) ) GROUP BY LEFT(album.titlesort, 1) ORDER BY concat('0', album.titlesort),me.disc,me.tracknum,concat('0', me.titlesort)': DBD::mysql::st execute failed: Unknown column 'me.disc' in 'order clause' at C:\Program Files\SlimServer\server\CPAN/DBIx/Class/Storage/DBI.pm line 771.

And then the entire process stops running.

I suspect that is an easy fix, but I'm wondering why SlimServer would just give up and quit, just because a query failed?  Queries fail all the time (heh, or maybe it's just the buggy queries that I write!), and as a rule, shouldn't make something designed to be running as a daemon/service stop running.  I do appreciate that there are some queries which might fail, and indeed SlimServer would have no way of knowing what to do, but if we're just browsing around, that shouldn't be cause for shutdown.  (I further appreciate that I'm asking for new custom error handling, along with some sort of decision process that decides whether something was trivial or essential).