Troubleshoot common exceptions

Last updated: August 2025

📄️ Auto session renewal failure

Katalon Studio sessions are authenticated using refresh tokens that periodically expire for security reasons. When a refresh token expires, your session ends automatically, and you are required to relogin. This ensures account security and prevents unauthorized long-term access.

📄️ Error exporting test artifacts in Katalon Studio

When exporting test artifacts in Katalon Studio, the following error can occur:Error exporting test artifacts{"\n"}Cannot invoke "java.io.File.getAbsolutePath()" because the return value of "com.katalon.platform.api.model.TestCaseEntity.getScriptFile()" is null{"\n"}

📄️ Failed to activate Katalon Runtime Engine license

This document explains troubleshooting methods to these errors when using Katalon Runtime Engine - Local:

📄️ "java.lang.NoClassDefFoundError: javax/xml/bind/JAXBException" error

You might encounter this error message javax/xml/bind/JAXBException.

📄️ Letter case changes in object names not synced

When renaming an object by changing the letter case, these changes are not reflected in your local file or in the Git repository after committing. As a result, tests may fail with errors such as:Test object with id '[Object Repository Path]' does not exist

📄️ "bind(): failed Cannot assign requested address (99)" when running Katalon Docker Image

During test startup or browser initialization, you may encounter the bind() failed: Cannot assign requested address (99) error when executing tests with Katalon Docker Image (KDI), especially in CI environments.

📄️ Logout due to inactivity

Katalon Studio automatically logs out inactive users after a certain period of time. This timeout mechanism protects your account by preventing unauthorized access in case you leave your session idle. When this happens, you are required to log in again before continuing your work.

📄️ "NoClassDefFoundError" error with Cucumber in Katalon Test Execution - Local

When running Cucumber tests in Katalon Test Execution - Local, you may encounter:

📄️ Session has been terminated: Your account has been logged in on another machine

When you log in to Katalon Studio using a license on one machine and then attempt to use the same license on another machine, the first session is automatically terminated. This prevents simultaneous use of the same license across multiple environments.

📄️ Unable to log in or activate Katalon Studio

There are a few possible reasons why you are unable to log in or activate Katalon Studio. Refer to the following reasons and solutions.

📄️ Unable to open project: Resource Exception

You encounter the following message in Katalon Studio Resource ExceptionThis issue might happen because Katalon Studio fails to read the project description file (.project).

📄️ Unable to open the Katalon Studio application

You are unable to open the Katalon Studio application on Windows machine and might encounter the following error\Users\Laxmi.Kadam\Downloads\Katalon Studio Windows64-9.4.0\Kat{"\n"}alonStudioWindows64-9.4.0\config\.metadata\log.

📄️ Unable to record web scripts on a VDI machine

On a virtual desktop infrastructure (VDI) machine, you may not be able to record web scripts using Chrome or Edge Chromium browsers. When attempting to do so, you may encounter errors such as:

📄️ Unable to send RESTful requests with client certificate in Katalon Studio

When trying to send RESTful requests using a client certificate, you may encounter the following error:Could not initialize class org.apache.commons.ssl.KeyMaterial

📄️ How to resolve Katalon Studio crashing frequently?

Condition

📄️ Resolve Katalon Studio Hanging and Crashing

Users may experience Katalon Studio randomly hanging and crashing. Similar symptoms include Groovy script syntax highlighting disappearing, or the code in Script Mode appearing entirely white (no colors). These indicate that Katalo Studio is hanging and about to crash.