Won't Launch - "Unable to start ROESEngine:\n\nCan't start application" - ROES Server
ROES Server Corrupted XML in Printers, Queues, or Workflows
Use this article when ROES Server fails to start and displays an application error, usually caused by a corrupted XML file in the Printers, Queues, or Workflows folders.
Application Error Example
The error may appear similar to the example below.
Overview
If ROES Server encounters this issue, check for a corrupted XML file in the Printers, Queues, or Workflows folders. The quickest recovery is to restore known-good versions of those files from a backup of the ROES Server folder.
Solution
Locate a known-good backup
Use a backup of the .ROESServer folder, or a similarly named folder such as ROESSAS or ROESSAR.
Replace files from backup
Replace the files in the current Printers, Queues, or Workflows folders with the matching files from the good backup.
Restart or retest ROES Server
After replacing the corrupted file or files, relaunch or retest ROES Server to confirm the issue is resolved.
If No Backup Exists
If there is no good backup available, the affected Printer/Agent, Queue, or Workflow must be recreated.
Folders to Check
- Printers
- Queues
- Workflows
Expected Result
Once the corrupted XML file is replaced with a known-good backup copy, ROES Server should be able to load the affected printer/agent, queue, or workflow normally.
Escalation Notes
- Ask whether a recent backup of the ROES Server folder exists.
- Check the Printers, Queues, and Workflows folders for the likely corrupted XML file.
- Restore only from a backup known to be good.
- If no backup is available, recreate the affected printer/agent, queue, or workflow.