Mid Server - Unable to start Service

[Edxavier Robert]

Hi all, 

Currently working on a Mid Server installation and got stuck. I follow the process to install the mid-server but for some reason the service for the mid server won't start. 

Steps that I already done: 

1. Create local account with the log on permission

2. Create mid server account with the mid_server role

3. Installed the mid server file using the .msi file from ServiceNow. 

I even recreated the server again and started from scratch, the server is a windows 2022

I went through the logs, this is what I am getting when I try to start the service:

--> Wrapper Started as Service
2024/02/14 11:12:48 | Java Service Wrapper Standard Edition 64-bit 3.5.51
2024/02/14 11:12:48 | Copyright (C) 1999-2022 Tanuki Software, Ltd. All Rights Reserved.
2024/02/14 11:12:48 | http://wrapper.tanukisoftware.com
2024/02/14 11:12:48 | Licensed to ServiceNow, Inc. for MID
2024/02/14 11:12:48 |
2024/02/14 11:12:48 | Classpath element, wrapper.java.classpath.2, did not match any files: extlib/*.jar
2024/02/14 11:12:48 | Launching a JVM...
2024/02/14 11:12:52 | WrapperManager: Initializing...
2024/02/14 11:12:54 | Logger for 'glide' has not been configured by the container, configuring now:
2024/02/14 11:12:54 | Configuring log handler: java.util.logging.FileHandler
2024/02/14 11:12:54 | Setting useParentHandlers=false for Logger 'glide'
2024/02/14 11:12:56 | Overriding formatter to: com.service_now.mid.logging.MidLogFormatter (for handler: java.util.logging.FileHandler)
2024/02/14 11:12:56 | FIPS Enforced Mode: false
2024/02/14 11:12:56 | JVM property java.security.egd: file:/dev/urandom
2024/02/14 11:13:06 | <-- Wrapper Stopped

[Community Alums]

If you created local admin user (for the MID) , opened port to your servicenow instance (out:443/if for test add and 80), your Java is actually current/prerequisite version, checked your Java path is correct in your environment variable, set your MID to run as service under local account (your MID user), your MID folder is not shared folder but on C; drive and in folder without special permissions - uninstall everything and download the zip version and run the install.sh

[Edxavier Robert]

Hi, 

Still not sucess, I event create another server but this time with 2012 version and I'm having the same experience. 

[Edxavier Robert · Accepted solution]

After a lot of troubleshooting, I was able to fix my issue. What I did was change the password for the ServiceNow account that I was using for the mid server. I had a very complex password, so what I did was simplify the password and it's working now. 

[smistry]

Which password was this? Was it the service user on the windows host, or the mid server account on the servicenow instance?