If an error occurs while a document is being sent or received, an error code is displayed on the job log in the Status Monitor/Cancel screen, and is included in various reports. Check what the error code is, and then take the required steps to solve the problem. (See Chapter 17, "Appendix," in Getting Started and "Status Monitor/Cancel.")
For explanations of messages that are not listed here, see "Problem Solving," "Network," and "Using the Machine to Send/Receive a Fax."
|
NOTE
|
|
If a send job is cancelled, <STOP> is printed in the Results column on the Send report.
|
|
|
|||
|
|
|||
|
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 without setting the Different Size Originals mode.
|
|
Remedy
|
Set the Different Size Originals mode, and then try scanning again.
|
|
Cause
|
Communications that take longer than the preset time (64 minutes) caused the error.
|
|
Remedy 1
|
Reduce the resolution or divide the document into two or more parts, and then try sending the document again. (See "Resolution Settings.")
|
|
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.
|
|
Cause 1
|
There is no paper.
|
|
Remedy
|
Load paper. (See "Maintenance.")
|
|
Cause 2
|
The paper drawer or paper deck is not correctly inserted into the machine.
|
|
Remedy
|
Insert the paper drawer or paper deck properly. (See "Maintenance.")
|
|
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.
|
|
Cause 1
|
Forwarding could not be performed because all of the addresses stored in the specified group destination have been deleted, or a mail box is specified as the group destination.
|
|
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
|
Re-enter the destination in the Address Book, and try sending again.
|
|
Cause 3
|
Forwarding could not be performed because a group address that includes a destination using WebDAV is selected as the forwarding destination.
|
|
Remedy
|
Specify a forwarding destination that does not use WebDAV.
|
|
Cause
|
The document could not be received because there was insufficient memory available.
|
|
Remedy
|
Delete the unnecessary documents and documents with errors from memory to increase the amount of available memory. (See "Scan and Store," "Fax/I-Fax Inbox," and "Access Stored Files.")
|
|
Cause
|
The document could not be sent because there was insufficient memory available.
|
|
Remedy 1
|
Resend the document at a lower resolution.
|
|
Remedy 2
|
Delete the unnecessary documents and documents with errors to make more memory available. (See "Scan and Store," "Fax/I-Fax Inbox," and "Access Stored Files.")
|
|
Remedy 3
|
If this problem occurs frequently, contact your local authorized Canon dealer.
|
|
Cause 1
|
The specified Department ID does not exist, or the password has changed.
|
|
Remedy
|
Enter the correct Department ID or password using
 -  (numeric keys) on the control panel, and then try sending again. |
|
Cause 2
|
The Department ID or password was changed during the job.
|
|
Remedy
|
Try performing the job again with the new Department ID and password. If you do not know the password, contact your System Manager.
|
|
Cause 3
|
<Allow Printer Jobs with Unknown IDs> in Department ID Management in User Management in Management Settings (Settings/Registration) is set to 'Off'.
|
|
Remedy
|
Set <Allow Printer Jobs with Unknown IDs> in Department ID Management in User Management in Management Settings (Settings/Registration) to 'On'. (See "Department ID Management.")
|
|
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.
|
|
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 Mail Box and 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.")
|
|
Remedy 3
|
If you are trying to send in the PDF format, you may be able to correctly send by changing the file format to other than PDF.
|
|
Cause
|
An error occurred while 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.")
|
|
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 in Send in Function Settings (Settings/Registration). 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.
|
|
Cause
|
The Address Book is being imported or exported from the Remote UI, or it is being used by another sending component.
|
|
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.
|
|
Cause
|
The Mail Box and Fax/I-Fax Inbox memory is full.
|
|
Remedy
|
Delete the unnecessary documents stored in the Mail Box and the Fax/I-Fax Inbox. (See "Scan and Store," "Fax/I-Fax Inbox," and "Access Stored Files.")
|
|
Cause
|
The maximum number of documents is already stored in the Mail Box and the Fax/I-Fax Inbox.
|
|
Remedy
|
Delete the unnecessary documents stored in the Mail Box and the Fax/I-Fax Inbox. (See "Scan and Store," "Fax/I-Fax Inbox," and "Access Stored Files.")
|
|
Cause
|
The document in the Mail Box and the Fax/I-Fax Inbox was deleted before its link was sent via e-mail.
|
|
Remedy
|
Store the necessary document in the Mail Box and the Fax/I-Fax Inbox again, and then try to send the link via e-mail.
|
|
Cause 1
|
The server is not functioning. The network is down (the server is unable to connect to the network or was disconnected).
|
|
Remedy 1
|
Check the recipient's address. Check that the network is up.
|
|
Remedy 2
|
If WebDAV sending is based on the following conditions, enable Use Chunked Encoding with WebDAV Sending in Common Settings in Send in Function Settings (Settings/Registration). (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 "Confirming TCP/IPv4 and TCP/IPv6 Settings.")
|
|
Cause 1
|
The server is not functioning. The network is down.
|
|
Remedy
|
Check that the SMTP server is operating properly. Check the network status.
|
|
Cause 2
|
The SMTP server name for e-mail or I-fax is not correct. 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 in E-Mail/I-Fax Settings in Send in Function Settings (Settings/Registration). (See "Common Communication Settings for E-Mail/I-Fax.")
|
|
Cause
|
A TCP/IP error occurred while sending an e-mail message. (Socket, Select error, etc.)
|
|
Remedy
|
Check the network cables and connectors. If the machine still does not operate normally, turn the main power OFF, and then back ON. (See "Main Power and Control Panel Power.")
|
|
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.
|
|
Cause 1
|
You cannot send jobs because TCP/IP is not functioning correctly.
|
|
Remedy
|
Check TCP/IP Settings in Network in Preferences (Settings/Registration). (See "Confirming TCP/IPv4 and TCP/IPv6 Settings.")
|
|
Cause 2
|
The IP address is not set.
|
|
Remedy
|
Check TCP/IP Settings in Network in Preferences (Settings/Registration). (See "Confirming TCP/IPv4 and TCP/IPv6 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 TCP/IP Settings in Network in Preferences (Settings/Registration). (See "Confirming TCP/IPv4 and TCP/IPv6 Settings.")
|
|
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 are sending 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.")
|
|
Remedy 2
|
If you are sending 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.")
|
|
Cause
|
Could not send to a domain that is not registered as an allowed domain because Allow MDN Not via Server in E-Mail/I-Fax Settings in Send in Function Settings (Settings/Registration) is set to 'On'.
|
|
Remedy
|
Try sending again after setting Allow MDN Not via Server in E-Mail/I-Fax Settings in Send in Function Settings (Settings/Registration) to 'Off', or registering the domain as an allowed domain. (See "Restricting the Domains to Which E-mail/I-Fax Documents Can Be Sent.")
|
|
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.")
|
|
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 of the WebDAV server.
|
|
Remedy 2
|
Check the proxy server if you are communicating via a proxy server.
|
|
Cause 1
|
If [Optimize PDF for Web] is set to 'On' in Generate File in Common in Function Settings (Settings/Registration), 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. Or, set [Optimize PDF for Web] to 'Off' in Generate File in Common in Function Settings (Settings/Registration).
|
|
Cause 2
|
If [Format PDF to PDF/A] is set to 'On' in Generate File in Common in Function Settings (Settings/Registration), PDF modes that cannot be set are selected in forwarding settings. See "Standardize PDF as PDF/A."
|
|
Remedy
|
Cancel the Encrypt, Visible Signatures, and Apply Policy settings. Or, set [Format PDF to PDF/A] to 'Off' in Generate File in Common in Function Settings (Settings/Registration).
|
|
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 network status.
|
|
Cause 2
|
The SMTP server returned an error while trying to connect. The destination is not correct. An error occurred on the server side during transmission to a file server.
|
|
Remedy
|
Check that the SMTP server is functioning normally. Check the network status. Check the destination setting. Check the status and setting of the file server.
|
|
Cause 3
|
You are sending a file to a destination to which you have no write permission.
|
|
Remedy
|
Check the destination setting.
|
|
Cause 4
|
When the machine tried to send a file to the server, a file with the same name already exists on the FTP server and that file cannot 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 is incorrectly specified or the password is incorrect.
|
|
Remedy
|
Check the destination setting.
|
|
Cause
|
The name of the SMTP Server in Communication Settings in E-Mail/I-Fax Settings in Send in Function Settings (Settings/Registration) is incorrect. The DNS server name in DNS Settings in TCP/IP Settings in Network in Preferences (Settings/Registration) is incorrect. Connection to the DNS server failed.
|
|
Remedy
|
Check the name of the SMTP Server in Communication Settings in E-Mail/I-Fax Settings in Send in Function Settings in (Settings/Registration). Check the DNS server name in DNS Settings in TCP/IP Settings in Network in Preferences (Settings/Registration). (See "Common Communication Settings for E-Mail/I-Fax.")
Check that the DNS server is functioning normally. |
|
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.
|
|
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.
|
|
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.
|
|
Cause 1
|
A POP (Post Office Protocol) server connection error occurred while receiving an I-fax.
|
|
Remedy
|
Check the POP Server name in Communication Settings in E-Mail/I-Fax Settings in Send in Function Settings (Settings/Registration). (See "Common Communication Settings for E-Mail/I-Fax.")
Confirm that the POP server is functioning normally. Check the network status. |
|
Cause 2
|
The POP server returned an error during the connection.
|
|
Remedy
|
Check the POP Server name in Communication Settings in E-Mail/I-Fax Settings in Send in Function Settings (Settings/Registration). (See "Common Communication Settings for E-Mail/I-Fax.")
Confirm that the POP server is functioning normally. Check the network status. |
|
Cause 3
|
A timeout error occurred on the server while connecting to the POP server.
|
|
Remedy
|
Check the POP Server name in Communication Settings in E-Mail/I-Fax Settings in Send in Function Settings (Settings/Registration). (See "Common Communication Settings for E-Mail/I-Fax.")
Confirm that the POP server is functioning normally. Check the network status. |
|
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.
|
|
Cause
|
The received data is not in a printable file format.
|
|
Remedy
|
Ask the sender to change the file format and resend the data.
|
|
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.
|
|
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.
|
|
Cause
|
You have received data that cannot be processed (TIFF analysis error).
|
|
Remedy
|
Check the settings, and ask the sender to resend the data.
|
|
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.
|
|
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.
|
|
Cause
|
You have received HTML data.
|
|
Remedy
|
Ask the sender to use a file format other than HTML, and then resend the data.
|
|
Cause
|
Data that contains more than 1,000 pages is 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
|
A DSN (Delivery Status Notification) error notification is 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 in E-Mail/I-Fax Settings in Send in Function Settings (Settings/Registration) so that it is less than the mail server capability. (See "Maximum Data Size for Send.")
|
|
Remedy 3
|
Check the status of the mail server, DNS server, and network.
|
|
Cause
|
An I-fax document could not be received using SMTP because of the RX Filter setting in Firewall Settings in Network in Preferences (Settings/Registration).
|
|
Remedy
|
Reset the RX Filter setting in Firewall Settings in Network in Preferences (Settings/Registration). (See "Confirming TCP/IPv4 and TCP/IPv6 Settings.")
|
|
Cause
|
DSN (Delivery Status Notification) mail was not sent because TCP/IP Settings in Network in Preferences (Settings/Registration) or Communication Settings in E-Mail/I-Fax Settings in Send in Function Settings (Settings/Registration) have not been set, or because trouble has occurred in the mail server.
|
|
Remedy 1
|
Check the DNS Settings and IP Address Settings in TCP/IP Settings in Network in Preferences (Settings/Registration), and Communication Settings in E-Mail/I-Fax Settings in Send in Function Settings (Settings/Registration). (See "Common Communication Settings for E-Mail/I-Fax" and "Confirming TCP/IPv4 and TCP/IPv6 Settings.")
|
|
Remedy 2
|
Check the status of the mail server and DNS server.
|
|
Cause
|
MDN (Mail Delivery Notification) mail was not sent because TCP/IP Settings in Network in Preferences (Settings/Registration) or Communication Settings in E-Mail/I-Fax Settings in Send in Function Settings (Settings/Registration) have not been set, or because trouble has occurred in the mail server.
|
|
Remedy 1
|
Check the DNS settings and IP Address settings in TCP/IP Settings in Network in Preferences (Settings/Registration), and Communication Settings in E-Mail/I-Fax Settings in Send in Function Settings (Settings/Registration). (See "Common Communication Settings for E-Mail/I-Fax" and "Confirming TCP/IPv4 and TCP/IPv6 Settings.")
|
|
Remedy 2
|
Check the status of the mail server and DNS server.
|
|
Cause
|
An MDN (Mail Delivery Notification) error notification is received because of an incorrect I-fax address or destination setting, or because trouble has occurred in the network or mail server. Alternatively, the memory of the receiving machine is full.
|
|
Remedy
|
Check the I-fax address and destination settings.
|
|
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.
|
|
Cause
|
A connection request was received from a host whose connection is restricted by the RX Filter settings in Firewall Settings in Network in Preferences (Settings/Registration).
|
|
Remedy
|
Check the RX Filter settings in Firewall Settings in Network in Preferences (Settings/Registration). (See "Confirming TCP/IPv4 and TCP/IPv6 Settings.")
Make sure that the connection request is made from an authorized host. |
|
Cause
|
The user name or password for <SMTP Authentication (SMTP AUTH) > in <POP AUTH Method> in Communication Settings in E-Mail/I-Fax Settings in Send in Function Settings (Settings/Registration) is incorrect.
|
|
Remedy
|
Check the user name and password for <SMTP Authentication (SMTP AUTH) > in <POP AUTH Method> in Communication Settings in E-Mail/I-Fax Settings in Send in Function Settings (Settings/Registration). (See "Common Communication Settings for E-Mail/I-Fax.")
|
|
Cause
|
The encryption algorithm that matches the mail server does not exist for sending e-mail or I-fax.
|
|
Remedy 1
|
Set Allow SSL in Communication Settings in E-Mail/I-Fax Settings in Send in Function Settings (Settings/Registration) to 'Off'. (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.
|
|
Cause
|
Authentication using the client certificate was requested by the mail server for sending an e-mail message or I-fax.
|
|
Remedy 1
|
Set Allow SSL in Communication Settings in E-Mail/I-Fax Settings in Send in Function Settings (Settings/Registration) to 'Off'. (See "Common Communication Settings for E-Mail/I-Fax.")
|
|
Remedy 2
|
Change the mail server settings so that the client certificate is not requested.
|
|
Cause
|
There is large difference between the current time set in the KDC (Key Distribution Center) server and the time set in the machine.
|
|
Remedy 1
|
Change the current date and time in Date/Time Settings in Timer/Energy Settings in Preferences (Settings/Registration). (See "Current Date and Time.")
|
|
Remedy 2
|
Change the current time set in the KDC (Key Distribution Center) server.
|
|
Cause
|
Could not save the received document in the Confidential Fax Inbox, as the memory of the Confidential Fax Inbox is full.
|
|
Remedy
|
Delete the unnecessary documents stored in the Confidential Fax Inbox or the Memory RX Inbox. (See "Fax/I-Fax Inbox.")
|
|
Cause 1
|
There is insufficient memory remaining in the system.
|
|
Remedy
|
Check the system's available memory, and delete unnecessary documents in the Mail Box and the Fax/I-Fax Inbox. (See "Scan and Store," "Fax/I-Fax Inbox," and "Access Stored Files.")
|
|
Cause 2
|
The memory for image data is full.
|
|
Remedy
|
Delete the unnecessary documents to make more memory available. (See "Scan and Store," "Fax/I-Fax Inbox," and "Access Stored Files.")
|
|
Cause 3
|
The scanned document cannot be stored because there are more than 2,000 documents in the specified box or inbox in the Mail Box or the Fax/I-Fax Inbox.
|
|
Remedy
|
Delete the unnecessary documents from the specified box or inbox in the Mail Box or the Fax/I-Fax Inbox. (See "Scan and Store," "Fax/I-Fax Inbox," and "Access Stored Files.")
|
|
Cause
|
An error occurred because the main power was turned OFF due to an unspecified cause while a job was being processed.
|
|
Remedy
|
Check to see that the power plug is firmly inserted into the power outlet and that it is not in a situation where the power can easily be turned OFF. Try processing the job again, if necessary. (See "Main Power and Control Panel Power.")
|
|
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 back ON.
|
|
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 of the WebDAV server.
|
|
Remedy 2
|
Check Proxy Settings in TCP/IP Settings in Network in Preferences (Settings/Registration). (See "Confirming TCP/IPv4 and TCP/IPv6 Settings.")
|
|
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.
|
|
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 destination.
|
|
Remedy 3
|
Check the settings of the WebDAV server.
|
|
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 destination.
|
|
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 of the WebDAV server.
|
|
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 Proxy Settings in TCP/IP Settings in Network in Preferences (Settings/Registration). (See "Confirming TCP/IPv4 and TCP/IPv6 Settings.")
|
|
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 of the WebDAV server.
|
|
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 in Common Settings in Send in Function Settings (Settings/Registration) to 'Off'. (See "Dividing Data Into Chunks When Sending With WebDAV.")
|
|
Remedy 2
|
Check the settings of the WebDAV server.
|
|
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 of the WebDAV server.
|
|
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 of the WebDAV server.
|
|
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 of the WebDAV server.
|
|
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 of the WebDAV server.
|
|
Remedy 2
|
If you are sending via a proxy server without using SSL communication, set Use Chunked Encoding with WebDAV Sending in Common Settings in Send in Function Settings (Settings/Registration) to 'Off'. (See "Dividing Data Into Chunks When Sending With WebDAV.")
|
|
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 of the WebDAV server.
|
|
Remedy 2
|
Check the settings of the proxy server.
|
|
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 of the WebDAV server.
|
|
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 of the WebDAV server.
|
|
Remedy 2
|
Check the settings of the proxy server.
|
|
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 of the WebDAV server.
|
|
Cause
|
Received a response from the destination stating that the server does not have sufficient free disk space to execute the request when sending with WebDAV (received HTTP Error 507: Insufficient Storage).
|
|
Remedy
|
Check the settings of the WebDAV server.
|
|
Cause
|
An unexpected error occurred when sending with WebDAV.
|
|
Remedy 1
|
Check the settings of the WebDAV server.
|
|
Remedy 2
|
Check the settings of the proxy server.
|
|
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 in Common Settings in Send in Function Settings (Settings/Registration) to 'Off'. (See "Dividing Data Into Chunks When Sending With WebDAV.")
|
|
Cause
|
The e-mail message or I-fax has been successfully sent. However, reception may be incomplete because the transmission may relay via multiple servers. Check the following, if necessary.
|
|
Remedy 1
|
Check if you received an error notification. The error notification the machine has received is automatically printed.
|
|
Remedy 2
|
Contact the recipient.
|
|
Cause
|
Reserved communication jobs were cleared.
|
|
Remedy
|
Reserve the jobs again, if necessary.
|