Canon imageRUNNERC1022 Service Manual page 344

Chapter 12
Displayed log is only five latest log.
3) Select log and press [OK] button. The communication log detailed screen is displayed. (Example: No.001)
NOTE:
Press [OK] button to return to the communication log list screen.
4) When a message is displayed, take an appropriate action referring to "Error code and strings".
No.2
Symptom: A communication test results NG! even if network setting is set properly.
Causes: The network environment is inappropriate, or RGW-ADR or RGW-PORT settings for E-RDS have been changed.
Remedy: The following points should be checked.
1) Check network conditions such as proxy server settings and so on.
2) Check the E-RDS setting values.
- Check the communication log from COM-LOG.
- Check whether RGW-ADR or RGW-PORT settings has changed. If RGW-ADR or RGW-PORT settings has changed, restore initial values. For initial
values, see "E-RDS setting items".
No.3
Symptom: Registration information of an E-RDS is once deleted from the UGW server, and is re-registered after that. If a communication test is not per-
formed, then device information on the UGW becomes invalid.
Causes: When registration of the E-RDS is deleted from the UGW, the status will be changed to that the communication test has not completed because related
information has lost from a database.
So, device information will also become invalid if that condition will be left for seven days without performing the communication test.
Remedy: Perform a communication test before becoming the invalidity state.
No.4
Symptom: There was a log, indicating "Device is not ready, try later" in error details of COM-LOG list.
Cause: A certain problem occurred in networking.
Remedy: Check and take actions mentioned below.
1) Check networking conditions and connections.
2) Turn on the power supply of a device and perform a communication test about 60 seconds later.
No.5
Symptom: "Unknown error" is displayed though a communication test (COM-TEST) has done successfully.
Cause: It could be a problem at the server side or the network load is temporarily faulty.
Remedy: Try again after a period of time. If the same error persists, check the UGW status with a network and UGW administrator.
No.6
Symptom: A service call request cannot be made.
Cause: There has been already a service call request.
Remedy: Perform either of the following remedy works:
- Touch the [Cancel] button to cancel the service call request that has been made.
12-30
F-12-60
F-12-61