List of Error Codes without Messages

If a job or operation does not complete successfully, the error code is displayed on the Details screen for Log on the Status Monitor/Cancel screen. (See "Status Monitor/Cancel.")

If a send, receive, or fax job does not complete successfully, the error code is printed in the Results column of various reports such as the Communication Management Report. (See "Printing Reports.")

Perform the necessary procedures according to the error code.

#003 to 700

#003	#012	#025	#081	#401	#406	#411
#005	#018	#037	#099	#402	#407
#009	#019	#040	#102	#403	#409
#011	#022	#080	#107	#404	#410

#701 to 800

#701	#706	#751	#755	#770
#702	#711	#752	#761	#771
#703	#712	#753	#762	#773
#704	#749	#754	#766

#801 to 850

#801	#807	#819	#827	#832	#839	#845
#802	#810	#820	#828	#833	#841	#846
#803	#815	#821	#829	#834	#842	#849
#804	#816	#822	#830	#835	#843	#850
#806	#818	#825	#831	#837	#844

#851 to 995

#851	#856	#861	#869	#874	#879	#884	#904
#852	#857	#862	#870	#875	#880	#885	#905
#853	#858	#863	#871	#876	#881	#886	#995
#854	#859	#865	#872	#877	#882	#889
#855	#860	#868	#873	#878	#883	#899

NOTE
If a send job is cancelled, <STOP> is printed in the Results column on the Send report.

#003

Cause	Communication took longer than the preset time (64 minutes), causing an error.
Remedy 1	Reduce the resolution or divide the document into two or more parts, and then try sending the document again. (See "Setting the Resolution.")
Remedy 2	When receiving a document, ask the remote party to either reduce the resolution at which the document is scanned, or divide the document into two or more parts before sending it.

#005

Cause 1	The recipient did not answer within 35 seconds.
Remedy	Confirm that the recipient's machine is able to communicate, and then try again.
Cause 2	The receiving machine is not a G3 fax.
Remedy	Check the type of machine used by the recipient.

#009

Cause 1	There is no paper.
Remedy	Load paper. (See "Loading Paper.")
Cause 2	The paper drawer is not correctly inserted into the machine.
Remedy	Insert the paper drawer properly. (See "Loading Paper into a Paper Drawer.")

#011

Cause	The document that you are sending is not placed correctly.
Remedy	Place the document properly into the feeder or on the platen glass, and try sending again.

#012

Cause	The document could not be sent because the receiving fax machine was out of paper.
Remedy	Ask the recipient to load paper into their fax machine.

#018

Cause 1	The recipient's machine did not respond when your machine redialed.
Remedy	Confirm that the recipient's machine is able to communicate, and then try again.
Cause 2	The documents could not be sent because the recipient's machine was performing another task.
Remedy	Confirm that the recipient's machine is able to communicate, and then try again.
Cause 3	The settings on your machine do not match the settings on the recipient's machine.
Remedy	Confirm that the recipient's machine is able to communicate, and then try again.

#019

Cause	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.
Remedy 1	Wait a few moments, and then try again after the other send jobs on the Remote Fax server machine are complete.
Remedy 2	Erase unnecessary documents and documents with errors from the Remote Fax server machine to increase the amount of available memory.

#022

Cause 1	Forwarding could not be performed because all of the addresses stored in the specified group destination have been deleted.
Remedy	Try sending again.
Cause 2	When transmitting to a destination stored in the Address Book, transmission could not be performed because the specified destination stored in the Address Book was deleted while the documents were waiting to be sent.
Remedy	Try sending again.
Cause 3	Transmission via fax driver is not allowed.
Remedy	[Allow Fax Driver TX] is set to 'Off'. Set it to 'On'. (See "Restricting the Send Function.")

#025

Cause	A telephone line not connected to the Remote Fax server machine was specified when sending fax from the Remote Fax client machine.
Remedy	First, check the telephone line number for the server machine. Then, set the correct telephone line number for the server machine in Remote Fax TX Settings on the client machine. (See "Remote Fax TX Settings.")

#037

Cause 1	The document could not be received because there was insufficient memory available.
Remedy	Delete unnecessary documents and documents with errors to make more memory available. (See "Checking the Detailed Information for/Deleting a File in the Memory RX Inbox.")
Cause 2	Data that contains more than 1,000 pages was received.
Remedy	This machine can print or store up to 999 pages of data in memory, but will delete any data that exceeds this limit. Ask the sender to resend the remaining pages.
Cause 3	The image data for the document to send was not found in memory when performing delayed sending or redialing.
Remedy 1	Scan the original and perform sending again.
Remedy 2	When resending the document, select the Direct Sending mode.
Cause 4	Sending could not be performed when sending to multiple destinations because there was insufficient memory available.
Remedy 1	Delete unnecessary documents and documents with errors to make more memory available.
Remedy 2	Divide the sending operation into multiple batches instead of sending the document to all destinations at once.
Remedy 3	Lower the resolution or divide the document into two or more parts, and then try sending the document again.

#040

Cause	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.
Remedy 1	Erase unnecessary documents and documents with errors from the Remote Fax server machine to increase the amount of available memory.
Remedy 2	Divide the sending operation into multiple batches instead of sending the document to all destinations at once.
Remedy 3	Lower the resolution or divide the document into two or more parts, and then try sending the document again.

#080

Cause	A subaddress is not set in the recipient's machine.
Remedy	Try sending the document without a subaddress, or request that the recipient set the same subaddress as the sender's subaddress.

#081

Cause	A password is not set in the recipient's machine.
Remedy	Try sending the document without a password, or request that the recipient set the same password as the sender's password.

#099

Cause 1	The job was cancelled.
Remedy	Perform the job again.
Cause 2	An error occurred because the main power switch was turned OFF while executing a job.
Remedy	Check whether the main power switch is turned ON, and perform the operation again, as necessary. (See "Main Power and Energy Saver Key.")

#102

Cause	The subaddress and/or password do not match.
Remedy	Check the subaddress and/or password for the recipient's machine. Make sure that the subaddress and password you are sending with the document matches the recipient's, and then try again.

#107

Cause	The document could not be sent because there was insufficient memory available.
Remedy 1	Lower the resolution or divide the document into two or more parts, and then try sending the document again.
Remedy 2	Delete unnecessary files to make more memory available. (See "Checking the Detailed Information for/Deleting a File in the Memory RX Inbox" and "Checking File Information/Adding and Deleting Files.")
Remedy 3	If this problem occurs frequently, contact your local authorized Canon dealer.

#401

Cause	The memory media or file server is full, or the number of files that can be saved in the root directory (the top level folder inside the memory media) has been exceeded.
Remedy	Delete unnecessary files from the memory media or file server, or create a new folder and move existing files to that folder to create room in the root directory.

#402

Cause	The image transfer failed when transferring to the memory media because an invalid character (such as \) was included in the specified filename.
Remedy	Change the filename to the correct filename.

#403

Cause	The file could not be saved because a file with the same name already exists. Normally, automatic renaming is performed to append a number between 1 and 999 to the filename when a file with the same name exists, but the file could not be saved because files with the numbers 1 to 999 appended to them already exist.
Remedy	Change the filename and save the file again.

#404

Cause	Writing failed because the write protect switch of the memory media was enabled.
Remedy	Disable the write protect switch of the memory media.

#406

Cause 1	Writing failed due to one of the following possible causes: Memory media was removed while the file was being written to it. The Advanced Space of another machine on the network was deleted while the file was being written to it.
Remedy	Check that the memory media is inserted or that the Advanced Space of another machine on the network is available, and read the file again.
Cause 2	The image transfer failed when transferring to the memory media because an unspecified error occurred. (The connected memory media may be formatted with an unsupported file system.)
Remedy	Check the status of the memory media and confirm that it is formatted with a file system supported by the machine (FAT32). Then, try performing the procedure again.
Cause 3	The size of the file exceeded the upper limit.
Remedy	Lower the resolution or reduce the number of pages, and perform the operation again.

#407

Cause	The length of the full path to the specified file (or folder) exceeds the maximum supported length.
Remedy	Change the filename so that the length of the full path is within 256 characters, or change the destination folder.

#409

Cause	The file could not be saved because the maximum number of files that can be saved in the destination has been reached.
Remedy	Change the destination to save the file.

#410

Cause	Storing cannot be performed because there are too many jobs waiting to be stored.
Remedy	Perform the operation again when the other jobs are complete.

#411

Cause	The files are already locked by the other operations.
Remedy	Wait a while, and perform the operation again.

#701

Cause 1	The specified Department ID does not exist, or the PIN has changed.
Remedy	Enter the correct Department ID or PIN using - (numeric keys) on the control panel, and then try sending again.
Cause 2	The Department ID or PIN was changed during the job.
Remedy	Try performing the job again with the new Department ID and PIN. If you do not know the PIN, contact your System Manager.
Cause 3	Reception of print jobs with unknown IDs or remote scan jobs with unknown IDs is disabled.
Remedy	Set <Allow Printer Jobs with Unknown IDs> and <Allow Remote Scan Jobs with Unknown IDs> for [Department ID Management] to 'On'. (See "Accepting Jobs with Unknown Department IDs.")
Cause 4	Sending could not be performed because authentication failed between the Remote Fax server machine and the Remote Fax client machine.
Remedy	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

Cause	The document could not be sent because the memory is full.
Remedy 1	Wait a few moments, and then try again after the other send jobs are complete.
Remedy 2	Do not send the document to too many recipients at the same time. Send the document to a smaller number of recipients.

#703

Cause	The memory for the image data is full.
Remedy 1	Wait a few moments, and then try again after the other send jobs are complete.
Remedy 2	Delete files stored in the Fax/I-Fax Inbox. If the machine still does not operate normally, turn the main power OFF, and then back ON. (See "Main Power and Energy Saver Key.")

#704

Cause	An error occurred when reading address information from the Address Book.
Remedy	Check the address settings. If the machine still does not operate normally, turn the main power OFF, and then back ON. (See "Main Power and Energy Saver Key.")

#706

Cause	The address book is currently being imported/exported from the Remote UI, or the machine is busy with other send related functions.
Remedy	Try sending again.

#711

Cause	The Fax/I-Fax Inbox memory is full.
Remedy	Delete files stored in the Fax/I-Fax Inbox. (See "Checking the Detailed Information for/Deleting a File in the Memory RX Inbox" and "Checking File Information/Adding and Deleting Files.")

#712

Cause	The maximum number of files is already stored in the Fax/I-Fax Inbox.
Remedy	Delete files stored in the Fax/I-Fax Inbox. (See "Checking the Detailed Information for/Deleting a File in the Memory RX Inbox" and "Checking File Information/Adding and Deleting Files.")

#749

Cause	The operation could not be performed because a service call message is displayed.
Remedy	Turn the main power OFF, and turn the main power ON again. If the operation still cannot be performed correctly, turn the main power switch OFF, remove the power plug from the outlet, and contact your local authorized Canon dealer. (See "Main Power and Energy Saver Key.")

#751

Cause 1	The server is not functioning. The network is not connected. (The server may be unable to connect to the network, or it may have lost the connection.)
Remedy 1	Make sure that the server is ON, and check the destination. Check the status of the network.
Remedy 2	If WebDAV sending is based on the following conditions, enable Use Chunked Encoding with WebDAV Sending. (See "Dividing Data into Chunks When Sending with WebDAV.") The destination uses IIS6.0 with Windows Server 2003. The authentication method for the WebDAV server is Digest Access Authentication. SSL communication is performed via a proxy.
Cause 2	The IP address is not set.
Remedy	Check [TCP/IP Settings] in Network in [Preferences] (Settings/Registration). (See "Protocol Settings.")
Cause 3	You were unable to send to an SMB server (including the Advanced Space of another imageRUNNER ADVANCE series machine made accessible by SMB), because Windows (SMB) is being used to browse file servers. (See "Specifying a File Server Using the Browse Key (Windows (SMB)).")
Remedy 1	If a delayed send error occurs, close the [Browse] screen → scan and send the original again.
Remedy 2	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.
Remedy 3	You can avoid errors by using FTP as the protocol for sending to servers.

#752

Cause 1	The server is not functioning. The network is not connected.
Remedy	Check that the SMTP server is operating properly. Check the status of the network.
Cause 2	The SMTP server name for the e-mail or I-fax is not correct. Alternatively, the domain name or e-mail address may not be set.
Remedy	Check the SMTP Server Name, Domain Name, and E-Mail Address in Communication Settings. (See "Common Communication Settings for E-Mail/I-Fax.")

#753

Cause	A TCP/IP error (Socket or Select error, etc.) occurred when sending an e-mail or sending a fax from the Remote Fax client machine.
Remedy	Check that the network cables and connectors are properly connected. If the machine still does not operate normally, turn the main power OFF, and then back ON. (See "Main Power and Energy Saver Key.")

#754

Cause	The client machine is not functioning or the network is down when device information is being delivered. The destination setting is incorrect.
Remedy	Check the client machine and network. Check the destination settings.

#755

Cause 1	The fax could not be sent from the Remote Fax client machine because TCP/IP is not operating normally.
Remedy	Check [TCP/IP Settings] in [Preferences] (Settings/Registration).
Cause 2	The IP address is not set.
Remedy	Check [TCP/IP Settings] in [Preferences] (Settings/Registration).
Cause 3	When the machine was turned ON, an IP address was not assigned to the machine by the DHCP or Auto IP server.
Remedy	Check [TCP/IP Settings] in [Preferences] (Settings/Registration).

#761

Cause	A PDF or XPS file with a digital signature could not be sent, because a digital certificate or key pair registered in the machine is corrupt or could not be accessed.
Remedy 1	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, re-install it. (See "Digital Signatures" and "Installing/Checking/Deleting a User Signature Certificate File and Key Pair File.")
Remedy 2	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. (See "Digital Signatures.")

#762

Cause	Could not send to a domain that is not registered as an allowed domain, because [Allow MDN Not via Server] is set to 'On'.
Remedy	Set [Allow MDN Not via Server] to 'Off', or register the domain as an allowed domain, and try to send again. (See "Restricting the Domains to Which E-mail/I-Fax Documents Can Be Sent.")

#766

Cause	The certificate used to send a PDF or XPS with a digital signature has expired.
Remedy 1	Update the certificate, or use a certificate which has not expired.
Remedy 2	Set the date and time of the machine to the correct date and time. (See "Current Date and Time.")

#770

Cause 1	Data could not be sent with WebDAV, because the WebDAV server or proxy server does not support SSL communications.
Remedy 1	Check the settings for the WebDAV server.
Remedy 2	Check the proxy server, if you are communicating via a proxy server.
Cause 2	Verification of the SSL server certificate was attempted when sending with WebDAV because [Confirm SSL Certificate for WebDAV TX] is set to 'On', but verification failed and sending could not be performed.
Remedy 1	Using the Remote UI, confirm that the CA certificate which signed the SSL server certificate of the WebDAV server is installed on your machine.
Remedy 2	Confirm that the SSL server certificate of the WebDAV server is valid.
Remedy 3	Make sure that the SSL server certificate is not a self-signed certificate.
Cause 3	Verification of the SSL server certificate was attempted when accessing the folders/files in the Advanced Space of another imageRUNNER ADVANCE machine opened as a WebDAV server because [Confirm SSL Certificate for Network Access] is set to 'On', but verification failed and the operation could not be completed.
Remedy 1	Using the Remote UI, confirm that the CA certificate which signed the SSL server certificate of the Advanced Space of another imageRUNNER ADVANCE machine opened as a WebDAV server, is installed on your machine.
Remedy 2	Confirm that the SSL server certificate of the Advanced Space of another imageRUNNER ADVANCE machine opened as a WebDAV server is valid.
Remedy 3	Make sure that the SSL server certificate is not a self-signed certificate.

#771

Cause 1	The setting for the Remote Fax Server Address is incorrect.
Remedy	Check [Remote Fax TX Settings]. (See "Remote Fax TX Settings.")
Cause 2	The Remote Fax Server has not been started.
Remedy	Check the Remote Fax Server.
Cause 3	The network is not connected.
Remedy	Check the status of the network.
Cause 4	The Remote Fax server could not be connected to because the machine could not connect to the DNS server.
Remedy 1	Check the DNS server name in [Communication Settings]. (See "Common Communication Settings for E-Mail/I-Fax.")
Remedy 2	Check that the DNS server is functioning normally.

#773

Cause 1	[Optimize PDF for Web] is set to 'On', and PDF modes that cannot be set are selected. (See "Optimizing PDF for Web.")
Remedy	Set only one of the following: Device Signature, User Signature, or Reader Extensions. Alternatively, set [Optimize PDF for Web] to 'Off'.
Cause 2	[Format PDF to PDF/A] is set to 'On', and PDF modes that cannot be set are selected. (See "Formatting PDF Files to PDF/A.")
Remedy	Cancel the Reader Extensions, Encrypt, and Visible Signatures settings. Alternatively, set [Format PDF to PDF/A] to 'Off'.

#801

Cause 1	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.
Remedy	Check that the SMTP server is functioning normally. Check the status of the network.
Cause 2	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.
Remedy	Check that SMTP is operating normally. Check the status of the network and file server. Check the settings for the destination.
Cause 3	You are trying to send a file to a destination for which you have no write permission.
Remedy	Check the address settings.
Cause 4	When the machine tried to send a file to the server, a file with the same name already existed on the server, and that file could not be overwritten.
Remedy	Change the settings on the file server to enable the file to be overwritten, or contact the server administrator.
Cause 5	When the machine tried to send a file to the server, either the folder name was incorrectly specified or the password was incorrect.
Remedy	Check the address settings.

#802

Cause	The SMTP server name specified in Communication Settings is incorrect. The DNS server name specified in DNS Settings is incorrect. Connection to the DNS server failed.
Remedy	Check the settings for the SMTP Server Name and DNS Server Name in Communication Settings. (See "Common Communication Settings for E-Mail/I-Fax.") Check that the DNS server is functioning normally.

#803

Cause	The connection was interrupted due to reasons on the recipient's side before all of the pages could be sent.
Remedy	Re-enter the group destination, and try sending again.

#804

Cause 1	Unable to match the specified folder path when sending data to a file server.
Remedy	Check the destination.
Cause 2	You have no permission to access the folder/file, or the folder/file may be deleted in other operations.
Remedy	Change the settings on the file server to enable access to the folder, or contact the server administrator.

#806

Cause 1	An incorrect user name or password was specified for the sending of a file to a file server.
Remedy	Change the user name or password.
Cause 2	An incorrect destination was specified for the sending of an e-mail message or I-fax.
Remedy	Check the e-mail or I-fax address.

#807

Cause	You do not have access privileges for the specified directory.
Remedy	Set access privileges for the server directory, or send to a directory that you have access privileges for. Alternatively, contact your System Manager.

#810

Cause 1	A POP (Post Office Protocol) server connection error occurred when receiving an I-fax.
Remedy	Check the settings for the POP Server in Communication Settings. (See "Common Communication Settings for E-Mail/I-Fax.") Confirm that the POP server is functioning normally. Check the status of the network.
Cause 2	The POP server returned an error during the connection.
Remedy	Check the settings for the POP Server in Communication Settings. (See "Common Communication Settings for E-Mail/I-Fax.") Confirm that the POP server is functioning normally. Check the status of the network.
Cause 3	A timeout error occurred on the server while connecting to the POP server.
Remedy	Check the settings for the POP Server in Communication Settings. (See "Common Communication Settings for E-Mail/I-Fax.") Confirm that the POP server is functioning normally. Check the status of the network.

#815

Cause	You cannot log on to the file server because the machine is printing a document sent to that server. Simultaneous connections are not possible.
Remedy	Wait for a few moments before trying to send the data again. Alternatively, stop the PServer.

#816

Cause	Printing could not be performed because the maximum number of prints set in Department ID Management was exceeded.
Remedy	Contact your System Manager.

#818

Cause	The received data is not in a printable file format.
Remedy	Ask the sender to change the file format and resend the data.

#819

Cause	You have received data that cannot be processed (MIME information is incorrect).
Remedy	Check the settings, and ask the sender to resend the data.

#820

Cause	You have received data that cannot be processed (BASE 64 or uuencode is incorrect).
Remedy	Check the settings, and ask the sender to resend the data.

#821

Cause	You have received data that cannot be processed (TIFF analysis error).
Remedy	Check the settings, and ask the sender to resend the data.

#822

Cause	You have received data that cannot be processed (image data cannot be decoded).
Remedy	Check the settings, and ask the sender to resend the data.

#825

Cause 1	Printing could not be performed because the Department ID and PIN for a reserved or executing printing job were deleted, or the PIN was changed.
Remedy	Try performing the job again with the new Department ID and PIN. Register the Department ID and PIN. If you do not know the PIN, contact your System Manager.
Cause 2	Device information could not be delivered because the System Manager is registered on the destination client machine but not on the host machine. Or device information could not be delivered because the System Manager ID and System PIN registered in the client machine differ from the System Manager ID and System PIN registered in the host machine.
Remedy	Register the same System Manager ID and System PIN in both the host machine and the destination client machine, and then try delivering the device information again.

#827

Cause	You have received data that cannot be processed (contains MIME information that is not supported).
Remedy	Check the settings, and ask the sender to resend the data.

#828

Cause	You have received HTML data.
Remedy	Ask the sender to use a file format other than HTML, and then resend the data.

#829

Cause	Data that contains more than 1,000 pages was received.
Remedy	This machine can print or store up to 999 pages of data in memory, but will delete any data that exceeds this limit. Ask the sender to resend the remaining pages.

#830

Cause	A DSN (Delivery Status Notification) error notification was received because of an incorrect I-fax address or destination setting, or because the data size of the sent documents exceeds the mail server capacity.
Remedy 1	Check the I-fax address or destination setting.
Remedy 2	Set Maximum Data Size for Sending so that it is less than the mail server capacity. (See "Maximum Data Size for Send.")
Remedy 3	Check the status of the mail server, DNS server, and network.

#831

Cause	An I-fax document could not be received using SMTP because of the Receive Filter setting in Firewall Settings.
Remedy	Reset the Receive Filter setting in Firewall Settings. (See "Protocol Settings.")

#832

Cause	DSN (Delivery Status Notification) mail was not sent because TCP/IP Settings in Network or Communication Settings in E-Mail/I-Fax Settings have not been set. Alternatively, DSN mail was not sent due to a problem with the mail server.
Remedy 1	Check the communication settings, DNS settings, and IP address settings. (See "Common Communication Settings for E-Mail/I-Fax," "TCP/IPv4 Settings," and "TCP/IPv6 Settings.")
Remedy 2	Check the status of the mail server and DNS server.

#833

Cause	MDN (Mail Delivery Notification) mail was not sent because TCP/IP Settings have not been set, or due to a problem with the mail server.
Remedy 1	Check the communication settings, DNS settings, and IP address settings. (See "Common Communication Settings for E-Mail/I-Fax" and "Protocol Settings.")
Remedy 2	Check the status of the mail server and DNS server.

#834

Cause	An MDN (Mail Delivery Notification) error notification was received because of an incorrect I-fax address or destination setting, or because trouble occurred in the network or mail server. Alternatively, the memory of the receiving machine is full.
Remedy	Check the I-fax address or destination setting.

#835

Cause	The maximum number of text lines for receiving an I-fax has been exceeded.
Remedy	Ask the sender to reduce the amount of text data in the body of the document, and then resend the data.

#837

Cause	A connection request was received from a host whose connection is restricted by the Receive Filter settings in Firewall Settings.
Remedy	Check the Receive Filter settings in Firewall Settings. (See "Protocol Settings.") This may also represent a hacking attempt via unauthorized access.

#839

Cause	The user name or password specified in Communication Settings is incorrect.
Remedy	Check the user name and password set for <SMTP Authentication (SMTP AUTH)> in Communication Settings. (See "Common Communication Settings for E-Mail/I-Fax.")

#841

Cause	An encryption algorithm that matches the mail server does not exist for sending e-mail or I-fax.
Remedy 1	Set Allow SSL to 'Off' in Communication Settings. (See "Common Communication Settings for E-Mail/I-Fax.")
Remedy 2	Add the same encryption algorithm as the mail server in the mail server settings.

#842

Cause 1	The mail server requested authentication using the client certificate for sending an e-mail or I-fax.
Remedy 1	Set Allow SSL to 'Off' in Communication Settings. (See "Common Communication Settings for E-Mail/I-Fax.")
Remedy 2	Change the mail server settings so that a client certificate is not requested when sending.
Cause 2	Verification of the SSL server certificate was attempted when sending with SMTP because [Confirm SSL Certificate for SMTP TX] is set to 'On', but verification failed and sending could not be performed.
Remedy 1	Using the Remote UI, confirm that the CA certificate which signed the SSL server certificate of the SMTP server is installed on your machine.
Remedy 2	Confirm that the SSL server certificate of the SMTP server is valid.
Remedy 3	Make sure that the SSL server certificate is not a self-signed certificate.

#843

Cause	There is a large difference between the current time set in the KDC (Key Distribution Center) server and the time set in the machine.
Remedy 1	Adjust the current date and time in Date/Time Settings. (See "Current Date and Time.")
Remedy 2	Adjust the current time set in the KDC (Key Distribution Center) server.

#844

Cause 1	When sending with POP before SMTP, SSL encrypted communication with the POP server failed.
Remedy 1	Check the SSL encrypted communication setting of the POP server.
Remedy 2	Set <Allow SSL (POP)> in [Communication Settings] to 'Off'. If the problem cannot be solved, set <POP Authentication Before Send> in [Communication Settings] to 'Off', and change the communication setting to the other except for the POP before SMTP. (See "Common Communication Settings for E-Mail/I-Fax.")
Cause 2	Verification of the SSL server certificate was attempted when receiving with POP because [Confirm SSL Certificate for POP RX] is set to 'On', but verification failed and receiving could not be performed.
Remedy 1	Using the Remote UI, confirm that the CA certificate which signed the SSL server certificate of the POP server is installed on your machine.
Remedy 2	Confirm that the SSL server certificate of the POP server is valid.
Remedy 3	Make sure that the SSL server certificate is not a self-signed certificate.

#845

Cause	When sending with POP before SMTP, POP authentication (POP AUTH) failed.
Remedy 1	Check the settings of the POP address and POP password in [Communication Settings]. (See "Common Communication Settings for E-Mail/I-Fax.")
Remedy 2	Check the POP authentication setting of the POP server.
Remedy 3	Select [Standard] or [APOP] for <POP AUTH Method> in [Communication Settings]. If the problem cannot be solved, set <POP Authentication Before Send> in [Communication Settings] to 'Off', and change the communication setting to the other except for the POP before SMTP. (See "Common Communication Settings for E-Mail/I-Fax.")

#846

Cause	When sending with POP before SMTP, POP authentication (APOP) failed.
Remedy 1	Check the settings of the POP address and POP password in [Communication Settings]. (See "Common Communication Settings for E-Mail/I-Fax.")
Remedy 2	Check the APOP setting of the POP server.
Remedy 3	Select [Standard] or [POP AUTH] for <POP AUTH Method> in [Communication Settings]. If the problem cannot be solved, set <POP Authentication Before Send> in [Communication Settings] to 'Off', and change the communication setting to the other except for the POP before SMTP. (See "Common Communication Settings for E-Mail/I-Fax.")

#849

Cause	Device information could not be delivered because the destination client machine is executing a job.
Remedy	Deliver the device information again after the destination client machine has finished executing its job.

#850

Cause	Device information could not be delivered because the destination client machine is operating a screen related to the device information.
Remedy	Check the device information that was not delivered, and then deliver the device information again. (See "Checking the Communication Log.")

#851

Cause 1	There is insufficient memory remaining in the system.
Remedy	Check the memory of the machine, and delete unnecessary files in the Fax/I-Fax Inbox.(See "Fax/I-Fax Inbox.")
Cause 2	The memory for image data is full.
Remedy	Delete unnecessary files and files with errors to make more memory available. (See "Fax/I-Fax Inbox.")
Cause 3	The scanned file cannot be stored because the number of files stored in the Fax/I-Fax Inbox has exceeded the upper limit.
Remedy	Delete files stored in the Fax/I-Fax Inbox. (See "Fax/I-Fax Inbox.")

#852

Cause	An error occurred because the main power was turned OFF due to an unspecified cause while a job was being processed.
Remedy	Check that the power plug is firmly inserted into the power outlet, and that it is not in a state where the power can easily be turned OFF. Try processing the job again, if necessary. (See "Main Power and Energy Saver Key.")

#853

Cause 1	The job could not be executed when you tried to print a large number of pages on the printer, due to insufficient resources.
Remedy	Reduce the number of pages to print, or execute the job again when there are no other reserved print jobs.
Cause 2	When sending print data to the machine from a computer, the job could not be executed because it was cancelled from the printer driver.
Remedy	Perform the operation again.
Cause 3	The spool region for the received data became full and all the data from the host could not be spooled with [Use Spool Function] set to 'On' in [Network Settings] in [Preferences] (Settings/Registration).
Remedy	Set [Use Spool Function] to 'Off' in [Network Settings] in [Preferences] (Settings/Registration), and perform the operation again. (See "Communication Environment Setup.")
Cause 4	The maximum received data size was exceeded when processing the received data.
Remedy	Perform printing again when all the jobs are complete. If you still cannot perform printing, check the sent data.
Cause 5	The maximum number of secure print jobs that can be received at the same time was exceeded.
Remedy	Execute or erase secure print jobs stored in the machine, and perform the operation again.

#854

Cause	Device information was delivered from a machine of a different model group with [Restrict Receiving Device Information] set to 'On' in [Device Information Delivery Settings] in [Management Settings] (Settings/Registration) on the destination client machine.
Remedy	Set [Restrict Receiving Device Information] to 'Off' in [Device Information Delivery Settings] in [Management Settings] (Settings/Registration), and deliver the device information again. (See "Restricting the Reception of Device Information.")

#855

Cause	Device information could not be delivered because it included a language that cannot be handled by the destination client machine.
Remedy	Contact your local authorized Canon dealer.

#856

Cause	The job was cancelled because the hard disk region for saving temporary data became full.
Remedy	Contact your System Manager.

#857

Cause	Data reception timed out or the job was cancelled on the host.
Remedy	Check the network status, and perform printing again.

#858

Cause 1	A problem occurred in the print data.
Remedy	Change the print data or print settings, and perform printing again.
Cause 2	Printing was executed using a protocol that is not supported by the machine.
Remedy	Confirm the protocols supported by the machine with your System Manager, and use the appropriate protocol to print.

#859

Cause	A compression error occurred with the image data.
Remedy	Check the original and the settings, and then try scanning again.

#860

Cause 1	A paper jam occurred during printing.
Remedy	Remove the jammed paper, reload the paper, and perform printing again.
Cause 2	Transparencies not made for the machine were used.
Remedy	Perform printing again using transparencies made for the machine.
Cause 3	A print job was sent using a PDL that is not supported by the machine.
Remedy	Confirm the PDLs supported by the machine with your System Manager, and use the appropriate printer driver.
Cause 4	An unsupported combination of functions was specified.
Remedy	Change the print data resolution or other print settings, and perform printing again.

#861

Cause	An error occurred while processing the print data or image data.
Remedy	Change the print data or print settings, and perform printing again.

#862

Cause 1	An unsupported combination of functions was specified.
Remedy	Change the print data or print settings, and perform printing again.
Cause 2	Data not guaranteed to be compatible was printed.
Remedy	Change the print data or print settings, and perform printing again.

#863

Cause	An error occurred while processing the print data or image data.
Remedy	Check the settings, and then try the operation again.

#865

Cause 1	The functions related to job execution are restricted.
Remedy	Contact your System Manager.
Cause 2	The maximum number of secure print jobs that can be received at the same time was exceeded.
Remedy	Execute or erase secure print jobs stored in the machine, and perform the operation again. (See "Secure Print" and "Cancelling Print Jobs.")

#868

Cause	Failed to communicate with the destination when sending with WebDAV, because access via a proxy server was requested (received HTTP Error 305: Use Proxy).
Remedy 1	Check the settings for the WebDAV server.
Remedy 2	Check the proxy settings. (See "Protocol Settings.")

#869

Cause	Received a response from the destination stating that authentication failed when sending with WebDAV (received HTTP Error 401: Unauthorized).
Remedy 1	Check the user name and password for the destination.
Remedy 2	Check the security settings of the WebDAV server.

#870

Cause	Received a response from the destination stating that the request was denied when sending with WebDAV (received HTTP Error 403: Forbidden).
Remedy 1	Wait a few moments, and then try again.
Remedy 2	Check the address settings.
Remedy 3	Check the settings for the WebDAV server.

#871

Cause	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).
Remedy	Check the address settings.

#872

Cause	Received a response from the destination stating that access is denied when sending with WebDAV (received HTTP Error 405: Method Not Allowed).
Remedy	Check the settings for the WebDAV server.

#873

Cause	Received a response from the destination stating that proxy authentication failed when sending with WebDAV (received HTTP Error 407: Proxy Authentication Required).
Remedy	Check the proxy settings. (See "Protocol Settings.")

#874

Cause	Received a response from the destination stating that the connection timed out when sending with WebDAV (received HTTP Error 408: Request Timeout).
Remedy 1	Wait a few moments, and then try again.
Remedy 2	Check the settings for the WebDAV server.

#875

Cause	Received a response from the destination stating that chunked encoding was denied when sending with WebDAV (received HTTP Error 411: Length Required).
Remedy 1	Set Use Chunked Encoding with WebDAV Sending to 'Off'. (See "Dividing Data into Chunks When Sending with WebDAV.")
Remedy 2	Check the settings for the WebDAV server.

#876

Cause	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).
Remedy	Check the settings for the WebDAV server.

#877

Cause	Received a response from the destination stating that the URI (host name + folder path) was too long when sending with WebDAV (received HTTP Error 414: Request-URI Too Long).
Remedy	Check the settings for the WebDAV server.

#878

Cause	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).
Remedy	Check the settings for the WebDAV server.

#879

Cause	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).
Remedy 1	Check the settings for the WebDAV server.
Remedy 2	If you are sending via a proxy server without using SSL communication, set Use Chunked Encoding with WebDAV Sending to 'Off'. (See "Dividing Data into Chunks When Sending with WebDAV.")

#880

Cause	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).
Remedy 1	Check the settings for the WebDAV server.
Remedy 2	Check the settings of the proxy server.

#881

Cause	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).
Remedy	Check the settings for the WebDAV server.

#882

Cause	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).
Remedy 1	Check the settings for the WebDAV server.
Remedy 2	Check the settings of the proxy server.

#883

Cause	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).
Remedy	Check the settings for the WebDAV server.

#884

Cause	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).
Remedy	Check the settings for the WebDAV server.

#885

Cause	An unexpected error occurred when sending with WebDAV.
Remedy 1	Check the settings for the WebDAV server.
Remedy 2	Check the settings of the proxy server.

#886

Cause	Received a response from the destination stating that the request was invalid when sending with WebDAV (received HTTP Error 400: Bad Request).
Remedy	If you are sending via a proxy server without using SSL communication, Set Use Chunked Encoding with WebDAV Sending to 'Off'. (See "Dividing Data into Chunks When Sending with WebDAV.")

#889

Cause	The original cannot be scanned or printed because it is embedded with job restriction information.
Remedy	Check the job restriction information, or contact your System Manager.

#899

Cause	The e-mail message or I-fax has been successfully sent, but reception may be incomplete because the transmission was relayed via multiple servers. Check the following, as necessary.
Remedy 1	If you are using POP RX, press [Check I-Fax RX] on the Status Monitor/Cancel screen to check whether the machine has received an error notification. (See "Operations from the Receive Screen.")
Remedy 2	If you are using POP RX and you set something other than '0 min' for [POP Interval] or set to receive error notification via SMTP, the error notification received by the machine is automatically printed. (See "Common Communication Settings for E-Mail/I-Fax.")
Remedy 3	Contact the other party.

#904

Cause	Destinations registered in [Favorite Settings] are not updated when the Address Book is retrieved using device information delivery from an iR/imagePRESS series machine connected to the network.
Remedy	Register [Favorite Settings] again from the touch panel display of the machine.

#905

Cause	The job could not be executed because a network error occurred.
Remedy	Check the path length and access privileges of the server, and whether the file or folder is in use.

#995

Cause	Reserved communication jobs were cleared.
Remedy	Reserve the jobs again, if necessary.

» Problem Solving » List of Error Codes without Messages

0JJE-0HE