Main Class "com.softworks.dls.app.ROESSAServer" could not be loaded - ROES Server
ROES Server Main Class Error from Cached JAR File
Use this article when ROES Server fails to launch with a Main Class error and the cached ROESSAServer.jar file may be zero KB or corrupt.
If this image does not display, open it directly: MainClass_Error_ROESServer.gif
Overview
This error can occur when the cached ROESSAServer.jar file is zero KB or otherwise damaged. Quit the running ROES process, remove the bad cached file, and relaunch so ROES can download or rebuild the needed cache.
Before You Begin
Quit the ROESWebStart process in Windows Task Manager, or Force Quit ROESEngine on Mac, before deleting cached files.
PC Fix
Quit ROESWebStart
Open Task Manager and quit the ROESWebStart process if it is running.
Open the ROES Server release cache
Browse to the ROES Server cache release folder:
Check ROESSAServer.jar
Look for ROESSAServer.jar. If the file size is zero KB, delete that file.
Relaunch ROES Server
Launch ROES Server again and confirm the error is cleared.
Mac Fix
Force Quit ROESEngine
Force Quit ROESEngine if it is running.
Open the ROESEngine cache folder
Use Go to Folder and enter:
Find ROESSAServer.jar
Look through the numbered or lettered folders until you find the folder containing ROESSAServer.jar.
Delete the zero KB JAR file
If ROESSAServer.jar has a file size of zero KB, delete it.
Relaunch ROES Server
Launch ROES Server again and confirm the error is cleared.
Second Solution
A quicker option is to delete the contents of the SWROES folder on Windows or the .ROESEngineCache folder on Mac, then relaunch ROES Server.
Expected Result
After the zero KB or corrupt cached JAR file is removed, ROES Server should relaunch and rebuild the needed cache without the Main Class error.
Escalation Notes
- Confirm the running ROES process was fully quit before deleting cache files.
- Confirm ROESSAServer.jar is zero KB before deleting only that file.
- If deleting only the JAR does not resolve it, delete the contents of the platform cache folder and relaunch.
- If the issue persists after cache deletion, gather the launch error details and platform information.