The Zurich release has arrived! Interested in new features and functionalities? Click here for more

Mid Server - Unable to start Service

Edxavier Robert
Mega Sage

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

1 ACCEPTED SOLUTION

Edxavier Robert
Mega Sage

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. 

View solution in original post

5 REPLIES 5

The password for the mid server account in servicenow. Not sure why this fix the issue, but now is working without issues.