Hi there,
I already posted on the "German Board":
http://www.mediamonkey.com/forum/viewtopic.php?t=25899
I am running MM Gold 3.0.2.1134 and all my MP3s are stored on a NAS, which is mapped as Drive M:\ via Loginskript. Everything worked fine for a few days but this morning my library was offline again, which means after starting MM all titles are browsable but in light grey and therefore not accessible.
I had this problem before and solved it that way:
Uninstalling MM completely, removing _all_ related directories and also the registry-keys, rebooting, re-installing and re-adding my songs to the (new) library.
Anyone has an explaination for this strange behaviour?
Thx.
Cheers,
Joshua
EDIT:
After unmapping my network-drives and re-mapping it manually (not using the loginscript) the library is online again. Perhaps it doesnt like my loginscript?
Library offline
Moderator: Gurus
Once again, after reboot, the library is not accessible.
What I found out now while playing around a bit:
If I open the mapped networkdrive in explorer _before_ starting MM, library is always online and accesible.
If I start MM without having opened the mapped networkdrive in explorer, library is always offline and inaccesible but -and that makes me wonder- if I try to disconnect the networkdrive while MM is still open it says "open files on Drive M:".
Cheers,
Joshua
What I found out now while playing around a bit:
If I open the mapped networkdrive in explorer _before_ starting MM, library is always online and accesible.
If I start MM without having opened the mapped networkdrive in explorer, library is always offline and inaccesible but -and that makes me wonder- if I try to disconnect the networkdrive while MM is still open it says "open files on Drive M:".
Cheers,
Joshua
MediaMonkey has issues with the way Windows maps networked drives. As such it's adviced to use the UNC path (\\devicename\folder or \\IP\folder) instead of a mapped drive to access files on a network location.
Download MediaMonkey ♪ License ♪ Knowledge Base ♪ MediaMonkey for Windows 2024 Help ♪ MediaMonkey for Android Help
Lowlander (MediaMonkey user since 2003)
Lowlander (MediaMonkey user since 2003)
fwiw: I use an NAS mapped to Z: and have not had any problems with MM recognizing the NAS on startup. I run a batch file on Windows (XP) startup that executes a single line: "Net use z: \\musicserver\share <password> /USER:<user>" and the drive seems to mount just fine.
Not sure if that's what the OP meant by using loginskript, but if not, that might be a help.
Not sure if that's what the OP meant by using loginskript, but if not, that might be a help.
anyone else haver the same thing happen on a partitioned disk? The same solution worked for me - rescan and file monitor as if it is a UNC networked drive - i.e //device name/file path...
It works, though media monkey seems to crash more often this way than in the past.
Someone said that it must have something to do with permissions, which is obviously correct, because the problem arose only on my Vista Home Premium machine, not on my vista business machine. I even gave read/write/modify privileges to that drive for 'everyone' to try to make MM work via Documents/Music/Path.. but no luck
So what is it with home premium permissions? Running as Admin doesn't help either...
It works, though media monkey seems to crash more often this way than in the past.
Someone said that it must have something to do with permissions, which is obviously correct, because the problem arose only on my Vista Home Premium machine, not on my vista business machine. I even gave read/write/modify privileges to that drive for 'everyone' to try to make MM work via Documents/Music/Path.. but no luck
So what is it with home premium permissions? Running as Admin doesn't help either...