MID Server Install Fails - Logon as service right - but it has it.

[Dave2]

I am attempting to setup a MID server for a test integration of SNOW. I verified that the account has "Log on as Service" on both the server that I am installing it on and on the AD Domain Controller it will pull from. 

I complete the first step of the installer no problem. When I attempt to finish up the next step, I see the error below:

But this is copied directly from the server this is being installed on and you can clearly see that it DOES have that right. 

Just to be sure, I checked the "Deny Log on as Service" on the server and nothing is there either... 

So if it has the rights, why does the MID installer think it doesn't? Any ideas?

Thanks!

[Dave2 · Accepted solution]

Here is an update on this. It is more or less resolved, just not the way I had anticipated. Here is what I ultimately had to do:

1. I created a new OU in my AD and moved the MID server there. I assigned a dedicated GPO to that OU that forced my service account into the Log on as Service for all servers in that OU. - This is because the local policy was trumped by the domain policy. 

2. Then, I still got errors when I tried to install the server. So, I opened up a command prompt as administrator. Then, executed the MID installer using the command line (browse to the directory via command prompt and simply type the name of the installer and press "Enter"). 

3. All that together an "Voila!" the MID server installs. Now it's stuck on validating but that's another issue entirely.

Hopefully my solution will help others solve this issue. If you want more specific details about what I did, reply and I will reach out to you. 

Thanks!

Dave

[Ken Neikirk]

Did you ever get the validating to work?

[DaveHertel]

I ran into same error message/problems while installing Paris MID on lab windows machines that didn't have a windows domain.  Here is what worked for me:

1. On local machine where MID was being installed, opened Local Security Policy>User Rights Assignment > Login as a service.  Added the local user acct that would run the MID service

2. The MID installer complained that this account had Administrator rights... so I went into user/groups, selected the local user acct, and removed it from the administrator group.  (this seems to be a change with Paris... previously the service acct needed to be admin I believe...)

3. Opened command prompt AS ADMINISTRATOR.  Navigated to the directory with the installer, ran installer... validated.  Installer finished and all seemed OK... until I started MID service.   The MID never showed up...  um....

4. looked at logs (in Agent folder\logs).  Errors in logs pointed to access denied when service was trying to run.   This made sense because the installer insisted that I remove "administrator" from the service acct., but then the acct didn't have enough rights to read/write files in Agent folder.  A gotcha.

5. In file system, using file explorer > selected AGENT folder, properties > Security tab.  ADDED the local user acct to the Group or user names and Allowed "Modify" permission.

6.  Attempted starting MID service again.  Success!   And after ~15 seconds the newly defined MID showed up in my PDI instance.

Hope this helps some along the way...? 

[Roffy]

Following these steps for our domain service account worked for me - thanks.

I was running the MID Server MSI installer without elevating to admin privileges and I kept receiving the service account does not have the "Log On As Service" right error (even though it does have this right).

Running via an elevated command prompt console allowed me to continue.

[Ken Neikirk]

1. I logged into the host server the Administrator user account (not as a user with administrator but specifically the Administrator user) where I installed the mid server and created a new standard user to be the Service Account

2. Went to Local Security Policies, User Rights, and Log On as a Service, and added the new user I just created

3. Ran the mid server installer and used the Mid Server User on my ServiceNow instance that I created with the mid_server role and then used the new user specified in step 1 above as the Service Account

4. Completed the installation successfully