I have MM running as a service, but it won't show up under Media Servers on mobile device unless I run the app

[kkiejko]

So I set up a MediaMonkey server and everything works fine, but only if I'm running the app. I set it up to "run as service" using the option under the server settings, but it doesn't seem to actually do anything. I would assume that if the service is running, I should be able to connect to the server using a mobile device. But it only shows up if I start the app up. Am I missing something or is this working as expected?

[Lowlander]

Which Build (Help > About) of MediaMonkey are you using and did you setup the Service with the same Windows User MediaMonkey is running as?

[kkiejko]

Which Build (Help > About) of MediaMonkey are you using and did you setup the Service with the same Windows User MediaMonkey is running as?

I'm using MediaMonkey 2024.1.0.3113.
Well, that's odd. When I tried to enable the service through MM, it kept telling me my login was incorrect when it asked me for my password (even though it was correct), so I just went into services and set up the MM service to use the Local System Account as I didn't think it mattered. I just now went into services and changed the logon user to the user that I'm currently using (for some reason Services will accept my password) and it looks like it's working now. Odd, I don't see why the logon user would matter for the service.

[Lowlander]

Your MediaMonkey settings are tied to the Windows User, does the Service needs to be run as the same Windows User.

[kkiejko]

Your MediaMonkey settings are tied to the Windows User, does the Service needs to be run as the same Windows User.

Obviously that's true as I just verified it, though I just don't understand why the user running the service matters (as long as it has admin/service access, I would think that it wouldn't matter).

What's really odd is that MM couldn't use my local account to start the service, I had to go into services and edit the service to add my password properly. I guess at least leaving this info here might help someone else who runs into that same issue (with setting up the service).