 |
|
|
NOTE
|
|
If a send job is canceled, <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
|
Check the originals and the settings, and perform the operation again.
|
|
Cause 2
|
Different sized originals were scanned in the 2-Sided Original mode without setting the Different Size Originals mode.
|
|
Remedy
|
Check the originals and the settings, and perform the operation again.
|
|
Cause 3
|
A paper jam occurred.
|
|
Remedy
|
After removing the paper jam, check the originals and the settings, and perform the operation again.
|
|
Cause
|
Communication took longer than the preset time (64 minutes), causing an error.
|
|
Remedy 1
|
When sending the document, lower the resolution or divide the document into several parts. (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.
|
|
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.
|
|
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.
|
|
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.
|
|
Cause 1
|
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.
|
|
Cause 2
|
The document could not be sent because the memory of the machine is full.
|
|
Remedy
|
Delete unnecessary documents and documents with errors to make more memory available.
|
|
Cause 3
|
When performing memory sending, the image could not be stored in the memory.
|
|
Remedy 1
|
Perform memory sending again.
|
|
Remedy 2
|
Send the document with direct sending.
|
|
Cause 4
|
There was a problem with the scanned image when performing direct sending.
|
|
Remedy
|
Perform direct 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
|
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.")
|
|
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.")
|
|
Cause
|
The recipient's machine does not support confidential sending or subaddresses.
|
|
Remedy
|
Send the document without using confidential sending or subaddresses.
|
|
Cause 1
|
The destination for confidential sending specified for the recipient's machine did not exist.
|
|
Remedy
|
Check the destination for confidential sending in the recipient's machine and try sending again.
|
|
Cause 2
|
There was insufficient memory in the recipient's machine.
|
|
Remedy
|
Ask the recipient to make more memory available.
|
|
Cause
|
The recipient's machine does not support the forwarding function or subaddresses.
|
|
Remedy
|
Directly send to the forwarding destination.
|
|
Cause 1
|
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, and then try sending the document again.
|
|
Cause 2
|
The document could not be sent because the memory of the machine is full.
|
|
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, and then try sending the document again.
|
|
Cause
|
The sending process was interrupted because the user phone number and user name were not registered.
|
|
Remedy
|
Register the user phone number and user name, and perform sending again. (See "Fax Line Settings.")
|
|
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.
|
|
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.
|
|
Cause
|
The job was canceled.
|
|
Remedy
|
Perform the job again.
|
|
Cause 1
|
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.
|
|
Cause 2
|
There was insufficient memory in the recipient's machine.
|
|
Remedy
|
Ask the recipient to make more memory available.
|
|
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), and perform sending again. If you do not know the PIN, contact the administrator. |
|
Cause 2
|
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 3
|
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.
|
|
Cause
|
The document could not be sent because the memory is full.
|
|
Remedy
|
Wait a few moments, and then try again after the other send jobs are complete.
|
|
Cause 1
|
An error occurred while converting the image.
|
|
Remedy
|
Lower the resolution, and perform sending again.
|
|
Cause 2
|
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 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.") |
|
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.")
|
|
Cause
|
The send operation was interrupted because the size of the image data is larger than the maximum data size sets in [Maximum Data Size for Sending].
|
|
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 currently being imported/exported from the Remote UI, or the machine is busy with other send related functions.
|
|
Remedy
|
Wait a few moments. Try sending again after the other send jobs are complete.
|
|
Cause
|
The document in Mail Box or Fax/I-Fax Inbox was deleted before the link to it was sent via e-mail.
|
|
Remedy
|
Store the necessary document in the Mail Box or Fax/I-Fax Inbox again, and then send the link again via e-mail.
|
|
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 Box 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.
|
|
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.")
|
|
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.")
|
|
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).
|
|
Cause
|
An error occurred on while sending a link via e-mail to the Mail Box in which the file is stored.
|
|
Remedy
|
Contact your administrator.
|
|
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.")
|
|
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.")
|
|
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
|
The number of trials allowed for the Scan and Send function reached the upper limit.
|
|
Remedy
|
To continue using the function, purchase the official optional product.
|
|
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 Box 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 Box 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 Box 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.
|
|
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.
|
|
Cause 1
|
The settings of the Rights Management Server are incorrect.
|
|
Remedy
|
Check [Rights Management Server Settings]. (See "Setting a Rights Management Server.")
|
|
Cause 2
|
Cannot start the Rights Management Server.
|
|
Remedy
|
Check the Rights Management Server.
|
|
Cause 3
|
The network is not connected.
|
|
Remedy
|
Check the status of the network.
|
|
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 or User Signature. 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 Apply Policy, Encrypt, and Visible Signatures settings. Alternatively, set [Format PDF to PDF/A] to 'Off'.
|
|
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.
|
|
Cause 1
|
The SMTP server name specified in Communication Settings is incorrect.
|
|
Remedy
|
Check the SMTP server name set in Communication Settings. (See "Common Communication Settings for E-Mail/I-Fax.")
|
|
Cause 2
|
The DNS server address specified in the DNS settings is incorrect.
|
|
Remedy
|
Check the DNS server address specified in the DNS settings.
|
|
Cause 3
|
Connection to the DNS server failed.
|
|
Remedy
|
Check that the DNS server is functioning normally.
|
|
Cause 4
|
The settings for the FTP server specified as the destination are incorrect.
|
|
Remedy
|
Check the FTP server specified as the destination. (See "FTP Server Settings.")
|
|
Cause 5
|
Connection to the FTP server failed.
|
|
Remedy
|
Check that the FTP server is functioning normally.
|
|
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
|
Sending could not be performed when sending to the SMB server because the server had insufficient space available.
|
|
Remedy
|
Delete unnecessary documents and documents with errors on the server to make more space available. Otherwise, contact your 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
|
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 administrator.
|
|
Cause
|
When the machine tried to send a file to the SMB server, a file with the same name already existed on the server, and that file could not be overwritten.
|
|
Remedy 1
|
Rename the file and perform sending again.
|
|
Remedy 2
|
Change the settings of the SMB server to allow overwriting. Otherwise, contact your server administrator.
|
|
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.
|
|
Cause
|
A POP server authentication error (user account error or password 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.")
|
|
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.
|
|
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.
|
|
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.")
|
|
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.
|
|
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.
|
|
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.
|
|
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.
|
|
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]. (See "Common Communication Settings for E-Mail/I-Fax.")
|
|
Remedy 4
|
Set <POP Authentication Before Send> in [Communication Settings] to 'Off' → change the communication setting to a setting other than POP before SMTP. (See "Common Communication Settings for E-Mail/I-Fax.")
|
|
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 [APOP] for <POP AUTH Method> in [Communication Settings]. (See "Common Communication Settings for E-Mail/I-Fax.")
|
|
Remedy 4
|
Set <POP Authentication Before Send> in [Communication Settings] to 'Off', and change the communication setting to a setting other than POP before SMTP. (See "Common Communication Settings for E-Mail/I-Fax.")
|
|
Cause
|
The job was canceled because the hard disk region for saving temporary data became full.
|
|
Remedy
|
Contact your administrator.
|
|
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.")
|
|
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.
|
|
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.
|
|
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.
|
|
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.
|
|
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.")
|
|
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.
|
|
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.
|
|
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.
|
|
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.
|
|
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.
|
|
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.")
|
|
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.
|
|
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.
|
|
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.
|
|
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.
|
|
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.
|
|
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.
|
|
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.")
|
|
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 administrator.
|
|
Cause 1
|
The e-mail or I-fax was sent normally. However, reception may be incomplete because the transmission was relayed via multiple servers.
|
|
Remedy
|
Contact the other party.
|
|
Cause 2
|
The fax was sent normally from the remote fax client. However, reception may be incomplete because the transmission was relayed via a remote fax server.
|
|
Remedy 1
|
Check whether the fax was sent in the transmission results of the remote fax server.
|
|
Remedy 2
|
Check the status of the server and network.
|
|
Remedy 3
|
Contact the other party.
|
|
Cause
|
Reserved communication jobs were cleared.
|
|
Remedy
|
Reserve the jobs again, if necessary.
|
