View Issue Details

IDProjectCategoryView StatusLast Update
0011823MMW v4DLNA/UPnPpublic2014-02-03 15:36
Reporterrusty Assigned To 
PriorityurgentSeveritymajorReproducibilitysometimes
Status feedbackResolutionopen 
Product Version4.1 
Target Version4.1.1 
Summary0011823: UPnP installed as a service is created with incorrect credentials in some cases
DescriptionHere's what I did:
1 In MMW, click the install as a service button
2 Enter _incorrect_ password
-->error message re. incorrect credentials, but the service is still installed
3 In MMW, click the 'uninstall' service button
4 Re-install the service
5 Enter the correct password
-->Service seems to be installed correctly
6 close MMW
7 Try to access the UPnP server with MMA
-->It isn't listed!
8 On the windows machine, run services.exe, select the MediaMonkey Service and verify that it's running (it is)
9) Click the service's 'Log on' tab
--> The Service is configured to log on to the 'Local System Account' instead of to the user's account!!
10) Change the credentials to log onto 'This account': <accountname>, and apply
11) Restart the service by restarting MMW and closing it
--> The service works correctly

I'm not able to replicate this. Peke can you--perhaps with some variation?
TagsNo tags attached.
Fixed in build

Activities

Ludek

2014-01-31 18:08

developer   ~0039475

Last edited: 2014-01-31 18:15

I haven't been able to replicate, couldn't this be just test error?

In step 7) I can browse the server in MMA
In steps 8&9) I see that the service is running (as expected) and on the [Log on] page I see "This account: .\Ludek" (as expected)

peke

2014-01-31 23:33

developer   ~0039477

1-2: I tested on same steps and after step 2 I got ACCESS Denied.
3-8: Continued with steps and on step 8 Service wasn't running
9: Logon Tab was Filled With "Administrator" Credentials.
10: I corrected credentials to .\Peke Account
11: Service is working Correctly

12: Uninstalled Service
13: restarted System

Now I get same results as Ludek eg. for me it was test error or leftovers from previous installs.

Guess KB Article needs to be written to clarify this behaviors and how to manually correct things.

rusty

2014-02-03 03:51

administrator   ~0039483

I'm not sure what the test error could be. I never installed MM as a service previously and never accessed the MediaMonkey service via services.exe, so there's no way I could have set the service to use any particular account (i.e. I can't think of anything other than MMW that could have set it to use the 'Local system account').

So the question is: if MMW didn't set the service to use 'Local system account' how else could that arise?

Ludek

2014-02-03 09:53

developer   ~0039484

Last edited: 2014-02-03 10:00

When service is installed MM does it in several steps:
1) it installs the service (the default is the 'Local System Account')
2) it changes the log-on account to the user account
3) it sets rights to start/stop the service from the user account
4) it tries to run the service to verify the correctness and shows message dialog

So I guess that for some reason it failed on step 2) for you. Not sure why as I have not been able to reproduce it, maybe you did not accept the UAC prompt?

But in my case (the default Windows 7 settings) if the UAC isn't accepted then the service isn't installed at all. But maybe your local user policies / security options differs in some way causing the issue, the strange thing is that you could reproduce this only once (on first try) ??