Invalid Service Account - MID Server Installation

[lopchris27]

Dear my fellow ServiceNow Enthusiasts,

Hope you're all doing great!

I would just like to seek some help and guidance regarding this challenged I recently encountered while setting up or installing MID Server to our client's servers.

I tried to install MID Server using the .msi installer from ServiceNow (Vancouver). Before proceeding with the installation I already created a local account on the server with log on as a service rights and this account is not an admin or a member of it neither. When I was on the part of the installation where it asked me to enter a service account and validate therein, it prompted me that it's "Invalid Service Account".

Also tried to create a local account from the installation window and added log on as a service rights as well but same prompt occurs.

I've tried to use a domain account (not an admin) and added log on as a service rights however it prompted the same "Invalid Service Account".

May I know if someone here encountered the same and if you're able to find the cause.

Thank you so much and Happy Lunar Year!

[SteffenH_Adeno]

Hi,

 Just encountered the same on a new Washington install. I'm a backend sys.admin by trade (trying to find another trench), so I'd already been through the list @lopchris27 (brilliant that) posted. It seems like the installer has a problem with reading Service Accounts. What worked for me:

Run the installer, when it gets to the Service Account part, let the installer create a new local user that will automatically be granted "Log on as a Service" permissions. Then when testing the access, you'll get the "Invalid Service Account" error. Simply exit the installer, repeat the steps until you get to the Service Account part - this time, select the user created first time running the installer (hope you wrote down the password 😉 ) and Bob was my uncle.

When the installer is done and the service can be started, you can then switch the service account to you AD account.

HTH.

[dougw]

This happens, still, if everything is set up correctly and you run the msi file from Windows Explorer.

Easy solution is to launch a command prompt with admin rights and launch the msi from there.  No fuss, no muss.