List of Error Codes without Messages

If an error occurs while a document is being sent or received, an error code appears on the job log in the Status Monitor/Cancel screen. This error code is also included in various reports. Check the error code, and then take the required steps to solve the problem. (See "Checking and Cancelling Jobs from the Job Status Screen.")

#001	#706	#773	#822	#841	#870	#882
#003	#711	#801	#827	#842	#871	#883
#009	#712	#802	#828	#843	#872	#884
#011	#751	#803	#829	#844	#873	#885
#022	#752	#804	#830	#845	#874	#886
#037	#753	#806	#831	#846	#875	#899
#107	#754	#810	#832	#847	#876	#995
#701	#755	#815	#833	#851	#877
#702	#761	#818	#834	#852	#878
#703	#762	#819	#835	#859	#879
#704	#766	#820	#837	#868	#880
#705	#770	#821	#839	#869	#881

#001

Cause 1	Different sized originals were scanned without setting the Different Size Originals mode.
Remedy	Set the Different Size Originals mode, and then try scanning again.
Cause 2	Different sized originals were scanned in the 2-Sided Original mode without setting the Different Size Originals mode.
Remedy	Set the Different Size Originals mode, and then try scanning again.

#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.

#009

Cause 1	There is no paper.
Remedy	Load paper. (See "Routine Maintenance," in the Basic Operation Guide.)
Cause 2	The paper drawer or paper deck is not correctly inserted into the machine.
Remedy	Insert the paper drawer or paper deck correctly. (See "Routine Maintenance," in the Basic Operation Guide.)

#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.

#022

Cause 1	Forwarding could not be performed because all of the addresses stored in the specified group destination have been deleted.
Remedy	Re-enter the group destination, and 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	Forwarding could not be performed, because a group address that includes a destination using WebDAV is selected as a forwarding destination.
Remedy	Specify a forwarding destination that does not use WebDAV.

#037

Cause	The document could not be received because there was insufficient memory available.
Remedy	Delete documents with errors to make more memory available. (See "Checking the Detailed Information for/Deleting a Document in the Memory RX Inbox.")

#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 documents to make more memory available. (See "Checking the Detailed Information for/Deleting a Document in the Memory RX Inbox.")
Remedy 3	If this problem occurs frequently, contact your local authorized Canon dealer.

#701

Cause 1	The specified Department ID does not exist, or the PIN code has changed.
Remedy	Enter the correct Department ID or PIN code using - (numeric keys) on the control panel, and then try sending again.
Cause 2	The Department ID or PIN code was changed during the job.
Remedy	Try performing the job again with the new Department ID and PIN code. If you do not know the PIN code, contact your system administrator.
Cause 3	<Allow Printer Jobs With Unknown IDs>/<Allow Scan Jobs With Unknown IDs> is set to 'Off'.
Remedy	Set <Allow Printer Jobs With Unknown IDs>/<Allow Scan Jobs With Unknown IDs> to 'On' in [Department ID Management]. (See "Accepting Jobs with Unknown or Unspecified Department IDs.")

#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 documents 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 Control Panel Power.")

#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 Control Panel Power.")

#705

Cause	The send operation was interrupted because the size of the image data is larger than the Maximum Data Size for Sending set in [E-Mail/I-Fax Settings] in [Send] in [Function Settings] (Settings/Registration).
Remedy	Change the Maximum Data Size for Sending setting in [E-Mail/I-Fax Settings]. Select a lower resolution, or if you are using I-fax, decrease the number of pages containing images that you are sending each time, so that you do not exceed the Maximum Data Size for Sending limit. (See "Maximum Data Size for Send.") Depending on the destination conditions, it may be possible to divide the data.

#706

Cause	The address book is currently being imported/exported from the Remote User Interface, or the machine is busy with other send related functions.
Remedy	Wait until the Address Book Import/Export function from the Remote UI or the other sending component is complete, and then try sending again.

#711

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

#712

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

#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	Check the recipient's address. 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 Preferences (Settings/Registration). (See "Protocol Settings.")

#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, Select error, etc.) occurred while sending an e-mail message.
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 Control Panel Power.")

#754

Cause	The server is not functioning or the network is down. The destination setting is not correct.
Remedy	Check the server and network. Check the destination's address settings.

#755

Cause 1	You cannot send jobs because TCP/IP is not functioning correctly.
Remedy	Check the settings for TCP/IP. (See "Protocol Settings.")
Cause 2	The IP address is not set.
Remedy	Check the settings for TCP/IP. (See "Protocol Settings.")
Cause 3	When the machine was turned ON, an IP address was not assigned to the machine by the DHCP, RARP, or BOOTP server.
Remedy	Check the settings for TCP/IP. (See "Protocol Settings.")

#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 "Generating and Confirming a Key Pair and Device Signature Certificate and User Certificate for Adding Digital Signatures to PDF or XPS Files" and "Installing/Checking/Erasing 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 "Generating and Confirming a Key Pair and Device Signature Certificate and User Certificate for Adding Digital Signatures to PDF or XPS Files.")

#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	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.

#773

Cause 1	[Optimize PDF for Web] is set to 'On', and PDF modes that cannot be set are selected in forwarding settings. (See "Optimize 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 in forwarding settings. (See "Format PDF as PDF/A.")
Remedy	Cancel the 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	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.

#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.

#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.

#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	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.

#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	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.")

#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.")

#847

Cause	Could not save the received document in the Confidential Fax Inbox, as the memory of the Confidential Fax Inbox is full.
Remedy	Delete unnecessary documents stored in the Confidential Fax Inbox or the Memory RX Inbox. (See "Checking the Detailed Information for/Deleting a Document in the Memory RX Inbox.")

#851

Cause 1	There is insufficient memory remaining in the system.
Remedy	Check the system's available memory, and delete unnecessary documents in the Fax/I-Fax Inbox. (See "Checking the Detailed Information for/Deleting a Document in the Memory RX Inbox.")
Cause 2	The memory for the image data is full.
Remedy	Delete unnecessary documents and documents with errors to make more memory available. (See "Checking the Detailed Information for/Deleting a Document in the Memory RX Inbox.")
Cause 3	The scanned document cannot be stored because the number of documents stored in the inbox specified for the specified Fax/I-Fax Inbox has exceeded the upper limit.
Remedy	Delete unnecessary documents from the inbox specified for the specified Fax/I-Fax Inbox. (See "Checking the Detailed Information for/Deleting a Document in the Memory RX 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 Control Panel Power.")

#859

Cause 1	A compression error occurred with the image data.
Remedy	Check the print settings, and try printing again.
Cause 2	An original was not scanned properly, or the orientation of the original was incorrect.
Remedy 1	Check the scan settings, and try scanning again.
Remedy 2	Turn the main power OFF, wait for 10 or more seconds, and turn the main power ON again.

#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 authorization 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.")

#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	Check if the machine has received an error notification. Error notifications that the machine receives are printed automatically.
Remedy 2	Contact the other party.

#995

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

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

» Scan and Send » List of Error Codes without Messages