MediaMonkey forum

My mp3 files are on a NAS and connected with a network drive letter as /persistent:Yes (needed this because otherwise MM service would fail if i would not first click the netwerk drive after i booted up. This because of netwerkshare was not yet connected, before starting the MM service.) Same user as MM service and user on NAS and user windows login.

Hi,

CrashMonkey wrote: ↑Tue Oct 24, 2023 7:23 pm My mp3 files are on a NAS and connected with a network drive letter as /persistent:Yes (needed this because otherwise MM service would fail if i would not first click the network drive after i booted up. This because of networkshare was not yet connected, before starting the MM service.) Same user as MM service and user on NAS and user windows login.

This answer is not what I was hoped for. Unfortunately you have exact same issues that I had at the point when I tested it.
It was files under https://www.ventismedia.com/mantis/view.php?id=10726 which is superseded in MM5 with https://www.ventismedia.com/mantis/view.php?id=13971 so basically as MM starts as service its credentials are not updated/refreshed after UNC path gets mounted resulting in behavior like explained in https://www.ventismedia.com/mantis/view.php?id=18518

Can i solve that if i change MM storage from 'Local Drive' to netwerk location.
So instead of going to = Z:\music\ ( net use z: \\nasname\music)
Directly going to \\nasname\music.

That way there is no drive letter assigned and won't interfere and MM can connect directly to the nas?

Do i just disconnect the Z drive, and then MM can't find files, and let them search the files on the \\nasname\music location so the filepaths update for every song?

Ok i got VLC working when MM is off, and only the MM service is running. Changed music location from drive letter to fullpath to nas.
I guess i information popup while setting up the service with a guide how to use the fullpath would be handy for new users.

I have all the music files on an external HD (D:) in a folder Music. The permissions on Music is Everyone has Full Control. I also gave my self Full Control just to be safe. All the way down. I checked several files and the permissions are correct for Everyone and myself.

Also, the built in Windows Media Server works properly (although slowly!).
I have not tried uninstalling 2962.

I think I have a workaround to get this to work. For some reason when I drill to the song level, the service stops and is of course, unresponsive.

So I went into the Services app, select Media Monkey service -> Properties -> Recovery tab -> set "Restart the Service" for 1st, 2nd, subsequent failures and set Restart service after "0 minutes".

Then I am able to see and play the individual songs on my client app.

But if I go back into MM now and exit it, the service doesn't start up at all this time!! Crazy!

This service is not very solid. I guess the best solution is to open up the MM app and minimize it and not even use the service.

LINYbob

Just tested it at my end, and i get the same behaivor.
Hower this; "But if I go back into MM now and exit it, the service doesn't start up at all this time!! Crazy!"
If you see that this happens, go to task manager. I noticed that after quiting MM the service indeed does not start.
However MM initilized a new exe to act act as a service. But is not.
In task manager you need to exit the last running mediamonkey.exe and then the service does start again.

Windows eventvwr, gives two errors: Event id 7009 and 7000
Its a timeout that it cannot start, and ofcouse, when the mediamonkey.exe is already running in taskmanager, it cannot start the service.

Will try to catch this behaivor in the debugview. (edit; mediamonkey service does not provide info to debugview, so no additional info from there)

For devs;
Could it be the case it the MM script runs "mediamonkey.exe /Service" to start the service. Instead of using the propper command:
"net start MediaMonkey5Service"

Edit:
See service after reboot, and see the 'service' that is started after exiting MM app.
https://imgur.com/1Z193Hy

Sounds good. Very good work CrashMonkey. Thanks. I'll check out how many MM.exe are running. Hopefully a patch comes out that will solve this cleanly. It sounds like your solution is the correct way to do it.