When a Number Preceded by "#" (Error Code) Appears
13X7-0KH
If printing or scanning was not completed properly, or sending/receiving faxes failed, a number preceded by "#" (error code) is displayed on the detailed information screen of the job log or the Communication Management Report (Printing Reports and Lists).
Some error codes may not be displayed, depending on your machine.
When receiving a document, ask the recipient to either reduce the resolution at which the document is scanned, or divide the document into two or more parts before sending it.
#005
The recipient did not answer within 35 seconds.
Confirm that the recipient's machine is able to communicate, and then try again.
The recipient is using a fax machine other than G3 type.
The document that you are sending is not placed correctly.
Place the document properly into the feeder or on the platen glass, and send again.
#012
The document could not be sent because the recipient's fax machine was out of paper.
Ask the recipient to load paper into their fax machine.
#018
The recipient's machine did not respond when your machine redialed.
Confirm that the recipient's machine is able to communicate, and then redial again.
The documents could not be sent because the recipient's machine was performing another task.
Confirm that the recipient's machine is able to communicate, and then send again.
The settings on your machine do not match the settings on the recipient's machine.
Check the settings of the recipient's machine, and then send again.
#019
Sending could not be performed because the memory of the Remote Fax server machine became full when sending a fax from the Remote Fax client machine.
Send again after sending the other documents on the Remote Fax server machine is complete.
Delete unnecessary documents and documents with errors from the Remote Fax server machine to make more memory available.
The document could not be sent because the memory of the machine is full.
Delete unnecessary documents and documents with errors to make more memory available.
When performing memory sending, the image could not be stored in the memory.
Perform memory sending again.
Send the document with direct sending.
There was a problem with the scanned image when performing direct sending.
Perform direct sending again.
#022
Forwarding could not be performed because all of the addresses stored in the specified group destination were deleted, or a Mail Box was specified as the group destination.
Re-enter the group destination, and send again.
When sending to a destination stored in the Address Book, sending could not be performed because the specified destination stored in the Address Book was deleted while the documents were waiting to be sent.
Re-enter the group destination, and send again.
Sending via fax driver is not allowed.
Set <Allow Fax Driver TX> to <On>, and then send again.
A telephone line not connected to the Remote Fax server machine was specified when sending a fax from the Remote Fax client machine.
Check the number of telephone lines for the server machine, specify the number you checked for the server machine in <Remote Fax TX Settings> on the client machine, and then send again.
Data that contains more than 1,000 pages was received.
This machine can print or store up to 999 pages of data, but will delete any data that exceeds this limit. Ask the sender to resend the remaining pages.
The image data for the document to send was not found in memory when performing delayed sending or redialing.
Scan the document and send again.
When resending the document, select the Direct Sending mode.
Sending could not be performed when sending to multiple destinations because there was insufficient memory available.
Delete unnecessary documents and documents with errors to make more memory available.
Divide the sending operation into multiple batches instead of sending the document to all destinations at once.
Lower the resolution, and then send the document again.
#040
Sending could not be performed because there was insufficient memory available in the Remote Fax server machine when sending a fax from the Remote Fax client machine.
Delete unnecessary documents and documents with errors from the Remote Fax server machine to make more memory available.
Divide the sending operation into multiple batches instead of sending the document to all destinations at once.
Lower the resolution, and then send the document again.
The document could not be sent because the memory of the machine is full.
Delete unnecessary documents and documents with errors to make more memory available.
Divide the sending operation into multiple batches instead of sending the document to all destinations at once.
Lower the resolution, and then send the document again.
#054
The sending process was interrupted because the user phone number and user name were not registered.
Register the user phone number and user name, and then send again.
A subaddress is not set in the recipient's machine.
Check the recipient's subaddress, and then send again.
#081
A password is not set in the recipient's machine.
Check the recipient's password, and then send again.
#099
The operation was canceled.
Perform the canceled operation again.
#102
The subaddress and/or password do not match.
Check the subaddress and/or password for the recipient's machine, and then send again.
There was insufficient memory in the recipient's machine.
Ask the recipient to make more memory available.
#701
The specified Department ID does not exist, or the PIN has changed.
If user authentication is being used, assign a Department ID to the user again. If Department ID authentication is being used, log in again with the new Department ID and PIN.
<Allow Printer Jobs with Unknown IDs> or <Allow Remote Scan Jobs with Unknown IDs> is set to <Off>.
Set <Allow Printer Jobs with Unknown IDs> and <Allow Remote Scan Jobs with Unknown IDs> for <Department ID Management> to <On>.
Sending could not be performed because the Remote Fax client machine could not authenticate itself to the Remote Fax server machine.
If Department ID Management is set on the Remote Fax server machine, log in to the Remote Fax client machine using a Department ID and PIN registered in the Remote Fax server machine.
#702
The document could not be sent because the memory is full.
Wait a few moments, and then try again after the other documents have been sent.
#703
An error occurred while converting the image.
Lower the resolution, and then send the document again.
The memory for the image data is full.
Try again after sending the other documents is complete.
Delete unnecessary files stored in the Mail Box and Fax/I-Fax Inbox. If the machine still does not operate normally, turn OFF the machine, and then turn it back ON.
Sending was interrupted because the image data size was larger than the maximum data size specified in <Settings/Registration>.
Change the maximum data size for sending. Select a lower resolution, or if you are using I-fax, decrease the number of pages to send at a time so that you can send the data within the maximum data size. Depending on the recipient's machine, it may be possible to divide the sent data.
Check whether an expired or revoked certificate is used. Also check whether the certificate chain is invalid.
#751
The server is not running or the network is disconnected. (The server may be unable to connect to the destination, or the network may be broken.)
Check that the server is functioning normally.
Check the status of the network.
Set <Use Divided Chunk Send for WebDAV TX> to <On> for the following cases: The destination uses IIS6.0 with Windows Server 2003, the authentication method for the WebDAV server is Digest Access Authentication, or TLS encrypted communication is performed via a proxy.
You were unable to send to an SMB server (including the Advanced Box of another imageRUNNER ADVANCE series machine made accessible by SMB), because Windows (SMB) is being used to browse file servers.
If a delayed send error occurs, close the <Browse> screen → scan and send the document again.
If an error occurs when forwarding a document received by Fax/I-fax to an SMB server, scan the printed document → send the file to the forwarding destination.
A TCP/IP error (Socket or Select error, etc.) occurred when sending e-mail or sending a fax from the Remote Fax client machine.
Check that the network cables and connectors are properly connected. If the machine still does not operate normally, turn OFF the machine, and then turn it back ON.
An error occurred while sending a link via e-mail to the Mail Box in which the file is stored.
Contact the Administrator.
#761
A PDF or XPS file with a digital signature could not be sent, because a digital certificate or key/certificate registered in the machine is corrupt or could not be accessed.
If you want to send a PDF or XPS file with a user signature, confirm that the user certificate is not corrupt. If the user certificate is corrupt, reinstall it.
If you want to send a PDF or XPS file with a device signature, confirm that the device certificate is not corrupt. If the device certificate is corrupt, generate it again.
The number of trials allowed for the Scan and Send function reached the upper limit.
To continue using the function, purchase the official optional product.
#770
Data could not be sent with WebDAV, because the WebDAV server or proxy server does not support TLS encrypted communication.
Check the settings for the WebDAV server.
Check the proxy server, if you are communicating via a proxy server.
Verification of the TLS server certificate was attempted when sending with WebDAV because <Confirm TLS Certificate for WebDAV TX> is set to <On>, but verification failed and data could not be sent.
Check that the CA certificate which signed the TLS server certificate on the WebDAV server is installed on your machine.
Confirm that the TLS server certificate of the WebDAV server is valid.
Confirm that the TLS server certificate is not a self-signed certificate.
When the machine accessed another server, a verification of the TLS server certificate was attempted, but was not completed due to a verification error. Verification is performed when <Confirm TLS Certificate for Network Access> is set to <On>.
Check that the CA certificate which signed the TLS server certificate on the Advanced Box of another imageRUNNER ADVANCE machine opened as a WebDAV server is installed on your machine.
Confirm that the TLS server certificate of the Advanced Box of another imageRUNNER ADVANCE machine opened as a WebDAV server is valid.
Confirm that the TLS server certificate is not a self-signed certificate.
#771
The setting for the Remote Fax Server Address is incorrect.
A timeout error occurred while the machine was communicating with the SMTP server to send an e-mail message or send/receive an I-fax.
Check that the SMTP server is functioning normally.
Check the status of the network.
The SMTP server returned an error while trying to connect. The destination is incorrect. An error occurred on the server side during transmission to a file server.
Check that SMTP is operating normally. Check the status of the network and file server. Check the settings for the destination.
A file was sent to a destination for which you have no write permission.
Check the address settings.
When a file was sent to the server, a file with the same name already existed on the server where overwrite is prohibited.
Change the settings on the file server to enable files to be overwritten, or contact the server administrator.
Change the file name.
When a file was sent to a file server, either the folder name was incorrectly specified or the password was incorrect.
Check the folder name and password.
#802
The SMTP server name specified in <Communication Settings> is incorrect.
Check the SMTP server name set in <Communication Settings>.
Check that the DNS server is functioning normally.
The settings for the FTP server specified as the destination are incorrect.
Check the FTP server specified as the destination.
Connection to the FTP server failed.
Check that the FTP server is functioning normally.
#804
Could not find the folder that matched the folder path specified when sending a file to a file server.
Check the destination.
You have no permission to access the folder/file, or the folder/file may have been deleted by other operations.
Change the settings on the file server to enable access to the folder, or contact the server administrator.
#805
Sending could not be performed when sending to the SMB server because the server had insufficient space available.
Delete unnecessary documents and documents with errors on the server to make more space available. Otherwise, contact your server administrator.
#806
An incorrect user name or password was specified when sending a file to a file server.
Check the user name or password.
An incorrect destination was specified when sending an e-mail message or I-fax.
Check the e-mail or I-fax address.
#807
You do not have access privileges for the specified directory.
Set access privileges for the server directory, or send to a directory that you have access privileges for. Alternatively, contact the Administrator.
#809
When the machine tried to send a file to the SMB server, a file with the same name already existed on the server, and that file could not be overwritten.
Rename the file, and send again.
Change the settings of the SMB server to allow overwriting. Otherwise, contact your server administrator.
#810
A POP (Post Office Protocol) server connection error occurred when receiving an I-fax.
Check the settings for the POP Server in <Communication Settings>.
The received data is not in a printable file format.
Ask the sender to change the file format and resend the data.
#819
You have received data that cannot be processed (MIME information is incorrect).
Ask the sender to check the settings and resend the data.
#820
You have received data that cannot be processed (BASE 64 or uuencode is incorrect).
Ask the sender to check the settings and resend the data.
#821
You have received data that cannot be processed (TIFF analysis error).
Ask the sender to check the settings and resend the data.
#822
You have received data that cannot be processed (image data cannot be decoded).
Ask the sender to check the settings and resend the data.
#827
You have received data that cannot be processed (contains MIME information that is not supported).
Ask the sender to check the settings and resend the data.
#828
You have received HTML data.
Ask the sender to use a file format other than HTML and resend the data.
#829
Data that contains more than 1,000 pages was received.
This machine can print or store up to 999 pages of data, but will delete any data that exceeds this limit. Ask the sender to resend the remaining pages.
#830
A DSN (Delivery Status Notification) error notification was received due to an incorrect I-fax address or condition settings for the recipient's machine.
Check the I-fax address or condition settings for the recipient machine.
A DSN (Delivery Status Notification) error notification was received because the data size of the sent file exceeded the allowable size on the mail server.
Change the setting in <Maximum Data Size for Sending> so that the file size to send does not exceed the allowable size on the mail server.
MDN (Mail Delivery Notification) mail could not be sent due to problems with the mail server or DNS server.
Check the status of the mail server and DNS server.
#834
An MDN (Mail Delivery Notification) error notification was received due to an incorrect I-fax address or condition settings for the recipient's machine.
Check the I-fax address and conditions of the recipient's machine.
An MDN (Mail Delivery Notification) error notification was received due to problems with the mail server or the network.
Check the status of the mail server and network.
An MDN (Mail Delivery Notification) error notification was received because the memory was full or other error occurred on the recipient's machine.
Check the conditions and status of the recipient's machine.
#835
The maximum number of text lines for receiving an I-fax has been exceeded.
Ask the sender to reduce the amount of text data in the body of the document, and then resend the data.
#839
The user name or password specified in <Communication Settings> is incorrect.
Check the user name and password set for <SMTP Authentication (SMTP AUTH)> in <Communication Settings>.
Change the mail server settings so that a client certificate is not requested when sending.
Verification of the TLS server certificate was attempted when sending with SMTP because <Confirm TLS Certificate for SMTP TX> is set to <On>, but verification failed and data could not be sent.
Using the Remote UI, check that the CA certificate which signed the TLS server certificate on the SMTP server is installed on your machine.
Confirm that the TLS server certificate of the SMTP server is valid.
Confirm that the TLS server certificate is not a self-signed certificate.
#843
There is a large difference between the current time set in the KDC (Key Distribution Center) server and the time set in the machine.
Adjust the current date and time in <Date/Time Settings>.
Adjust the current time set in the KDC (Key Distribution Center) server.
#844
When sending with POP before SMTP, TLS encrypted communication with the POP server failed.
Check the TLS encrypted communication setting of the POP server.
Set <Allow TLS (POP)> in <Communication Settings> to <Off>. If the problem cannot be solved, set <POP Authentication Before Sending> in <Communication Settings> to <Off>, and switch the setting to one other than POP before SMTP.
Verification of the TLS server certificate was attempted when communicating with a POP server because <Confirm TLS Certificate for POP RX> is set to <On>, but verification failed and data could not be sent.
Using the Remote UI, check that the CA certificate which signed the TLS server certificate on the POP server is installed on your machine.
Confirm that the TLS server certificate of the POP server is valid.
Confirm that the TLS server certificate is not a self-signed certificate.
#845
When sending with POP before SMTP, POP authentication (POP AUTH) failed.
Check <POP Server>, <POP Login Name>, and <POP Password> in <Communication Settings>.
Check the POP authentication setting of the POP server.
Select <Standard> or <APOP> for <POP Auth. Method> in <Communication Settings>. If the problem cannot be solved, set <POP Authentication Before Sending> in <Communication Settings> to <Off>, and switch the setting to one other than POP before SMTP.
Select <Standard> or <POP AUTH> for <POP Auth. Method> in <Communication Settings>. If the problem cannot be solved, set <POP Authentication Before Sending> in <Communication Settings> to <Off>, and switch the setting to the one other than POP before SMTP.
Received a response from the destination stating that authentication failed when sending with WebDAV (received HTTP Error 401: Unauthorized).
Check the user name and password for the destination.
Check the security settings of the WebDAV server.
#870
Received a response from the destination stating that the request was denied when sending with WebDAV (received HTTP Error 403: Forbidden).
Wait a few moments, and then try again.
Check the address settings.
Check the settings for the WebDAV server.
#871
Received a response from the destination stating that the specified folder could not be found when sending with WebDAV (received HTTP Error 404: Not Found/409: Conflict/410: Gone).
Check the address settings.
#872
Received a response from the destination stating that access was denied when sending with WebDAV (received HTTP Error 405: Method Not Allowed).
Check the settings for the WebDAV server.
#873
Received a response from the destination stating that proxy authentication failed when sending with WebDAV (received HTTP Error 407: Proxy Authentication Required).
Received a response from the destination stating that the size of the data was too large when sending with WebDAV (received HTTP Error 413: Request Entity Too Large).
Check the settings for the WebDAV server.
#877
Received a response from the destination stating that the URI (host name and folder path) was too long when sending with WebDAV (received HTTP Error 414: Request-URI Too Long).
Check the settings for the WebDAV server.
#878
Received a response from the destination stating that the server encountered an unexpected condition that prevented it from executing the request when sending with WebDAV (received HTTP Error 500: Internal Server Error).
Check the settings for the WebDAV server.
#879
Received a response from the destination stating that the server does not support the necessary functions to execute the request when sending with WebDAV (received HTTP Error 501: Not Implemented).
Check the settings for the WebDAV server.
If you are sending via a proxy server without using TLS encrypted communication, set <Use Divided Chunk Send for WebDAV TX> to <Off>.
Received a response from the destination stating that the proxy server failed to communicate with the server above it when sending with WebDAV (received HTTP Error 502: Bad Gateway).
Check the settings for the WebDAV server.
Check the settings of the proxy server.
#881
Received a response from the destination stating that the server could not handle the current request when sending with WebDAV (received HTTP Error 503: Service Unavailable).
Check the settings for the WebDAV server.
#882
Received a response from the destination stating that the proxy server failed to communicate with the server above it when sending with WebDAV (received HTTP Error 504: Gateway Timeout).
Check the settings for the WebDAV server.
Check the settings of the proxy server.
#883
Received a response from the destination stating that the server does not support the necessary functions to execute the request when sending with WebDAV (received HTTP Error 505: HTTP Version Not Supported).
Check the settings for the WebDAV server.
#884
Received a response from the destination stating that the server lacks sufficient free disk space to execute the request when sending with WebDAV (received HTTP Error 507: Insufficient Storage).
Check the settings for the WebDAV server.
#885
Received a response from the server stating that an unexpected error occurred when sending with WebDAV.
Check the settings for the WebDAV server.
Check the settings of the proxy server.
#886
Received a response from the destination stating that the request was invalid when sending with WebDAV (received HTTP Error 400: Bad Request).
If you are sending via a proxy server without using TLS encrypted communication, Set <Use Divided Chunk Send for WebDAV TX> to <Off>.
The document cannot be scanned or printed because it is embedded with job restriction information.
Check the job restriction information, or contact the Administrator.
#899
The e-mail or I-fax has been successfully sent, but reception may be incomplete because the transmission was relayed via multiple servers.
Ask the recipient to check that the document was received properly.
The fax was sent normally from the remote fax client. However, reception may be incomplete because the transmission was relayed via a remote fax server.
Check whether the fax was sent in the transmission results of the remote fax server.
Check the status of the server and network.
Ask the recipient to check that the document was received properly.
#919
A syntax error or a PostScript error that exceeds device restrictions, etc. was detected.
Set <Print PS Errors> (Settings/Registration) to <On>, submit the job again, confirm the contents of the PostScript error, then execute the job after resolving the error.
#920
The machine received an I-fax for which S/MIME was used, but the machine does not support the encryption algorithm specified for S/MIME.
Ask the sender to select an encryption algorithm supported by the machine and send the I-fax again.
The machine received an I-fax for which S/MIME was used, but the machine does not support the signature algorithm specified for S/MIME, or an invalid signature is used in the public key certificate registered to the sending machine.
Register the public key certificate of the sending machine or the sender to the machine.
The job was canceled and one copy was output without being bound because the maximum number of sheets of paper that can be bound with the Eco (Staple-Free) mode was exceeded.
Check the maximum number of sheets of paper that can be bound with the Eco (Staple-Free) mode, and execute the job again.
You can specify the procedure to perform when there are too many sheets to staple at once.
The job was canceled and one copy was output without being stapled because the maximum number of sheets of paper that can be stapled together was exceeded.
Check the maximum number of sheets of paper that can be stapled together, and execute the job again.
You can specify the procedure to perform when there are too many sheets to staple at once.
Top
<No. of TX Lines>