Bugzilla – Bug 170
MoodLogic settings disappear
Last modified: 2009-09-08 09:25:27 UTC
I've MoodLogic installed and turned on in the SlimServer settings. Sometimes the MoodLogic setting disappears from the Server Settings page and the information is again read from the ID3 tags I can surely reproduce with the following steps: - SlimServer and MoodLogic running - Installing a new SlimServer version -> MoodLogic disappeard from the Server Settings page After a reboot everything everything is ok (MoodLogic settings are back there). Perhaps it also occurs on other occasions (I still do a lot of profiling and adding of new MP3's in MoodLogic), but I'm not sure
It also seems to occur if I restart manually the Windows service
is this still an issue with 5.1.1? if so, can you manually start using slim.exe --d_moodlogic and see if: 1) the problem occurs 2) what messages come up as the possible problem
The error still occurs. The are the error messages MoodLogic Error Event triggered: 'MixerError',10000 Try Rebuilding the Mixer Database 2004-04-05 00:44:41.8100 rebuilding mixer db MoodLogic Error Event triggered: 'MixerError',11000 Try Rebuilding the external databases MoodLogic Error Event triggered: 'MixerError',10000 Try Rebuilding the Mixer Database 2004-04-05 00:44:42.0435 using moodlogic: 0 MoodLogic Error Event triggered: 'MixerError',10000 Try Rebuilding the Mixer Database 2004-04-05 00:44:42.2881 rebuilding mixer db MoodLogic Error Event triggered: 'MixerError',11000 Try Rebuilding the external databases MoodLogic Error Event triggered: 'MixerError',10000 Try Rebuilding the Mixer Database 2004-04-05 00:44:42.5156 using moodlogic: 0 After rebuilding the MoodLogic database with Test_MoodLogic_COM.exe it works
perhaps this needs to have an item in the FAQ, with a link to the COM test app.
Or is there a way to automatically execute the tool on startup?
that would be bad. the test seems to lock the db, so when slimserver tries to check if moodlogic is available, it will fail. I have also had this happen if moodlogic was running at the same time as I start slimserver.
Kevin: what's the fix?
er...call microsoft and tell them access mdb shoudln't have to be locked? All I can say for sure is that I've found myself having to shut down moodlogic, slimserver AND not have the test_COM running...then I can restart. I just dont think running the test_COM automatically is good. I've only ever had it happen, seemingly at random or when I've been doing something that normal users could not be doing (swapping different mdb versions). When it happened the one time legitimately, I could not reproduce.
Have had this happen again recently, after leaving the mdb unused for weeks. slimserver gave a moodlogic debug message saying db was corrupt. Running moodlogic rebuilt the dB on startup. Perhaps this is something for the FAQ. It is similar to the iTunes problem.
KDF: Is this fixed?
From my understanding of why this was disappearing, its not womethign we CAN fix. If the db is corrupted, it has to be rebuilt before the connection to moodlogic will pass, thus enabling the plugin to work. I've not been able to get any info on what causes the db to be reported corrupt when sometimes nothing has touched the file in ages. However, running moodlogic does rebuild the db and make it all work again.
I'll mark as wontfix, since we basically can't.