Reference Guide – DOC. 7150B
3-Series Control Systems
•
57
Error Handling
The following errors may be encountered during the auto-update process. If the
below solutions do not resolve the error, contact Crestron technical support.
•
File download fails: the client is unable to download the hash file or the
actual component
o
Retry the download on the next polling interval.
o
If download still fails, delete the hash file (The hash file was
downloaded but not the actual component to the update).
•
Update operations: The unzipping operation fails or the firmware
component did not get updated.
o
Retry the operation.
•
Cannot resolve hostname: The client cannot resolve the hostname.
o
Check that the target hostname is valid, and then retry resolving the
hostname on the next polling interval.
•
Cannot connect to the server/device: The client cannot connect to the
server or the device.
o
Check that the server or the device is currently accessible, and then
retry connecting to the server or the device on the next polling
interval.
A control system can handle errors in different ways depending on the
component being updated and the dependencies between the components. The
control system will do one of the following:
•
Abort the current operation.
For example, if the control system is updating a .puf component, which
has dependencies defined, and the first part of the update fails, the
control system will abort this particular component and will continue to
the next item in the manifest file.
•
Log the error and continue on to the next step.
For example, if the control system is updating EX devices with the type
"CLW-LDIMEX" and one device update fails, the controller will continue
with the next set of devices.
