Fails to Relaunch - ROES Server
Fails to Relaunch - ROES Server
Use this article when ROES Server will not relaunch because of a database issue, corrupted file, incomplete working order, or damaged server configuration file.
Overview
A ROES Server relaunch failure can happen when the server cannot read or process something in the database, a working order, or one of the XML/configuration files. Start with the database tables because that is usually the easiest test. If the server still will not relaunch, move on to checking working order files and configuration files.
Symptoms
- ROES Server fails to relaunch after shutting down or restarting.
- ROES Server may be unable to digest a corrupted file.
- A file in the Printers, Queues, Workflows, .ROESServer, or Working Files folder may be 0 KB or contain repeated null values.
- An incomplete order may leave a .ro file and matching order folder in the Working Files directory.
Before You Begin
- Confirm the ROES Server computer and the location of the .ROESServer folder. The folder may have a similar but different name; like .ROESSA or .ROESSAS
- If available, locate a recent backup of the .ROESServer folder.
- Preserve questionable files and folders by moving them to a holding folder instead of deleting them.
- If you cannot launch ROES Server to use the tools under the Data tab, use a secondary ROES Server or a database manager when clearing database tables. (This article shows how to use the HSQL DB Manager
Important Recovery Note
Do not permanently delete server configuration files, working orders, printer definitions, queues, or workflow files while troubleshooting. Move files out of the active folder first so they can be restored if needed.
Solution
Try the database repair first
Clear the following tables in the database, then attempt to relaunch ROES Server:
- Coordinator
- EnsembleListeners
- Queues
If ROES Server cannot launch
If you cannot launch ROES Server to use the tools under the Data tab, clear the tables from a secondary ROES Server or use a database manager.
If the database repair does not work, check for corrupted files
Look for files in the Printers, Queues, Workflows, .ROESServer, or Working Files folders that are 0 KB or are filled with null values when opened in a text editor.
Rename the Working Files folder
As an easy first file test, rename the Working Files directory by adding a single character to the folder name. This prevents ROES Server from finding that folder and trying to read any order files inside it.
If ROES Server launches after renaming Working Files
- The issue is likely in the Working Files directory.
- Usually the last order processed, or the last order ROES Server attempted to process, is the problem.
- Open the Working Files directory and sort by Date Modified.
- Look for .ro files and a folder with the same name as the .ro file.
- If there are no .ro files, move the two newest folders out of Working Files and try to relaunch again.
Remove or replace SARPreferences.xml
If Working Files is not the issue, move SARPreferences.xml out of the .ROESServer folder and attempt to relaunch.
If ROES Server launches after removing SARPreferences.xml
- If the Server UI asks for a login, use admin and labkey.
- Replace the bad file with the copy from a recent backup, if available.
- If no backup is available, the server settings will need to be re-entered. Refer to the ROES-U quick start setup reference: ROES Server Quick Start Setup.
- Any configuration changes made after the backup was created must be manually updated. This includes most tabs, with the exception of the Production tab.
Remove, rename, or replace Printers, Queues, and Workflows
If the server still will not relaunch, test the Printers, Queues, and Workflows folders one at a time by moving the folder out of .ROESServer or adding a character to the folder name.
Isolation process
- Start with the Printers folder, then attempt to relaunch.
- If ROES Server launches, the issue is likely one of the XML files in that folder.
- Move all XML files out of the folder, then add them back one at a time and relaunch after each file to identify the bad file.
- If the Printers definitions have not changed since the last backup, replace the folder with the backup copy instead. If no backup is available, recreate the printer or agent and refer to the ROES-U printer/agent examples: ROES Server Printers List.
- Repeat the same process with the Printers and Workflows folders.
Use a full .ROESServer folder isolation if needed
As a broader isolation step, move all files from the .ROESServer folder into a subfolder and try relaunching ROES Server. This can help confirm whether a file inside .ROESServer is blocking launch.
Related References
- ROES Server Quick Start Setup — reference for re-entering server settings when no backup of .ROESServer is available.
- ROES Server Printers List — reference examples for recreating printers or agents when printer definitions must be rebuilt.
Expected Result
After the database table issue, working order issue, or corrupted configuration file is isolated and removed or replaced, ROES Server should relaunch normally. Any files or folders removed during testing should be restored from a known-good backup or rebuilt manually as needed.
Escalation Notes
- Record whether clearing Coordinator, EnsembleListeners, and Queues allowed the server to relaunch.
- Record which folder or file was moved, renamed, removed, or restored from backup.
- Check for 0 KB files or files filled with null values.
- Preserve any suspect Working Files orders, .ro files, XML files, and backups for review.
- If no backup exists, note which settings, printer definitions, queues, or workflows may need to be recreated manually.