QA MID Server Not Coming Up Properly | Missing snc-automation-api.jar

[deebika019]

I am facing an issue with a QA MID Server that is not coming up properly.

Observations:
The QA MID Server is not starting/connecting successfully.
I noticed that the snc-automation.jar file is missing from the active lib directory.
The server contains both lib and lib_old folders, and the JAR file exists in lib_old but not in lib.
I also found multiple folders such as bin, bin_old, lib, and lib_old.
We were advised to verify the JDK installation and version.
Additionally, the DEV and QA MID Servers have the same hostname and IP address configured in their respective instances. Dev mid server is working fine; QA mid server is not working fine.

Dev JDK version: 

OpenJDK 21.0.7

QA JDK version:

OpenJDK 17.0.12

Questions:

• Is the missing snc-automation.jar file a known issue, and what is the recommended way to restore it?
• Are there any recommended troubleshooting steps to validate the MID Server installation and startup process?
• Is there any ServiceNow documentation or KB article related to this scenario?

[drbob]

Gut feeling on the missing file - an upgrade that crashed out. Does the appearance of the error  coincide with a platform upgrade ?

You could try copying the file in from another MID server install. If it's just missing binaries and the config is intact that _should_ work ...but I usually just reinstall that MID - unless you need the logs or are using it for file export there are no important files in the directory structure and the config file would be re-build during the install process...

1) Uninstall the service - there should be a batch file to do that in the remaining directory files, if not you can do it with Windows commands.
2) Blow away the whole directory structure

3) Run the installer

This will also clean things up if the MID server has been around a long time (I have seen discrepancies between one that has upgraded multiple times and a new install).

You don't need to do anything with the MID Server record in ServiceNow - the new install will re-attach to the same record (assuming you give it [the MID server service] the same name) and you can just validate it when it comes live (saves re-building schedules).

[drbob]

"the DEV and QA MID Servers have the same hostname and IP address configured in their respective instances"

I see no issue with that as long as they are distinct installs and thus separate services running on that host. I've seen 20 MID servers across 3 instances all running happily on the same MID server host system.

The different JDK versions (assuming you are checking the one within the MID server install directory structure) would point back at a failed upgrade.