ROES launch hangs at Done - Content Not Allowed in Prolog - Desktop
ROES Launch Hangs at Done – Content Not Allowed in Prolog - Desktop
Use this article when ROES startup reaches Done and then hangs because a local XML file is likely corrupted.
Overview
If ROES reaches Done during startup but does not fully launch, there is likely a corrupted file in the local ROES client structure. The roeslog file in the local .labname folder should indicate which file is causing the problem. The most common files to check are customer.xml and colors.xml.
Symptoms
- ROES opens but stops or hangs at Done.
- The launch does not proceed into the normal ROES client interface.
- The roeslog contains content not allowed in prolog near the end of the log.
- The roeslog may also mention error loading customer.xml.
Before You Begin
- Close ROES completely before deleting or moving local files.
- Open the local .labname folder for the affected ROES client.
- Review the roeslog file near the end of the log for the exact error.
- If you want to preserve a suspect XML file for review, move it to the Desktop instead of deleting it.
Important Note
Delete or move only the file specifically indicated by the log first. If customer.xml is named, start there. If only content not allowed in prolog appears and no specific customer file is named, try colors.xml.
Solution
Close ROES
Exit the ROES client completely before making changes to the local client files.
Open the local .labname folder
Go to the local ROES client folder for the affected lab. This folder is commonly referred to as the .labname folder.
Review the roeslog file
Open roeslog and look near the end for entries such as content not allowed in prolog and/or error loading customer.xml.
What the log tells you
- customer.xml is specifically mentioned: remove customer.xml.
- Only content not allowed in prolog is shown: try removing colors.xml.
Remove customer.xml if it is named in the log
If the log specifically mentions customer.xml or error loading customer.xml, delete customer.xml or move it out of the folder.
Remove colors.xml if no specific file is named
If the log only shows content not allowed in prolog and does not specifically mention customer.xml, delete colors.xml or move it out of the folder.
Relaunch ROES
Open ROES again. If the corrupted file was removed, ROES should launch normally and recreate the needed local file.
Expected Result
After the corrupted customer.xml or colors.xml file is removed, ROES should pass the Done stage and continue launching normally.
Escalation Notes
- Collect the end of the roeslog showing the content not allowed in prolog error.
- Confirm whether customer.xml was specifically mentioned.
- Confirm whether customer.xml or colors.xml was deleted or moved out of the folder.
- If ROES still hangs, collect the newest roeslog after the relaunch attempt.