Thanks, tracking as http://www.ventismedia.com/mantis/view.php?id=14218

pbryanw wrote:Hi,

Sorry for reopening this old thread but I had a similar problem (Error 1069: The service did not start due to a logon failure) when trying to install the MediaMonkeyService from inside MMW.

In the end, I found a fix on this old Microsoft support page: https://support.microsoft.com/en-gb/kb/327545
The advice still works for Windows 10:

1. Open Local Security Policy app
2. Expand Local Policies, and then click User Rights Assignment
3. In the right pane, right-click Log on as a service, and then click Add User or Group.
4. In the User and Group Names box, type the name that you want to add to the policy, and then click OK. (in my case this was the admin user account I log in with)
5. Quit the Local Security Policy app.

One reboot later, the MediaMonkey service started running with no problems. Hope this might be of help to someone who experiences the same error.

I just registered to forum to say thank yo a lot. this was worked for me.

pbryanw wrote:Hi,

Sorry for reopening this old thread but I had a similar problem (Error 1069: The service did not start due to a logon failure) when trying to install the MediaMonkeyService from inside MMW.

In the end, I found a fix on this old Microsoft support page: https://support.microsoft.com/en-gb/kb/327545
The advice still works for Windows 10:

1. Open Local Security Policy app
2. Expand Local Policies, and then click User Rights Assignment
3. In the right pane, right-click Log on as a service, and then click Add User or Group.
4. In the User and Group Names box, type the name that you want to add to the policy, and then click OK. (in my case this was the admin user account I log in with)
5. Quit the Local Security Policy app.

One reboot later, the MediaMonkey service started running with no problems. Hope this might be of help to someone who experiences the same error.

I had the same Error 1069 and your solution worked. Thank you.

Windows 10 Pro
MM 4.1.10.1778

Hi,

Sorry for reopening this old thread but I had a similar problem (Error 1069: The service did not start due to a logon failure) when trying to install the MediaMonkeyService from inside MMW.

In the end, I found a fix on this old Microsoft support page: https://support.microsoft.com/en-gb/kb/327545
The advice still works for Windows 10:

1. Open Local Security Policy app
2. Expand Local Policies, and then click User Rights Assignment
3. In the right pane, right-click Log on as a service, and then click Add User or Group.
4. In the User and Group Names box, type the name that you want to add to the policy, and then click OK. (in my case this was the admin user account I log in with)
5. Quit the Local Security Policy app.

One reboot later, the MediaMonkey service started running with no problems. Hope this might be of help to someone who experiences the same error.

Thanks Ludek.

On vacation now until Jan 17. Will do testing w/ special version when I get back.

Dennis

Hmm, it means that start of the service works fine via command line even if it is not running as administrator (as expected).

So that is really strange why MM is getting "Access Denied", because MM actually does the same (it calls 'sc start MediaMonkeyService').
In addition you indicated that the service is properly closed by MM on MM start, and properly started by MM on MM closing which is strange, because MM uses the same method to start it (as during install).

I am going to prepare special testing MM.EXE for you that could show us more.

EDIT: Could you please download this http://happymonkeying.com/beta/MediaMonkey.exe and replace your current MediaMonkey.exe by this one downloaded and generate debug log while installing the service? Thank you.

I had cut off the right-hand side of the 'sc start' command output. Here is the complete output:

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\dmcr>sc start MediaMonkeyService

SERVICE_NAME: MediaMonkeyService
TYPE : 10 WIN32_OWN_PROCESS
STATE : 2 START_PENDING
(NOT_STOPPABLE, NOT_PAUSABLE, IGNORES_SHUTDOWN)
WIN32_EXIT_CODE : 0 (0x0)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x76167d40
WAIT_HINT : 0x1388
PID : 6740
FLAGS :

> What exactly the error after installing the service in MM says

[SC] StartService: OpenService FAILED 5:
Access is denied.

So I caused the error to occur by uninstalling and reinstalling the service. Then I opened a command prompt window and typed in the command you said. It worked:

Microsoft Windows [Version 6.1.7601]
Copyright (c) 2009 Microsoft Corporation. All rights reserved.

C:\Users\dmcr>sc start MediaMonkeyService

SERVICE_NAME: MediaMonkeyService
TYPE : 10 WIN32_OWN_PROCESS
STATE : 2 START_PENDING
(NOT_STOPPABLE, NOT_PAUSABLE, IGNOR
WIN32_EXIT_CODE : 0 (0x0)
SERVICE_EXIT_CODE : 0 (0x0)
CHECKPOINT : 0x76167d40
WAIT_HINT : 0x1388
PID : 6740
FLAGS :

The MM service was not running before I typed in this command, and it *was* running afterward. This was when running as myself, not as admin. However, note that my account has admin permissions.

Note that as mentioned previously, after getting this error, I can also start the service from the Services window.

Dennis

Yes, the service is supposed to be running only when MM is not running, because it actually shares the same data and runs MediaMonkey.exe.
So MM stops the service when starting and starts the service when closing.

So it seems that there is a conflict when MM tries to start the service during install the service (when both MM and the service are running).
I will try the MediaMonkeyRemote to see if I can simulate the conflict.

What exactly the error after installing the service in MM says, is it still the "OpenService FAILED 5: Access is denied"?
If yes, could you please try this after the error is shown:
- run "cmd" (i.e. command line)
- type "sc start MediaMonkeyService" to the command line
What does it write?
And what does it write if you run "cmd" as administrator and perfrom "sc start MediaMonkeyService"?

> BTW: if you start MediaMonkeyService manually via the "Services" window, does it also write "access denied" or it is issues only when MM starts the service?

I just now tried that, and I got a different error (unfortunately, I did not write it down and now cannot reproduce). I then tried to uninstall the service and was unable to delete it. I had to reboot. But now that I've rebooted, I get the usual StartService error when I try to install the service. But when I exit MM, the service starts as expected. It then toggles off and on whenever the MM client is started or stopped. The service, when running, is functional and can be accessed by various uPnP clients around the house. So the only anomaly I am experiencing right now is the StartService error.

It is possible that some of the other problems I have reported might be due to the MediaMonkeyRemote server (by Erlend Dahl) that was running some of the time on my PC, and which I now see is unable to work with the service and also sometimes seems to prevent the service from functioning properly. (On the other hand, the MMR server mostly seems to work OK with the MM client itself).

Dennis

No, the service account should be your user name ".\dmcr" so that your MM settings is used (Users/dmcr/AppData/Roaming/MediaMonkey/...).

Have you been successful to change anything on the "Log on as" page?
But I don't think that user/passwrord is the problem, because the error would be "log on failure" when starting the service, but you wrote that it is "access denied" in your case, which is strange, because you are logged as "dmcr" so I don't see a reason for the "access denied".

BTW: if you start MediaMonkeyService manually via the "Services" window, does it also write "access denied" or it is issues only when MM starts the service?
If yes, it could be caused by Group Policies defined in your domain, similar problem had user here: http://forums.whirlpool.net.au/archive/1854339

Yes, the UAC dialog is displayed after I type in my password, and I then click Yes, and 5 seconds later get the StartService error.

And I have the standard (not portable) version of MM 1685 installed.

I noticed that the "Log On As" column in the Services window lists me as ".\dmcr" rather than simply "dmcr" or "MSHOME\dmcr" (where MSHOME is my workgroup name) or "dmcr-home\dmcr" (where dmcr-home is my computer name). I've not seen this syntax used before. If the password I type in is not being filtered in any way, then perhaps it is the user name (".\dmcr") that is the problem.

Or should the service's "Log On As" be "Local System", the same as other vendors' services that get installed?

Dennis

Hi, was MM asking for elevation (UAC dialog) when installing the service? I mean this dialog: http://reformedmusings.files.wordpress. ... dialog.jpg
Did you click [Yes] ?

If not, have you installed portable or standard version of MM? If you install portable then it could be: http://www.mediamonkey.com/support/inde ... icleid=153
So be sure you installed the standard version. (I opened new issue to cover this: http://www.ventismedia.com/mantis/view.php?id=11678 )

Rebooted and successfully installed 1685. It has the same problem getting the service to start.

Also, I just tried to install 1685, and encountered the same problem. Interestingly enough, I get a similar error when the installer tries to replace MediaMoneky.exe as when I was trying to install the service earlier:

DeleteFile failed; code 5.
Access is denied.

(In the install service failure case, I get:
[SC] StartService: OpenService FAILED 5:
Access is denied. )

I followed your suggestion and started Dbgview.exe as admin and enabled "Capture Global Win32". But when I then tried to install 1685, no information was logged in the Dbgview window at any point, including at the time of the DeleteFile failure. Could it be because I was running the installer and not MM itself?

Dennis