Rusty,
yes, I waited until 1244 was available and then tried again immediately. It did not really make a difference.

Note that I am doing this as a test, to try the limits and see if there is an improvement. In normal use, we don't start both MM's with auto-scan on!

But it must be said: when one of us wants to do tagging/synchronising/ripping, we must ask the other to stop MM. Still so with 1244.
And we would like to find a solution for that!

Regards,
Willy

willydvds,

My point was actually to try the new build 1244 since there are changes that are likely to mitigate the problem since there were some network-related problems that were exacerbated in 3.1 (as compared to 3.0).

-Rusty

I think I get the point: this is not a bug/error/shortcoming in MM, but a result of the combination of underlying database/hardware etc.
So: in fact not a topic for the beta forum. Correct me if I'm wrong!

I'll post a thread in the general forum for further suggestions how to best avoid the problems.

Thanks for the clarification,
Willy

Also, note that build 3.1.0.1244 includes several changes to improve network performance and error handling.

-Rusty

One other suggestion, instead of having multiple computers doing auto-scan, have only 1 do it. That way you greatly reduce the conflicts of multiple updates at the same time.

edit:

regarding 3.0, perhaps the problem re-manifested itself due to the increased database size.

From previous threads, the db increase is primarily due to full text search index added to db.

Thanks for the respons.

Indeed, SQLiteSafety = 2. The hosting server is a windows PC (XP).

We did have this problem with 3.0 initially, but after some time the problem "faded out". It occured, but so incidentally that we could accept it.
I don't understand why, though.

We're really very pleased with MM, but with this issue we can't use it as we want. So suggestions are welcome!

Thanks for looking at this!

Regards, Willy

[System]
SQLiteSafety=2

I think sqlite is just not very well suited for simultanious multi-user environment.

http://www.sqlite.org/whentouse.html

[quote]Client/Server Applications


If you have many client programs accessing a common database over a network, you should consider using a client/server database engine instead of SQLite. SQLite will work over a network filesystem, but because of the latency associated with most network filesystems, performance will not be great. Also, the file locking logic of many network filesystems implementation contains bugs (on both Unix and Windows). If file locking does not work like it should, it might be possible for two or more client programs to modify the same part of the same database at the same time, resulting in database corruption. Because this problem results from bugs in the underlying filesystem implementation, there is nothing SQLite can do to prevent it.

A good rule of thumb is that you should avoid using SQLite in situations where the same database will be accessed simultaneously from many computers over a network filesystem.

[/quote]

What is hosting your database, a windows computer? a nas? a linux box?

If it is a nas, you may be able disable some peformance options regarding write caches/locking files.

From what I understand, the root problem is that whatever is hosting your database is not keeping up with file locking transactions from multiple systems.

Why this worked for you on 3.07 and not 3.1 I can not explain.

Worse case scenario, you re-install 3.07 over the existing 3.1 on all your machines and restore the last usable 3.07 database you have.

Maybe you should check all your mediamonkey.ini files have included:
[code][System]
SQLiteSafety=2[/code]

There a tick before this thread, don't know if that means that the matter is solved? Well, sorry: it isn't.

I've installed 1244 on our 4 PC's. I start MM on the first, and make it scan the library. Then I start MM on the second: several errors messages, and then MM crashes.

Some automated messages have gone to support. The debug version is installed, so I can provide more info if required.

We consider this a very serious problem, in fact it means we cannot both use MM simultaneously.

Regards, Willy

reinstalled 1242... and all my problems went away! w00t... thanks MM team

fyi, some improvements were made for build 1242 re. DB upgrades. In addition, further improvements have been made for the next build (1243+) re. network performance.

-Rusty

the file is deskplayer.dll, and running vista ultimate, I have tried everything to get rid of this file with no luck. I think this is why I can't get a good reinstall. I have reinstalled several times, but MM still will not import my music to the library. I never had any problems until I tried beta...

This must be another problem, I don't see this file on my PC.
Regards, Willy

[quote="fatjacq"]Did an uninstall / reinstalled the old one, but during the uninstall, there is a file left that will NOT delete.[/quote]

With regards to the file that MediaMonkey fails to remove during uninstall, DeskPlayer.temp.0, you can just delete it manually in Explorer. It is an annoyance that the uninstall doesn't automatically delete it, as it should.

This happens to me every time. I only have one PC, new Vista install. Had no probs with the old version, and this is driving me nuts. Did an uninstall / reinstalled the old one, but during the uninstall, there is a file left that will NOT delete. Still have the two popup errors on startup. Somebody help!

I've been trying to create a problem that I can reproduce. Well, this goes wrong every time I try.

Setup: PC1 contains MM db and all MP3 files, PC 2 and PC 3 are user PC's running MM debug 1240. All PC's run XP.

PC 1 is on, no MM running. I start MM on PC 2, with monitoring option on. While it is still scanning the disk, I start MM on PC 3 (also with montoring on).
This is too much: lots of error messages and after a couple of minutes, both MM's hang. I can't do anything but stop both MM's with task manager.

Obviously, it can happen that the one MM must wait a bit while the other is doing something. But it shouldn't end up like this.
I have created a debug report. Shall I submit a ticket to get this to you?

Also let me know if you need some further information.

Regards, Willy