Troubleshooting: java.io.FileNotFoundException classes.jsa

In Liquibase Enterprise 9.x installations we have seen instances of this error:

Caused by: java.io.FileNotFoundException: C:\Users\Administrator\LiquibaseDesktop\jre\bin\server\classes.jsa (The system cannot find the file specified)

This issue is likely related to your machine's environment, with another application interfering with writing or accessing the Java Class Data Sharing archive file (jre\bin\server\classes.jsa).
 
One root cause for this issue may be the Dynatrace OneAgent - there is a known compatibility issue between Dynatrace OneAgent and classes.jsa. More details can be found here: OneAgent Process Injection Incompatibility with classes.jsa (ONE-19712)

Troubleshooting Steps:

1. Check whether Dynatrace OneAgent is installed:

   1. Look for a service named "Dynatrace OneAgent"

   2. Check for a directory such as C:\Program Files\dynatrace\oneagent or C:\apps\dynatrace-oneagent\agent

2. If Dynatrace OneAgent is running, perform all of these steps (Note: just stopping service is not sufficient):

   1. Temporarily stop the Dynatrace OneAgent service.

   2. Rename the Dynatrace OneAgent directory.

   3. Install Liquibase.

   4. Once the installation has completed successfully, rename the directory back to its original name and restart the Dynatrace service.

Additional Troubleshooting Steps if Dynatrace OneAgent is not installed

1. Check whether Windows Defender is running

   1. If running, the following command can check for detections

      Get-MpThreatDetection | Sort-Object InitialDetectionTime -Descending | Select-Object -First 5

2. Check for third-party security software

   Get-ItemProperty HKLM:\Software\Microsoft\Windows\CurrentVersion\Uninstall\* | Select-Object DisplayName, Publisher | Sort-Object Publisher | Where-Object { $_.DisplayName -ne $null }

   1. These items could potentially be culprits:

      • Dynatrace OneAgent

      • CrowdStrike Falcon

      • SentinelOne

      • Carbon Black

      • Trend Micro

      • Cylance

      • Sophos

      • McAfee/Trellix

3. If the culprit cannot be identified from the installed software list, run Process Monitor (ProcMon) filtered on Path contains .jsa while reproducing the error — the Process Name column will show exactly what is intercepting the write.