Two digit error codes (FAX)

Code 

Description 

X0 

Short description: call collision in layer 7 

May be caused by: sending a document with UTF, UIF or UFI 

Technical description: A channel that starts sending a fax detected an incoming fax call. The transmission is stopped and the incoming fax will be received. KCS retries to send the stopped message later. 

End-user description: The fax channel was occupied by an incoming call. KCS retries to send the message later. 

X1 

Short description: attempt to send an empty document 

May be caused by: sending a document with UTF, UIF or UFI 

Technical description: A document without image blocks or text lines has been sent. This should not happen because typically all documents will have at least a cover sheet. 

End-user description: The sending document was empty. Sending of empty documents via fax is not supported. 

X2 

Short description: error when opening back-received file 

May be caused by: sending a document with UTF, UIF or UFI 

Technical description: An error occurred during opening the back reception file. This may be caused by the following reasons:
(1) Wrong configuration. Check the back reception drive and number series in configuration lines 19 and 20 

(2) The next 10 references according to the back reception number series cant be used, because a none delete able file with that name already exists. Corrective action: Increase the cycle and/or keep always value for the used number series. 

End-user description: The transmission of the fax was not possible due to a temporary problem on the local KCS server. Try to re-send the message and contact the administrator. 

X3 

Short description: error in back reception 

May be caused by: sending a document with UTF, UIF or UFI 

Technical description: An error occurred while writing the back reception file. This may happen if the disk gets full while sending a very large file with back-reception. Check the available disk space and delete unused files. Check the settings of the number series. 

End-user description: The document could not be send because there is not enough free disk space on the KCS server to save the sending copy. Contact the administrator to fix the problem. 

X5 

Short description: error during reception 

May be caused by: receiving a document with UTF, UIF or UFI 

Technical description: Reception has been stopped because the KCS disk space limit was reached. 

End-user description: Reception has been stopped because the KCS disk space limit was reached. 

X6 

Short description: could not create inbound/scan/routing send order 

May be caused by: receiving a document with UTF or UIF 

Technical description: A incoming call failed, due a wrong received number (e.g. DID/DDI or DTMF input). The calling user will be informed with 3 peeps. In that case, no reception file will be created. The error is used intern and is only visible in the fax log entries in the short term archive. 

End-user description: End user will never get this error. 

XA 

Short description: call collision in layer 6 

May be caused by: sending a document with UTF, UIF or UFI 

Technical description: A channel that starts sending a fax detected an incoming fax call. The transmission is stopped and the incoming fax will be received. KCS retries to send the stopped message later. 

End-user description: The fax channel was occupied by an incoming call. KCS retries to send the message later. 

XB 

Short description: data error within TCI-block 

May be caused by: sending a document with UTF, UIF or UFI 

Technical description: The sending document contains a corrupted TCI block with invalid characters or a TCI block that does not end with a comma. 

End-user description: The sending document contains a bad image block. Try to send to message again. Contact the administrator, if the problem still exists. 

XC 

Short description: form buffer is out of memory 

May be caused by: sending a document with UTF, UIF or UFI 

Technical description: An overlay exceeds the maximum available overlay buffer. Overlays are typically used in cover sheets. They are stored as 1 dimensional Huffman code (like TCI code). Try to simplify the overlay images. 

End-user description: The message could not be sent because it contained too many or too large overlays. 

XF 

Short description: No answer from distant station (ring detected) 

May be caused by: sending a document with UTF on an analogue or E&M line 

Technical description: If an analogue line is used, the call progress will be detected using an in band ring and busy tone detector. If this detector recognizes at least 10 ring tones the transmission will be stopped with this error. 

End-user description: The distant fax machine did not answer the call. This typically happens if the number is wrong or the distant fax is out of order (e.g. out of paper). 

XG 

Short description: receiver not ready timeout (ECM) 

May be caused by: sending a document with UTF or UIF 

Technical description: An partial ECM page (up to 64kbyte of data) is not confirmed by the receiver within 60s. This may happen if the receiver has a problem storing the received data.  

End-user description: The transmission of the fax was not successfully due to a temporary problem with the receiving fax machine. Try to re-send the message. 

XH 

Short description: line occupied by local Telefax unit 

May be caused by: sending a document with UTF using TS29 + TS2X 

Technical description: The local connected fax machine occupies the line. 

End-user description: The local connected fax machine occupies the line. Try to re-send the message. 

XI 

Short description: error in selection number
May be caused by: sending a document with UTF, UIF or UFI 

Technical description: The fax receiver number contains invalid characters. 

End-user description: The fax receiver number contains invalid characters. 

XJ 

Short description: no dial tone 

May be caused by: sending a document with UTF 

Technical description: No dial tone has been detected. Check if the fax line is OK and connected with the KCS (line) server. 

End-user description: No dial tone has been detected. Check if the fax line is OK and connected KCS (line) server. 

XK 

Short description: answer back mismatch 

May be caused by: sending a document with UTF, UIF or UFI 

Technical description: You have specified an answerback verification in the number that does not match with answerback of the received fax machine. 

End-user description: You have specified an answerback verification in the number that does not match with answerback of the received fax machine.  

XL 

Short description: no fax machine detected 

May be caused by: sending a document with UTF, UIF or UFI 

Technical description: The call has not been answered by a fax machine. This typically happens if the number is wrong and the call is answered by a distant person or answering machine. 

End-user description: The call has not been answered by a fax machine. Check if the number is correct (try to call the number with a telephone) and then try to send again. 

XM 

Short description: illegal identification of called station 

May be caused by: sending a document with UTF or UIF 

Technical description: The receiver is a fax machine that is not compatible to receive a fax according to recommendation ITU-T T.30.  

End-user description: The receiver is a fax machine that is not compatible to receive a fax. 

XN 

Short description: illegal response during training phase 

May be caused by: sending a document with UTF or UIF 

Technical description: The T.30 training (DCS+TCF) has been terminated due to a response from the receiver that is not allowed according to recommendation ITU-T T.30. 

End-user description: The transmission of the fax was not successfully due to a temporary problem with the receiving fax machine. Try to re-send the message. 

XO 

Short description: three learn attempts unsuccessful 

May be caused by: sending a document with UTF or UIF 

Technical description: The receiving fax machine did not respond to the training sequence (DCS+TCF) even after 2 retries (see decision “3^rd TRY” in ITU-T Figure 5-2a/T.30). This may typically happen if the receiving fax machine disconnects the line during training. 

End-user description: The transmission of the fax was not successfully due to a temporary problem with the receiving fax machine. Try to re-send the message.  

XP 

Short description: illegal page confirmation 

May be caused by: sending a document with UTF or UIF 

Technical description: The receiving fax machine did not respond to the end of page command (MPS, EOP and EOM) according to recommendation ITU-T T.30.  

End-user description: The transmission of the fax was not successfully due a temporary problem with the receiving fax machine. Try to re-send the message. 

XQ 

Short description: page transmitted incorrectly 

May be caused by: sending a document with UTF, UIF or UFI 

Technical description: A page has been rejected with the T.30 responds RTN. 

End-user description: The transmission of the fax was not successfully due to bad line quality. Try to re-send the message. 

XR 

Short description: illegal frame received 

May be caused by: sending a document with UTF or UIF 

Technical description: The receiving fax machine did not respond to the training (DCS + TCF) according to recommendation ITU-T T.30.  

End-user description: The transmission of the fax was not successfully due to a temporary problem with the receiving fax machine. Try to re-send the message. 

XS 

Short description: unable to find appropriate baud rate 

May be caused by: sending a document with UTF or UIF 

Technical description: The receiver responded with FTT (failure to train) to a training with the lowest compatible speed (= V.27 with 2400 bps). KCS does not retrain in that case because it is better to re-connect to the distant fax machine (see decision “RETRAIN” in ITU-T Figure 5-2a/T.30). This may happen if the line quality is very bad.  

End-user description: The transmission of the fax was not successfully due to a temporary problem with the receiving fax machine. Try to re-send the message. 

XT 

Short description: no response received 

May be caused by: sending a document with UTF, UIF or UFI 

Technical description: The receiving fax machine did not respond to the end of page command (MPS, EOP or EOM).  

End-user description: The transmission of the fax was not successfully due to a temporary problem with the receiving fax machine. Try to re-send the message. 

XU 

Short description: busy or no dial tone on PBX connection 

May be caused by: sending a document with UTF 

Technical description: If an analogue line is used, the call progress will be detected using an in band busy and ring tone detector. If this detector recognizes a busy tone after the number is dialed the transmission will be stopped with this error.  

End-user description: The telephone line to the distant fax machine is busy. Try to re-send the message. 

XV 

Short description: unexpected end of document 

May be caused by: receiving a document with UTF or UIF 

Technical description: The sending fax machine disconnects the line instead of sending a further page. This may be caused by:
1.) A none T.30 confirm protocol implementation of the sending fax machine. 

2.) The sending fax machine has stopped sending due to manual inventions or due to a bad transmitted previous page. (e.g. KCS as sender will do this if the break page is not configured in configuration line 57) 

End-user description: The reception of the fax was not successfully due to a temporary line problem or the transmission has been stopped by the sending side. If the received document is not complete, the sender will likely retransmit it because missing pages have not been confirmed to the transmitter. 

XW 

Short description: too many line distortions at training sequence 

May be caused by: receiving a document with UTF or UIF 

Technical description: KCS responded with FTT (failure to train) with the lowest compatible speed (= V.27 with 2400 bps). This may happen if the line quality is very bad. 

End-user description: The reception of the fax was not successfully due to a temporary line problem or the transmission has been stopped by the sending side. If the received document is not complete, the sender will likely retransmit it because missing pages have not been confirmed to the transmitter. 

XX 

Short description: illegal identification received 

May be caused by: receiving a document with UTF, UIF or UFI 

Technical description: The sending fax machine starts with the T.30 procedure with a wrong command (training sequence with DCS was expected). If you get the error with a specific fax machine, you should report in to Kofax support. 

End-user description: If you get this error the receiver will retry to send you the message. 

XY 

Short description: no command received 

May be caused by: receiving a document with UTF, UIF or UFI 

Technical description: KCS expects any T.30 command from the sending fax machine but did not received it within the command reception time-out (configured in pos 2 of configuration line 73). See decision “COMMAND REC?” in ITU-T Figure 5-2b/T.30. This time-out typically happens if the connection to the sending fax machine gets lost during reception or if the line quality is very bad. 

End-user description: The reception of the fax was not successfully due to a temporary line problem or the transmission has been stopped by the sending side. If the received document is not complete, the sender will likely retransmit it because missing pages have not been confirmed to the transmitter. 

XZ 

Short description: illegal command received 

May be caused by: receiving a document with UTF or UIF 

Technical description: The distant fax has sent a T.30 command that is not valid in the current state. 

End-user description: The reception of the fax was not successfully due to a temporary line problem or the transmission has been stopped by the sending side. If the received document is not complete, the sender will likely retransmit it because missing pages have not been confirmed to the transmitter. 

Y0 

Short description: the receiving fax machine does not support fax sub-addresses 

May be caused by: sending a document with UTF or UIF 

Technical description: A Fax sub address is specified, but the receiving fax machine does not support reception of fax sub addresses. 

End-user description: A Fax sub address is specified, but the receiving fax machine does not support reception of fax sub addresses. Remove the fax sub address and try again. 

Y1 

Short description: the specified fax sub address is too long (max. 20 digits are allowed) 

May be caused by: sending a document with UTF or UIF 

Technical description: A fax sub address with more than 20 digits was specified. According to ITU-T.30 the maximum number of fax sub address digits is restricted to 20. 

End-user description: The document could not be sent, because the fax sub address was longer than 20 characters. Reduce the fax sub address length and try again.