database is locked

[guest19]

Hello,
I am testing mediamonkey and I like it very much.
However I have a problem that happens all the time and makes the application unusable.
I have the database file to a network location. Accessing the file from lan is not a problem.
But when I use my laptop over wifi I always get errors "there was a problem querying the database" ... "database is locked".
I noticed that this happens when there is short wifi disconnection. I reproduced also when turn off and on wifi.
After that mediamonkey shows all the time these errors and the only way to shut it down is task manager.

Is this something that can be fixed ?
thank you!

[pbs001]

I get the same problem.

Even knowing how to unlock it would be a pretty big help

[martialartsguy]

I found that a full restart of the computer and then running MM helped my database lockup.

[shawnharper]

I'm getting the same error repeatedly. My db is on a NAS.

Rebooting and restarting is NOT an option.

[Lowlander]

Try moving the database to the local PC as the NAS is probably locking it. Anyway it's recommended to work with the DB on the local PC and not a network location as performance will be slower and database corruption might occur.

Did you try restarting the NAS?

[martialartsguy]

This is getting to be quite an annoying experience. It happens quite often now, and I'm not sure what's causing it. Any ideas?

Just to iterate my situation: my MM3 is on the F drive (internal) of my desktop.

Running Windows 7 Pro, with MM run as administrator.

[shawnharper]

I'm having the same issue. My DB is on a NAS (Synology Diskstation) as well and has rendered MM unusable.

[Lowlander]

Please no double posting: http://www.mediamonkey.com/forum/viewto ... 53#p284453

as per: http://www.mediamonkey.com/forum/viewto ... =7&t=40381

[shawnharper]

double posting? or double responding? I can see the former being frowned upon, but...

Well, I guess each forum has it's standards. Sorry for trying to drive resolution of what seems to be a fairly common problem amongst users (and this one is a paid user).

[Lowlander]

That's why it's not recommended to use the database over WiFi or NAS as these issues can occur in those environments. Even sharing the database is not recommended as SQLite isn't really designed for a multi-user environment. You could try decreasing robustness and see if it affects file locking: http://www.mediamonkey.com/support/inde ... 75&nav=0,3 Although you now risk database loss so backups are important.

Also see if disabling the Backup script (if installed) helps.

[shawnharper]

Thanks Lowlander. I didn't realize that using the db over wifi or NAS wasn't recommended - that comment hadn't turned up in the other posts on this subject, so thanks. I may have to rethink my strategy, or try other software. Do you know if 4.0 will be an improvement in this area?

And apologies for the double-post. Now that I know the rules I'll behave.

[Lowlander]

I think using the DB over the network is going to cause some form of issue with most applications. Are you sharing the database between multiple users?

I doubt that MediaMonkey 4 solves any problems as this is deeper problem than MediaMonkey.

[shawnharper]

Hi Lowlander - I haven't used MM since our last exchange. Been busy, frustrated, etc...

But, I'm motivated again to get a "system" working again, and am hoping you can help me with the framework, since you seem to know the program very well.

My situation is this...

I have three computers that I could conceivably want to use MM on. By use, I really mean play. One computer, my laptop, is what'd I'd generally use 90% of the time for managing music (adding, tagging, etc). That could push to 100% if necessary.

My music is all on a linux-based server, and I can't assign a drive letter to it (if that matters). So my music is here - \\Server\music\

So... Should I keep the MM.db file on my laptop, or on the server? Based on your comments, I think on the laptop. But will that still cause issues, since all the music is still on the network?

Thanks,
Shawn

[Lowlander]

I also use 1 PC for all tagging. So each PC has it's own database locally and the files are on a NAS. This is not a problem and using the UNC path (\\Server\music\) is actually preferred.

All you have to do is once in a while scan your music again to pick up the changes made by the 1 laptop you use to make the changes.

[shawnharper]

Thanks - I'll try that approach. Should work fine. Not quite as good as simultaneous updates, but...