If an error code occurs, retry the communication. If the same problem occurs, try to fix the problem as suggested below. Note that some error codes appear only in the error code display and on the service report.
Code | Meaning | Suggested Cause/Action |
---|---|---|
0-00 | DIS/NSF not detected within 40 s of Start being pressed |
|
0-01 | DCN received unexpectedly |
|
0-03 | Incompatible modem at the other end | The other terminal is incompatible. |
0-04 | CFR or FTT not received after modem training |
Cross reference
|
0-05 | Modem training fails even G3 shifts down to 2400 bps |
Cross reference See error code 0-04. |
0-06 | The other terminal did not reply to DCS |
Cross reference See error code 0-04. |
0-07 | No post-message response from the other end after a page was sent |
|
0-08 | The other end sent RTN or PIN after receiving a page, because there were too many errors |
Cross reference
|
0-14 | Non-standard post message response code received |
Cross reference See error code 0-08. |
0-15 | The other terminal is not capable of specific functions. | The other terminal is not capable of accepting the following functions, or the other terminal’s memory is full.
|
0-16 | CFR or FTT not detected after modem training in confidential or transfer mode |
Cross reference See error code 0-08. |
0-17 | Communication was interrupted by pressing the [Stop] key | If the [Stop] key was not pressed and this error keeps occurring, replace the operation panel or the operation panel drive board. |
0-20 | Facsimile data not received within 6 s of retraining |
Cross reference
|
0-21 | EOL signal (end-of-line) from the other end not received within 5 s of the previous EOL signal |
Cross reference Maximum interval between EOLs and between ECM frames - G3 Switch 0A, bit 4 |
0-22 | The signal from the other end was interrupted for more than the acceptable modem carrier drop time (default: 200 ms) |
Cross reference Acceptable modem carrier drop time - G3 Switch 0A, bits 0 and 1 |
0-23 | Too many errors during reception |
Cross reference
|
0-29 | Data block format failure in ECM reception |
|
0-30 | The other terminal did not reply to NSS(A) in AI short protocol mode. |
Cross reference Dedicated tx parameters - Section 4 |
0-32 | The other terminal sent a DCS, which contained functions that the receiving machine cannot handle. |
|
0-33 | The data reception (not ECM) is not completed within 10 minutes. |
|
0-52 | Polarity changed during communication |
|
0-55 | FCU does not detect the SG3. |
|
0-56 | The stored message data exceeds the capacity of the mailbox in the SG3. | SG3 firmware or board defective. |
0-70 | The communication mode specified in CM/JM was not available. (V.8 calling and called terminal) |
|
0-74 | The calling terminal fell back to T.30 mode, because it could not detect ANSam after sending CI. |
|
0-75 | The called terminal fell back to T.30 mode, because it could not detect a CM in response to ANSam (ANSam timeout). |
|
0-76 | The calling terminal fell back to T.30 mode, because it could not detect a JM in response to CM (CM timeout). |
|
0-77 | The called terminal fell back to T.30 mode, because it could not detect a CJ in response to JM (JM timeout). |
|
0-79 | The called terminal detected CI while waiting for a V.21 signal. |
|
0-80 | The line was disconnected due to a timeout in V.34 phase 2 – line probing. |
If these errors happen at the transmitting terminal:
If these errors happen at the receiving terminal:
|
0-81 | The line was disconnected due to a timeout in V.34 phase 3 – equalizer training. | |
0-82 | The line was disconnected due to a timeout in the V.34 phase 4 – control channel start-up. | |
0-83 | The line was disconnected due to a timeout in the V.34 control channel restart sequence. | |
0-84 | The line was disconnected due to abnormal signaling in V.34 phase 4 – control channel start-up. |
|
0-85 | The line was disconnected due to abnormal signaling in V.34 control channel restart. |
|
0-86 | The line was disconnected because the other terminal requested a data rate using MPh that was not available in the currently selected symbol rate. |
|
0-87 | The control channel started after an unsuccessful primary channel. |
|
0-88 | The line was disconnected because PPR was transmitted/received 9 (default) times within the same ECM frame. |
|
2-11 | Only one V.21 connection flag was received | Replace the FCU. |
2-12 | Modem clock irregularity | Replace the FCU. |
2-13 | Modem initialization error |
|
2-22 | Counter overflow error of JBIG chip | If error occurs frequently, change the settings for resolution, paper size, compression type. |
2-23 | JBIG compression or reconstruction error | Turn off the machine, then turn it back on. |
2-24 | JBIG ASIC error | Turn off the machine, then turn it back on. |
2-25 | JBIG data reconstruction error (BIH error) |
|
2-26 | JBIG data reconstruction error (Float marker error) | |
2-27 | JBIG data reconstruction error (End marker error) | |
2-28 | JBIG data reconstruction error (Timeout) | |
2-29 | JBIG trailing edge maker error |
|
2-50 | The machine resets itself for a fatal FCU system error | If this is frequent, update the ROM, or replace the FCU. |
2-51 | The machine resets itself because of a fatal communication error | If this is frequent, update the ROM, or replace the FCU. |
2-53 | Snd msg() in the manual task is an error because the mailbox for the operation task is full. | The user did the same operation many times, and this gave too much load to the machine. |
4-01 | Line current was cut |
|
4-10 | Communication failed because of an ID Code mismatch (Closed Network) or Tel. No./CSI mismatch (Protection against Wrong Connections) |
|
5-00 | Data reconstruction not possible | Replace the FCU. |
5-10 | DCR timer expired | Replace the FCU. |
5-20 | Storage impossible because of a lack of memory |
|
5-21 | Memory overflow | |
5-23 | Print data error when printing a substitute rx or confidential rx message |
|
5-25 | SAF file access error |
|
6-00 | G3 ECM - T1 time out during reception of facsimile data |
|
6-01 | G3 ECM - no V.21 signal was received | |
6-02 | G3 ECM - EOR was received | |
6-04 | G3 ECM - RTC not detected |
|
6-05 | G3 ECM - facsimile data frame not received within 18 s of CFR, but there was no line fail |
Cross reference Rx cable equalizer - G3 Switch 07 (PSTN) |
6-06 | G3 ECM - coding/decoding error |
|
6-08 | G3 ECM - PIP/PIN received in reply to PPS.NULL |
|
6-09 | G3 ECM - ERR received |
|
6-10 | G3 ECM - error frames still received at the other end after all communication attempts at 2400 bps |
|
6-21 | V.21 flag detected during high speed modem communication | The other terminal may be defective or incompatible. |
6-22 | The machine resets the sequence because of an abnormal handshake in the V.34 control channel |
|
6-99 | V.21 signal not stopped within 6 s | Replace the FCU. |
13-17 | SIP user name registration error |
|
13-18 | SIP server access error |
|
13-24 | SIP authentication error |
|
13-25 | Network I/F setting error |
|
13-26 | Network I/F setting error at power on |
|
13-27 | IP address setting error | IP address of the device is not registered. |
14-00 | SMTP Send Error | Error occurred during sending to the SMTP server. Occurs for any error other than 14-01 to 16. For example, the mail address of the system administrator is not registered. |
14-01 | SMTP Connection Failed |
|
14-02 | No Service by SMTP Service (421) |
|
14-03 | Access to SMTP Server Denied (450) |
|
14-04 | Access to SMTP Server Denied (550) |
|
14-05 | SMTP Server HDD Full (452) |
|
14-06 | User Not Found on SMTP Server (551) |
|
14-07 | Data Send to SMTP Server Failed (4XX) |
|
14-08 | Data Send to SMTP Server Failed (5XX) |
|
14-09 | Authorization Failed for Sending to SMTP Server |
|
14-10 | Addresses Exceeded | Number of broadcast addresses exceeded the limit for the SMTP server. |
14-11 | Buffer Full | The send buffer is full so the transmission could not be completed. Buffer is full due to using Scan-to-Email while the buffer is being used send mail at the same time. |
14-12 | Data Size Too Large | Transmission was cancelled because the detected size of the file was too large. |
14-13 | Send Cancelled | Processing is interrupted because the user pressed Stop. |
14-14 | Security Locked File Error | Update the software because of the defective software. |
14-15 | Mail Data Error |
|
14-16 | Maximum Division Number Error |
|
14-17 | Incorrect Ticket | Update the software because of the defective software. |
14-18 | Access to MCS File Error |
|
14-20 | SMTP Authentication error | Make sure the administrator's e-mail address is same as the SMTP authentication address or POP before SMTP address. |
14-21 | Transmission error of S/MIME | Register the correct user certificate and device certificate. |
14-22 | Destination certificate is invalid in S/MIME transmission. | Register the correct destination certificate. |
14-23 | Device certificate is invalid in S/MIME transmission. | Register the correct device certificate. |
14-24 | Destination and device certificate is in valid in S/MIME. | Register the correct user certificate and device certificate. |
14-30 | MCS File Creation Failed | Failed to create the MCS file because:
|
14-31 | UFS File Creation Failed | UFS file could not be created:
|
14-32 | Cancelled the Mail Due to Error Detected by NFAX | Error detected with NFAX and send was cancelled due to a software error. |
14-33 | No Mail Address For the Machine | Neither the mail address of the machine nor the mail address of the network administrator is registered. |
14-34 | Address designated in the domain for SMTP sending does not exist |
|
14-50 | Mail Job Task Error | Due to an FCU mail job task error, the send was cancelled:
|
14-51 | UCS Destination Download Error | Not even one return notification can be downloaded:
|
14-60 | Send Cancel Failed | The cancel operation by the user failed to cancel the send operation. |
14-61 | Notification Mail Send Failed for All Destinations | All addresses for return notification mail failed. |
14-62 | Transmission Error due to the existence of zero line page | When the 0 line page exists in received pages with G3 communication, the transmission is interrupted. |
15-01 | POP3/IMAP4 Server Not Registered | At startup, the system detected that the IP address of the POP3/IMAP4 server has not been registered in the machine. |
15-02 | POP3/IMAP4 Mail Account Information Not Registered | The POP3/IMAP4 mail account has not been registered. |
15-03 | Mail Address Not Registered | The mail address has not been registered. |
15-10 | DCS Mail Receive Error | Error other than 15-11 to 15-18. |
15-11 | Connection Error | The DNS or POP3/IMAP4 server could not be found:
|
15-12 | Authorization Error | POP3/IMAP4 send authorization failed:
|
15-13 | Receive Buffer Full | Occurs only during manual reception. Transmission cannot be received due to insufficient buffer space. The buffer is being used for mail send or Scan-to-Email. |
15-14 | Mail Header Format Error | The mail header is not standard format. For example, the Date line description is incorrect. |
15-15 | Mail Divide Error | The e-mail is not in standard format. There is no boundary between parts of the e-mail, including the header. |
15-16 | Mail Size Receive Error | The mail cannot be received because it is too large. |
15-17 | Receive Timeout | May occur during manual receiving only because the network is not operating correctly. |
15-18 | Incomplete Mail Received | Only one portion of the mail was received. |
15-31 | Final Destination for Transfer Request Reception Format Error | The format of the final destination for the transfer request was incorrect. |
15-39 | Send/Delivery Destination Error | The transmission cannot be delivered to the final destination:
|
15-41 | SMTP Receive Error | Reception rejected because the transaction exceeded the limit for the “Auth. E-mail RX” setting. |
15-42 | Off Ramp Gateway Error | The delivery destination address was specified with Off Ramp Gateway OFF. |
15-43 | Address Format Error | Format error in the address of the Off Ramp Gateway. |
15-44 | Addresses Over | The number of addresses for the Off Ramp Gateway exceeded the limit of 30. |
15-61 | Attachment File Format Error | The attached file is not TIFF format. |
15-62 | TIFF File Compatibility Error | Could not receive transmission due to:
|
15-63 | TIFF Parameter Error | The TIFF file sent as the attachment could not be received because the TIFF header is incorrect:
|
15-64 | TIFF Decompression Error | The file received as an attachment caused the TIFF decompression error:
|
15-71 | Not Binary Image Data | The file could not be received because the attachment was not binary image data. |
15-73 | MDN Status Error | Could not find the Disposition line in the header of the Return Receipt, or there is a problem with the firmware. |
15-74 | MDN Message ID Error | Could not find the Original Message ID line in the header of the Return Receipt, or there is a problem with the firmware. |
15-80 | Mail Job Task Read Error | Could not receive the transmission because the destination buffer is full and the destination could not be created (this error may occur when receiving a transfer request or a request for notification of reception). |
15-81 | Repeated Destination Registration Error | Could not repeat receive the transmission because the destination buffer is full and the destination could not be created (this error may occur when receiving a transfer request or a request for notification of reception). |
15-91 | Send Registration Error | Could not receive the file for transfer to the final destination:
|
15-92 | Memory Overflow | Transmission could not be received because memory overflowed during the transaction. |
15-93 | Memory Access Error | Transaction could not complete due to a malfunction of SAF memory. |
15-94 | Incorrect ID Code | The machine rejected an incoming e-mail for transfer request, because the ID code in the incoming e-mail did not match the ID code registered in the machine. |
15-95 | Transfer Station Function | The machine rejected an incoming e-mail for transfer because the transfer function was unavailable. |
22-00 | Original length exceeded the maximum scan length |
|
22-01 | Memory overflow while receiving |
|
22-02 | Tx or rx job stalled due to line disconnection at the other end |
|
22-04 | The machine cannot store received data in the SAF |
|
22-05 | No G3 parameter confirmation answer | Defective FCU board or firmware |
23-00 | Data read timeout during construction |
|
25-00 | The machine software resets itself after a fatal transmission error occurred |
|
F0-xx | V.34 modem error | Replace the FCU. |
F6-xx | SG3 modem error |
|