When printing or scanning is not completed normally or fax transmission or reception fails, a number starting with "#" (an error code) is displayed on the details screen for job log or a communication management report (Printing Reports and Lists). Perform the countermeasure required for the error code.
Some error codes may not be displayed, depending on your machine.
Place the original correctly and try sending again from the start of the procedure.
#012
Could not send because the device of the other party does not have any paper.
Tell the other party to load paper.
#018
There was no response when redialing.
Check that the other party can communicate, and redial again.
Could not send because the other party was making a call, etc.
Check that the other party can communicate, and try sending again.
Could not send because the settings of the device of the other party do not match.
Check the settings of the other party, and try sending again.
#019
When sending a fax from a remote fax client machine, sending could not be performed because the memory of the remote fax server machine became full.
Try sending again after the other sending to the remote fax server machine is complete.
Delete unnecessary documents and error documents from the remote fax server machine to free up space.
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 the content of the group destination specified as the forwarding destination was deleted or only included a Mail Box.
Specify another destination, and try sending again.
When sending to a destination registered in the address book, sending could not be performed because the destination was deleted from the address book while the machine was waiting to send.
Specify another destination, and try sending again.
Sending from the fax driver is not allowed.
Set <Allow Fax Driver TX> to <On>, and try sending again.
When sending a fax from a remote fax client machine, a line that does not exist in the remote fax server machine was specified.
Check the number of lines in the server machine, and try sending again after matching the remote fax transmission settings of the client machine with the number of lines on the server machine.
Data containing more than 1,000 pages was received.
The machine deletes any pages after the 999th page, and prints or stores the remaining 999 pages. Tell the other party to send the 1,000th and subsequent pages again.
When performing delayed sending or redial sending, the image data of the document to send was not found in memory.
Scan the original again, and try sending again.
Select direct sending when sending again.
Could not send to multiple destinations because the machine had insufficient free memory.
Delete unnecessary documents and error documents to free up space.
Divide the document into two or more parts, and then try sending the document again.
Lower the resolution and try sending again.
#040
When sending a fax from a remote fax client machine, sending could not be performed because the memory of the remote fax server machine was insufficient.
Delete unnecessary documents and error documents from the remote fax server machine to free up space.
Divide the document into two or more parts, and then try sending the document again.
Lower the resolution and try sending 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 canceled because the unit telephone number and unit name were not registered.
Try sending again after registering the unit telephone number and unit name.
A subaddress is not set in the device of the other party.
Check the subaddress of the other party, and try sending again.
#081
A password is not set in the device of the other party.
Check the password of the other party, and try sending again.
#082
Polling transmission is not configured in the device of the other party.
Tell the other party to configure polling transmission, and perform polling reception again.
#083
The subaddress and password of the machine and the device of the other party did not match when performing polling reception.
Check that the subaddress and password of the machine and the device of the other party match, and try sending again.
#084
Cannot perform polling reception because the password is not supported by the device of the other party.
Perform polling reception without using a password.
#099
The operation was canceled before it was complete.
Perform the operation again.
#102
The subaddress and password do not match.
Check the subaddress and password of the other party, and try sending again.
There was insufficient memory in the recipient's machine.
Ask the recipient to make more memory available.
#701
The Department ID does not exist, or the PIN was changed.
If you are using User Authentication, assign Department IDs to users. If you are using DepartmentID Authentication, enter the new Department ID and PIN to log in again.
The reception setting in <Allow Printer Jobs with Unknown IDs> is set to <Off>.
Set <Allow Printer Jobs with Unknown IDs> and <Allow Remote Scan Jobs with Unknown IDs> in <Department ID Management> to <On>.
Sending could not be performed because the remote fax client machine failed authentication to the remote fax server machine.
If Department ID Management is set in the remote fax server machine, log in to the remote fax client machine using the Department ID and PIN set in the remote fax server machine.
#702
Sending could not be performed because the memory was full.
Wait a while. Try sending again after the other sending is complete.
#703
An error occurred while converting the image.
Lower the resolution, and then send the document again.
Could not write because the image area of the memory is full.
Try sending again after the other sending is complete.
Delete unnecessary files in the Mail Box and Fax/I-Fax Inbox. If there is still a problem, restart the machine.
Sending was canceled because the image data size exceeded the maximum value set in Settings/Registration.
Adjust the maximum data size for sending. Select a lower resolution or reduce the number of images sent at once when using the I-fax function to ensure that the maximum data size for sending is not exceeded. Divide the data, depending on the conditions of the other party.
Check whether an expired certificate or revoked certificate is being used. In addition, check whether the certificate chain is invalid.
#751
The server is not running or the network is disconnected (either you could not connect to the destination, or the connection was lost before the job could be completed).
Check whether the server is operating normally.
Check the status of the network.
If the destination is using IIS 6.0 with Windows Server 2003 and digest authentication is used as the authentication method of the WebDAV server, set <Use Divided Chunk Send for WebDAV TX> to <On> to send with WebDAV via a proxy using TLS communication.
Could not send to an SMB server (including the Advanced Box of another imageRUNNER ADVANCE series machine disclosed with SMB) because a file server is being browsed using Windows (SMB).
If an error occurs with delayed sending, close the <Browse> screen, and scan and send the document again.
If an error occurs when forwarding a received fax/I-fax file to an SMB server, scan a printed copy of the received file, and send it to the forwarding destination.
An error occurred when sending the URL of the Mail Box in which a file was saved.
Contact your administrator.
#761
When sending a PDF/XPS file with a digital signature, the file could not be sent because the certificate or key pair set in the machine was corrupt or could not be accessed.
When sending a PDF/XPS file with a user signature, check whether the user certificate is corrupt. If the user certificate is corrupt, install it again.
When sending a PDF/XPS file with a device signature, check whether the device certificate is corrupt. If the device certificate is corrupt, generate it again.
Could not connect to the time stamp server because there is a problem with the network line.
Check the status of the DNS server, proxy server, and network.
#769
The number of trials allowed for the send function reached the upper limit.
If you want to continue using this function, purchase the official optional product.
#770
When sending with WebDAV, sending could not be performed because TLS communication was not supported on the WebDAV server side or proxy server side.
Check the WebDAV server settings.
Check the proxy server if you are sending via a proxy.
Sending could not be performed because a validation error occurred when validating the TLS server certificate when sending with WebDAV because <Confirm TLS Certificate for WebDAV TX> is set to <On>.
Check whether the CA certificate used to sign the TLS server certificate on the WebDAV server side is registered in the machine.
Check whether the TLS server certificate on the WebDAV server side is correct.
Check whether the TLS server certificate is a self-signed certificate.
The operation could not be completed because a validation error occurred when validating the TLS server certificate when accessing another server because <Confirm TLS Certificate for Network Access> is set to <On>.
Check whether the CA certificate used to sign the TLS server certificate of the Advanced Box of the other imageRUNNER ADVANCE series machine disclosed as a WebDAV server is registered in the machine.
Check whether the TLS server certificate of the Advanced Box of the other imageRUNNER ADVANCE series machine disclosed as a WebDAV server is correct.
Check whether the TLS server certificate is a self-signed certificate.
#771
The remote fax server address setting is incorrect.
A timeout error occurred due to a problem on the mail server side when communicating with the SMTP server to send an e-mail or send or receive an I-fax.
Check whether the SMTP server is operating normally.
Check the status of the network.
An error was returned from the SMTP server when connecting with SMTP. The address setting is incorrect. An error occurred due to a problem on the server side when sending to a file server.
Check whether SMTP is operating normally, the status of the network, the destination settings, and the status and settings of the file server.
You sent to a destination that does not have write privileges.
Check the destination settings.
A file with the same name existed when sending to a file server that does not allow files to be overwritten.
Change the settings of the file server to enable files to be overwritten. Alternatively, contact the server administrator.
Change the filename.
The folder name or password specified when sending to a file server was incorrect.
Check the folder name or 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
When sending to a file server, no folders matched the specified path.
Check the destination.
You do not have access privileges for the folder or file. Alternatively, the folder or file may have been deleted by another operation.
Allow access to the folder on the server side. Alternatively, contact the server administrator.
#805
Could not send to the SMB server because there was insufficient free space on the server side.
Delete unnecessary documents and error documents from the server to free up space. Alternatively, contact the server administrator.
#806
The user name or password specified when sending to a file server was incorrect.
Check the user name or password.
The destination specified when sending an e-mail/I-fax was incorrect.
Check the e-mail/I-fax destination.
#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 your administrator.
#809
When sending to an SMB server, a file with the same name already exists and overwriting of files is not allowed.
Change the filename and try sending again.
Change the settings of the SMB server to enable files to be overwritten. Alternatively, contact the server administrator.
When sending to an SMB server, the response on the server side was slow, causing a wait time timeout on the machine side before the data could be sent or forwarding could be completed.
The received data was in a file format that cannot be printed.
Tell the other party to change the file format and send again.
#819
Data that cannot be handled was received. The MIME information is invalid.
Tell the other party to check the settings and send again.
#820
Data that cannot be handled was received. The BASE64 or uuencode is invalid.
Tell the other party to check the settings and send again.
#821
Data that cannot be handled was received. A TIFF analysis error occurred.
Tell the other party to check the settings and send again.
#822
Data that cannot be handled was received. The image cannot be decoded.
Tell the other party to check the settings and send again.
#825
The Department ID and PIN of a job being executed or a reserved job were deleted, or the PIN was changed.
Execute the job again using the changed Department ID and PIN.
#827
Data that cannot be handled was received. Unsupported MIME information was included.
Tell the other party to check the settings and send again.
#828
HTML data was received.
Tell the other party to change to a format other than HTML and send again.
#829
Data containing more than 1,000 pages was received.
The machine deletes any pages after the 999th page, and prints or stores the remaining 999 pages. Tell the other party to send the 1,000th and subsequent pages again.
#830
A DSN error notification was received because the I-fax address or destination conditions were incorrect.
Check the specified I-fax address and the destination conditions.
A DSN error notification was received because the size of the file that was sent exceeded the size allowed by the mail server.
Change the setting in <Maximum Data Size for Sending> so that the size of the file to send does not exceed the size allowed by the mail server.
Change mail server settings so that a client certificate is not requested.
Sending could not be performed because a validation error occurred when validating the TLS server certificate when sending with SMTP because <Confirm TLS Certificate for SMTP TX> is set to <On>.
Use the Remote UI to check whether the CA certificate used to sign the TLS server certificate on the SMTP server side is registered in the machine.
Check whether the TLS server certificate on the SMTP server side is correct.
Check whether the TLS server certificate is a self-signed certificate.
#843
There is a great difference between the time of 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
Failed to perform TLS encrypted communication with the POP server when sending with POP before SMTP.
Check the TLS encrypted communication settings of the POP server.
Set <Allow TLS (POP)> to <Off> in <Communication Settings>. If the problem is not resolved, set <POP Authentication Before Sending> to <Off> in <Communication Settings>, and switch to a setting other than POP before SMTP.
Sending could not be performed because a validation error occurred when validating the TLS server certificate when communicating with the POP server because <Confirm TLS Certificate for POP RX> is set to <On>.
Use the Remote UI to check whether the CA certificate used to sign the TLS server certificate on the POP server side is registered in the machine.
Check whether the TLS server certificate on the POP server side is correct.
Check whether the TLS server certificate is a self-signed certificate.
#845
Failed to perform POP authentication (POP AUTH) when sending with POP before SMTP.
Check the settings in <POP Server>, <POP Login Name>, and <POP Password> in <Communication Settings>.
Check the POP authentication settings of the POP server.
Select <Standard> or <APOP> in <POP Auth. Method> in <Communication Settings>. If the problem is not resolved, set <POP Authentication Before Sending> to <Off> in <Communication Settings>, and switch the communication settings to something other than POP before SMTP.
Select <Standard> or <POP AUTH> in <POP Auth. Method> in <Communication Settings>. If the problem is not resolved, set <POP Authentication Before Sending> to <Off> in <Communication Settings>, and switch the communication settings to something other than POP before SMTP.
An error occurred when combining an e-mail that was divided and sent.
The divided data may have been deleted. If you delete divided data, it cannot be combined to form a completed document, even if the remaining data is received later. Ask the sender to send the data again.
#851
The printer job could not be stored in the Mail Box because the memory is full.
Check the amount of available memory, and execute the job again.
#852
The power was turned OFF while the job was being executed.
Check that the power cable and plug are securely connected, and execute the job again.
#853
The memory is full.
Reduce the number of pages or check that the number of jobs waiting to be processed has decreased, and execute the job again.
#856
The executed operation was canceled because the hard disk area for temporarily saving data became full.
Contact your administrator.
#857
Printing was canceled due to the job being canceled while being received, or due to timeout.
If timeout has occurred, check the status of the network.
#858
The data is invalid.
Check that the print protocol is supported by the machine, as well as the print settings.
#860
Recovery failed after a paper jam, or an incompatible page description language or settings which cannot be combined were included.
Check the paper or job settings.
#861
An error occurred while processing the print data or image data.
Check the image size and paper size, as well as the color specification settings.
#862
Settings are included which are not supported, cannot be combined, or otherwise exceed the limits of the machine.
Check the job settings.
#863
The job was canceled because initialization operations were performed while the print data was being processed.
Execute the job again.
#864
Could not correctly recognize the external controller, or an error occurred while forwarding print data.
Check the controller and the print data.
#865
The required functions for printing are currently restricted.
Check the machine and the job settings.
#868
When sending with WebDAV, communication with the destination failed, and access via a proxy was requested (received HTTP Error 305: Use Proxy).
When sending with WebDAV, a response indicating that authentication failed was received from the destination (received HTTP Error 401: Unauthorized).
Check the user name or password.
Check the WebDAV server security settings.
#870
When sending with WebDAV, a response indicating that the request was rejected was received from the destination (received HTTP Error 403: Forbidden).
Try sending again after waiting a while.
Check the destination settings.
Check the WebDAV server settings.
#871
When sending with WebDAV, a response indicating that the specified folder was not found was received from the destination (HTTP Error 404: Not Found/409: Conflict/410: Gone).
Check the destination settings.
#872
When sending with WebDAV, a response indicating that access is not allowed was received from the destination (received HTTP Error 405: Method Not Allowed).
Check the WebDAV server settings.
#873
When sending with WebDAV, a response indicating that proxy authentication failed was received from the destination (received HTTP Error 407: Proxy Authentication Required).
When sending with WebDAV, a response indicating that a timeout occurred was received from the destination (received HTTP Error 408: Request Timeout).
Try sending again after waiting a while.
Check the WebDAV server settings.
#875
When sending with WebDAV, a response indicating that chunk transmission was refused was received from the destination (received HTTP Error 411: Length Required).
Set <Use Divided Chunk Send for WebDAV TX> to <Off>.
When sending with WebDAV, a response indicating that the size of the data was too large was received from the destination (received HTTP Error 413: Request Entity Too Large).
Check the WebDAV server settings.
#877
When sending with WebDAV, a response indicating that the URI (host name and path to folder) was too long was received from the destination (received HTTP Error 414: Request-URI Too Long).
Check the WebDAV server settings.
#878
When sending with WebDAV, a response indicating that an unexpected situation preventing the request from being executed occurred on the server side was received from the destination (received HTTP Error 500: Internal Server Error).
Check the WebDAV server settings.
#879
When sending with WebDAV, a response indicating that the server does not support the necessary functions to execute the request was received from the destination (received HTTP Error 501: Not Implemented).
Check the WebDAV server settings.
When sending via a proxy with non-TLS communication, set <Use Divided Chunk Send for WebDAV TX> to <Off>.
When sending with WebDAV, a response indicating that communication with an upstream server failed was received from the proxy server (received HTTP Error 502: Bad Gateway).
Check the WebDAV server settings.
Check the proxy server settings.
#881
When sending with WebDAV, a response indicating that requests currently cannot be handled was received from the destination (received HTTP Error 503: Service Unavailable).
Check the WebDAV server settings.
#882
When sending with WebDAV, a response indicating that communication with an upstream server failed was received from the proxy server (received HTTP Error 504: Gateway Timeout).
Check the WebDAV server settings.
Check the proxy server settings.
#883
When sending with WebDAV, a response indicating that the server does not support the necessary functions to execute the request was received from the destination (received HTTP Error 505: HTTP Version Not Supported).
Check the WebDAV server settings.
#884
When sending with WebDAV, a response indicating that disk space required for the request could not be secured on the server side was received from the destination (received HTTP Error 507: Insufficient Storage).
Check the WebDAV server settings.
#885
When sending with WebDAV, an unexpected error response was received from the server.
Check the WebDAV server settings.
Check the proxy server settings.
#886
When sending with WebDAV, a response indicating that the request was invalid was received from the destination (received HTTP Error 400: Bad Request).
When sending via a proxy with non-TLS communication, set <Use Divided Chunk Send for WebDAV TX> to <Off>.
The original could not be scanned or printed because it was embedded with job restriction information.
Check the job restriction information or contact your administrator.
#899
E-mail or I-fax transmission completed normally. However, the transmission may not have been received by the other party because it is relayed by multiple servers.
Ask whether the other party received the transmission, as necessary.
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.
#918
Could not recognize the QR code in the original.
Check whether the QR code is in the correct position and scan the original again.
#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.
#922
The maximum number of sheets that can be saddle-stitched has been exceeded. Saddle-stitching may be able to be performed by reducing the number of sheets.
Check the maximum number of sheets that can be saddle-stitched, and execute again.
#923
Could not print on the specified side of the cover, or body of the booklet.
Change to a paper type that is compatible with two-sided printing, and execute the job again.
#924
A function was specified which cannot be combined with the Eco (Staple-Free) mode.
If you change the staple position or the paper type, it may be possible to bind with the Eco (Staple-Free) mode.
#925
A transmission error occurred from the fax driver.
An image size that cannot be sent was specified. Check the size of the image.
#927
A transmission error occurred from the fax driver.
Font that cannot be processed is included in the data received by the machine from a computer. Check the received data.
#928
A transmission error occurred from the fax driver.
The memory is full, or the data size has exceeded the size that can be processed at one time. Delete unnecessary data or check the data size.
#929
A transmission error occurred from the fax driver.
A network error occurred when the machine was receiving data from a computer. Check the network connections and settings.
#931
The job was canceled because saddle folding could not be performed.
Check the setting combinations as well as the type of paper you are using and the number of sheets.
#932
The maximum number of sheets that can be stapled with the Eco (Staple-Free) mode has been exceeded. Stapling with the Eco (Staple-Free) mode may be able to be performed by reducing the number of sheets.
Check the maximum number of sheets that can be stapled with the Eco (Staple-Free) mode, and execute again.
#933
The maximum number of sheets that can be stapled has been exceeded. Stapling may be able to be performed by reducing the number of sheets.
Check the maximum number of sheets that can be stapled, and execute again.
#934
An error occurred for a print job, and the job was deleted because the specified time period elapsed.
Resolve the error and execute the job again.
You can also change the time period before deletion or disable automatic deletion from <Auto Delete Suspended Jobs> (Settings/Registration).
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
Troubleshooting
<TCP/IP Settings>