Windows
Install Failures
The ROES Client may fail to install and launch on occasion. The causes can vary based
on operating system or other factors external to your system. The native launch.msi file is a true Windows installer file
and is secure signed by our company. Some antivirus software may not consider our company name to be 'commonly found' in
their application install list so could flash an alert about this. An installation guide can be
found here. The install
may fail if some portions of the process fail, and starting fresh is the best bet. To do this, click Start and type in the field
that appears just above it C:\ProgramData and press Enter. Scroll down in the window that opens to find the SWROES folder and
delete it. Then re-execute the launch.msi file.
Launch Failures
After installation and even some use, the ROES Client
may fail to launch. If you have run ROES on the system before, then it's possible a saved setting is the issue and cleaning
up to start fresh is the best bet. First, open an Explorer window (click Start and Computer) and choose C: drive, then Users
(or Documents and Settings for XP) and go into your user account folder. Find the .roescache folder and permanently delete it
(this may take some time), then see if ROES launches. If it still fails, in the same user login folder look for the folder starting
with a period that applies to your lab/their ROES. In that folder will be a file of the same name as the folder ending in .properties.
Delete this .properties file, which stores old/saved preferences, and then try the launch again.
Order Completion
Failures
The ROES Client may fail to complete your order for reasons usually involving the image files used. First, be sure
that all images used in the order have not been moved (such as removing a CD or USB drive) or renamed since being added to the
order in ROES. The files are not physically added into the order for the lab until you finish the order completion steps prior
to transmission. Second, beware of using any characters or punctuation in the file names you use. Parentheses, apostrophes,
quotes, copyright signs and other hotkey characters should be avoided at all times.
Common Order Transmission
Failure
The most current send issue is with FTP and Java 7 or higher. Java changed their FTP calls in version 7, and in Windows, due
to a bug in the operating system (specifically Windows Firewall), FTP fails immediately. Many labs have changed to a new transmission
method ROES offers, however most are still using the usually reliable FTP. You can try the following steps if the Uploads pane
shows the failure immediately.
Turn off the problem issue in Windows Firewall, which can be done via the following steps:
Click
Start in Win 7/Vista, then choose All Programs, Accessories, and right-click on Command Prompt.
Choose Run as Administrator in the
list and the black command window will open. At the prompt type:
netsh advfirewall set global StatefulFTP disable
and press Enter. An
'OK' should appear below it and bounce back to a prompt. Then type
exit
and press Enter to formally quit the window. After that ROES
orders should send OK via FTP. The command simply turns off a check in Windows Firewall that is causing the issue.
Render Failures
When
using the Render button in the cart pane, larger products like book spreads with multiple images or wide format items may fail
to produce flattened images. This is almost always a memory allocation issue. If you are in 32 bit Windows such as XP,
able to overcome this issue easily as the maximum memory is not very high. If you are in 64 bit Windows, you may be running
the older installation in Java that is not using a very high memory allocation. Remove the current desktop icon and visit the
lab page for the ROES Client, which should give you the ability to use the native installer via the launch.msi file. Once it
finishes and opens, this should then allow you to return to the saved order and render the items.
