MID Service account validation failed

[Grischa]

Hi,

I just created a new SNOW instance running the Paris release. 

I downloaded the MID server installer for Windows (64 bit) and unfortunately I'm stuck in the service account validation.

The error message is: 

Service account does not have the "Log On As Service" right. 

I checked the log on as service right and the user has the rights. 
Tested also with 2 other users, but still the same issue.

The "old" Orlando release worked fine. 

Any ideas? 

[Grischa]

I tried domain user (domain\username) and also a local user (with ".\" and without).

In the logon as service rights domain users are listed as "domain\username" - local user just the username

[Patrick DeCarl1]

Hmm. I did the local account and made sure it had admin rights to the box, and updated the policy. So my account was call midserver, and when I put in the service account field I did the .\midserver formate. 

Have you a HI case? Worst case, you can download NY or O mid server installer, once install and connected to the P instance it will upgrade. Again, doesn't solve your issue but just get you going. 

[Patrick DeCarl1]

Grischa, 

I am hearing from coworkers there might be a bug with current version if the hostname has any uppercase letters. Does your server hostname have any uppercase?

[mayurmalhotra]

Thank you. When I lower the letters for hostname then the issue got resolved.

[Twoodard]

Hi @Grischa 

If you are still having issues with the "Log On As Service" right for the user, here are two things you can try/check.

1. When you are adding the Log on right through the local security policy, make sure you are choosing the correct "location" for the username that you are adding.   I have run into situations where people are trying to apply the right, but then choose the domain location rather than the local location for a local user.  This will result in it failing.

2. A second way you can give the right to a user is to go to the service tab.  There, you can see each service has its own "Log On User".  If you go to properties for a given service, you can configure this yourself.   If you try to set a service's logon user as one which doesn't currently have the right, it will apply the right to that user.

If adding it normally through the local security policy doesn't work, I would look for a non-running service in the services window, and try switching the logon user to the user you want to use for the MID.  After you do this, you can switch it back to local system or whatever it was before.  This should let the installer succeed in using that user