MID Server Java classes missing or incompatible after upgradingIssue Customers often implement custom integrations and scripts that run in the MID Server platform, that use Java classes already present in the MID Server application. These are often 3rd party code, and implemented as .jar files in the agent/lib folder of the MID Server installation. The scripts in JavaScript Probes, MID Server Script Includes [ecc_agent_script_include],or Integration Hub actions, will then make packages calls to those classes. Between versions, ServiceNow often add, change and remove 3rd party libraries, or upgrade the versions, as and when needed. That may have been for supporting out-of-box functionality, responding to known vulnerabilities, resolving incompatibilities, or simply tidying up things no longer needed. This can break those custom scripts and cause errors.ReleaseSee versions in the lists.CauseSome recent examples of changes that may affect custom scripts include these, but there will be many more changes not listed: log4j-core.jar 2.17.1 was removed from Tokyo. Changed to using slf4j instead.jsch.jar 0.1.54 was removed from Utah. No longer supported by jGit, so not needed by Source Control.ojdbc6.jar 11.2.0.3.0 was replaced with ojdbc8.jar 19.3.0.0.0 in Quebec. This was to support more recent Oracle versions in Import Set Data Sources.oauth2-oidc-sdk.jar 6.5 upgraded to 9.10.1 in Washington, Vancouver Patch 2, Utah Patch 7, Tokyo Patch 10 Hot Fix 1a (PRB1679574), however that has caused dependency problems for OAuth/Azure authentication. oauth2-oidc-sdk.jar 9.10.1 was removed in Washington Patch 9 by PRB1812692, but does remain in Xanadu and Yokohama.adal4j.jar 1.6.4 was removed from Washington Patch 9 and Xanadu, and added back and upgraded to adal4j.jar 1.6.7 in Yokohama.This dependencies issue should all be fixed fully in Yokohama by PRB1808239. Resolution2 options: Add the Java class back into the MID Server using the supported MID Server JAR File systemhttps://docs.servicenow.com/en-US/bundle/vancouver-servicenow-platform/page/product/mid-server/task/t_SynchronizeAJARFiletoMIDServers.html Download the latest Jar from the vendor's websiteNavigate to MID Servers -> JAR Files in the instance [ecc_agent_jar]Create a new record, name it after the file, and attach the jar fileAdd a description to describe the reason for adding the jar file, to help with supporting and maintaining it in futureSave the record, and it will automatically be synchronised to all MID Servers agent/extlib folderNote: As the class is not included out-of-box, you will now be responsible for maintaining it. Upgrading to newer versions to respond to any bugs or vulnerabilities is the customer's responsibility and out of the scope of ServiceNow tech support. ServiceNow tech support may ask you to temporarily deactivate the jar file while debugging problems with out-of-box features. Modify your code to use different classes. In the case of classes with known vulnerabilities, or that are deprecated by the vendor, this is the recommended option. Note: Do not copy a jar file manually into either the lib or extlib folder. Upgrades will delete anything from lib that should not be there, and MID Server File Sync will delete anything from extlib that is not active in the ecc_aject_jar table in the instance. If you need to override an out-of-box class in lib with a different version added to extlib via the Jar files table, then the class path order can be swapped around by editing wrapper-override.conf. See KB1182832