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

Dave2 · ‎08-10-2020

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 · ‎08-13-2020

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

View solution in original post

jason_lau · ‎11-30-2020

I had the same problem. KB below solved the issue for me (Paris release):

https://hi.service-now.com/kb_view.do?sysparm_article=KB0855251

Basically, you have to start the msi installer from command shell running as administrator (versus running as user with administrator permission.

Per KB documentation:

There are two workarounds for this issue.

Launch a "Run as Administrator" command prompt, and use the following command to launch the installer
"msiexec /i {installer name here}
Log in as the built in Administrator account, and launch the installer.

Randall King · ‎12-03-2020

Running the MSI from an elevated command prompt resolved the problem for me. I didn't make any other changes.

Bobin · ‎05-16-2021

Hi All,

Just to keep you all updated on this issue which occured to my instance which is in Quebec release.

I had a domain account with "Log on as Service" enabled and a non-admin one as per the docs (tried providing admin as well).

Tried the steps as suggested by everyone above and the only solution worked for me was to install the MID Server from the ZIP file (which takes you through the old installation method where it does not ask you for a service account).

You can download the ZIP file by enabling the below option in MID Server > Downloads page.

Hope this saves some time for anyone facing similar issues.

Thanks,

Bobin

Neil5 · ‎08-12-2021

I tried installing a MID server today and have the same issues as everyone. We are in Quebec release.

What i did was check the Windows Security logs and find that the installer is trying to login with a local server account instead of a domain account. Means even if i put "domain\service account", the event logs reflects failure because it's actually trying "servername\service account".

So what worked for me was to create a local account, assign appropriate "log on as a service". Installation will now push through creating the appropriate service. Edit the service and change the "Logon As" with the domain account.

Hope this helps.

Community Alums · ‎01-25-2022

Thank you Neil, actually this approach solved our issue (Quebec release as well) and we managed to install the mid server!