After a restart of the system the problem has not appeared. Unfortunately though, as I just wanted to try to figure out, what is keeping windows from accessing these particular files using process monitor. As I wrote before the behavior did not seem to be related to MediaMonkey itself but rather Windows with it's network access causing the trouble. Thanks for your suggestions though.

Might you have saved a bad login for the network path?

I am using Vista and the File Server is running on Debian Etch. It does require login and I need to provide this to MediaMonkey whenever I restart the Vista machine. However, as I can play all the other tracks of the discussed albums and access the files using the network share, I guess this issue is not related to authentication.

I just figured out, that I can access the files using explorer through the mapped network shares (virtual drive), but cannot access them using the entire network path. So it seems, that this is not related to MediaMonkey, but to Windows, as the second method is the way in which the files are stored in the library. I still have no idea though what this is caused by (especially as it always is track number one) and the file permissions on the Samba shares are the same for files, that are accessible and files, that are not.

Does the server require login or are you sure you're logged in before you try to access the files on this server? Can you give some more details on this server? Do you have other servers and do they work? What version of Windows are you using?

Recently I noticed repeatedly that my Monkey fails to play the first track of several albums from my network server share. The tracks are there and readable (if I move them to the local harddrive, I can play them without any problems) and the path stored in the library is correct, too. However, if I try to use the reorganize feature of MediaMonkey on these files, it fails as well stating: "An error occured while moving file xy to abc. Do you want to try again?"

It seems to me, that this happens since I updated to 3.1.0.1256 - before everything was okay.