Unable to start ServiceNow MID Server service

Oliver Anderson
Kilo Sage

‎02-17-2023 08:11 AM

Hi, we use a domain service account to log on as a service and start the MID server service.

 

After an automatic upgrade failing last month, the MID server went down and will no longer start back up. Getting this error in windows:

OliverAnderson_0-1676650205264.png

 

In the wrapper.log I get this message every time it tries to start:

2023/02/17 10:39:33 | --> Wrapper Started as Service
2023/02/17 10:39:33 | Java Service Wrapper Standard Edition 64-bit 3.5.40
2023/02/17 10:39:33 |   Copyright (C) 1999-2019 Tanuki Software, Ltd. All Rights Reserved.
2023/02/17 10:39:33 |     http://wrapper.tanukisoftware.com
2023/02/17 10:39:33 |   Licensed to ServiceNow, Inc. for MID
2023/02/17 10:39:33 | 
2023/02/17 10:39:34 | Launching a JVM...
2023/02/17 10:39:36 | WrapperManager: Initializing...
2023/02/17 10:39:38 | WrapperStartStopApp Error: Unable to locate the class com.service_now.mid.Main: java.lang.ClassNotFoundException: com.service_now.mid.Main
2023/02/17 10:39:38 | 
2023/02/17 10:39:38 | WrapperStartStopApp Usage:
2023/02/17 10:39:38 | WrapperManager Error: Error in WrapperListener.start callback.  java.lang.IllegalArgumentException: can't parse argument number: start_class{/start_method}
2023/02/17 10:39:38 | WrapperManager Error: java.lang.IllegalArgumentException: can't parse argument number: start_class{/start_method}
2023/02/17 10:39:38 | WrapperManager Error: 	at java.base/java.text.MessageFormat.makeFormat(MessageFormat.java:1451)
2023/02/17 10:39:38 | WrapperManager Error: 	at java.base/java.text.MessageFormat.applyPattern(MessageFormat.java:491)
2023/02/17 10:39:38 | WrapperManager Error: 	at java.base/java.text.MessageFormat.<init>(MessageFormat.java:370)
2023/02/17 10:39:38 | WrapperManager Error: 	at java.base/java.text.MessageFormat.format(MessageFormat.java:859)
2023/02/17 10:39:38 | WrapperManager Error: 	at org.tanukisoftware.wrapper.WrapperResources.getString(WrapperResources.java:215)
2023/02/17 10:39:38 | WrapperManager Error: 	at org.tanukisoftware.wrapper.WrapperStartStopApp.showUsage(WrapperStartStopApp.java:1028)
2023/02/17 10:39:38 | WrapperManager Error: 	at org.tanukisoftware.wrapper.WrapperStartStopApp.start(WrapperStartStopApp.java:544)
2023/02/17 10:39:38 | WrapperManager Error: 	at org.tanukisoftware.wrapper.WrapperManager$11.run(WrapperManager.java:4497)
2023/02/17 10:39:38 | WrapperManager Error: Caused by: java.lang.NumberFormatException: For input string: "start_class{/start_method}"
2023/02/17 10:39:38 | WrapperManager Error: 	at java.base/java.lang.NumberFormatException.forInputString(NumberFormatException.java:65)
2023/02/17 10:39:38 | WrapperManager Error: 	at java.base/java.lang.Integer.parseInt(Integer.java:652)
2023/02/17 10:39:38 | WrapperManager Error: 	at java.base/java.lang.Integer.parseInt(Integer.java:770)
2023/02/17 10:39:38 | WrapperManager Error: 	at java.base/java.text.MessageFormat.makeFormat(MessageFormat.java:1449)
2023/02/17 10:39:38 | WrapperManager Error: 	... 7 more
2023/02/17 10:39:39 | <-- Wrapper Stopped
0 Helpfuls
  • 1,564 Views
3 REPLIES 3

Abdul Khan4
Kilo Guru

‎07-18-2023 11:35 PM - edited ‎07-18-2023 11:35 PM

Did you get resolution of this issue

0 Helpfuls

Sukirti
Tera Contributor

‎07-19-2023 04:54 AM

Hello Oliver,

 

Did you get any resolution for this. I am facing the same issue in my instance and need a fix ASAP. It will be helpful if you could the fix applied for this. 

 

Regards

0 Helpfuls

Abdul Khan4
Kilo Guru

‎07-25-2023 10:36 AM

Below response from ServiceNow. It resolves my issue.

 

It seems server failed the auto upgrade with a java error, this is fairly common and is sometimes caused by a http error. Please refer KB to manual upgrade or steps provided below.

1. Login to the host machine for mid-server.
2. Try using .zip download procedure file from the instance MID server/ Downloads on the host machine. Download the required zip file suitable for your MID server.
3. Rename the old agent folder to agent_old_DO_NOT_RUN and copy the new agent into the mid-server folder
4.Copy following files from old agent folder to the newly created agent folder.
config.xml, warpperovveride.conf and cacerts files
wrapperoverride.conf will be under \agent\conf\
cacerts file will be under agent\jre\lib\security
5.Once above 3 files are copied from old agent folder to the new agent folder, start MID server service
6. Back in the instance, once MID server status is UP, perform Invalidate and then after sometime do validate