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!

[Oyvind Schei]

Hi @lopchris27!

Facing an "Invalid Service Account" error during MID Server installation can be frustrating, but this issue is often related to permission settings or the way the account is being recognized by the ServiceNow MID Server installer. Here are some pointers and troubleshooting steps that might help resolve this issue:

1. Check the Account Permissions: Ensure that the account you're using for the MID Server service has the necessary permissions. Even though the account doesn't need to be an admin on the system, it must have "Log on as a service" rights. Double-check these rights through the Local Security Policy on the server to ensure they're correctly set.

2. Format of the Username: When entering the service account information, ensure that you're using the correct format. For domain accounts, you should use the format DOMAIN\username. For local accounts, just the username should suffice. A common mistake is formatting the username incorrectly.

3. Password Complexity and Policy Compliance: Ensure that the account's password complies with the domain's or local security policy's complexity requirements. Sometimes, the issue might be due to the password not meeting these requirements.

4. Try Running the Installer as Administrator: Even if the service account isn't an administrator, running the installer with elevated permissions (right-click on the .msi file and choose "Run as administrator") can help avoid certain permission-related issues during the installation process.

5. Verify the Account's Existence and Status: Make sure the account is active and not locked or disabled. This can be checked through the Local Users and Groups manager on the server (for local accounts) or through your domain controller's management tools (for domain accounts).

6. Use the Local System Account for Testing: As a troubleshooting step, try installing the MID Server using the Local System account. If the installation proceeds without the "Invalid Service Account" error, the issue is likely related to the specific account you're trying to use. Note that using the Local System account is not recommended for production environments due to security considerations.

7. Review MID Server Logs and ServiceNow Documentation: If the installation fails, review the MID Server installer logs for any additional details that might point to the cause of the issue. Additionally, ServiceNow's official documentation for the Vancouver release might have specific instructions or prerequisites for the MID Server installation that could be relevant.

8. Contact ServiceNow Support: If you're unable to resolve the issue after following these steps, consider reaching out to ServiceNow support for assistance. They might be able to provide specific guidance based on the details of your environment and the version of the MID Server you're installing.

The key to resolving such issues often lies in careful attention to detail regarding account permissions, installation procedures, and adherence to best practices as outlined in ServiceNow's documentation.

And to be honest... Sometimes, it's easiest to start over with a fresh installation to ensure you avoid possible complications later on. This approach can help establish a clean baseline from which to build your discovery process, ensuring that you're working with the most up-to-date and efficient setup possible.

Hope this helps out @lopchris27!

Kind regards

Øyvind

Sopra Steria Norway

[lopchris27]

Hello @Oyvind Schei,

Thanks for these suggestions. I will run through with these checks and keep you posted.

[chrohm]

Hi! Try login with the service account on the server once before running the setup

[lopchris27]

Hi @chrohm,

Thanks for the tip. Will try this one.