Countermeasures for Each Error Code
0YRY-0JW 1100-0K0 10XJ-0K0 1106-0K0 10YY-0K0 10H3-0JX 10H4-0JX 108A-0JY 1116-0JY
When printing or scanning is not completed normally or fax transmission or reception fails, a number starting with "#" (an error code) is displayed on the details screen for job log or a communication management report (Printing Reports and Lists). Perform the countermeasure required for the error code.
|
|
|
Some error codes may not be displayed, depending on your machine.
|
#001 to #800
#801 to #999
#001
Different size originals were scanned without setting the Different Size Originals mode.
Check the originals and the settings and scan the originals again.
#003
Communication that exceeds the specified time (64 minutes) causes an error.
Lower the resolution and try sending again.
When receiving a document, ask the other party to lower the resolution when scanning or divide the document into multiple parts.
#005
There was no response from the other party for 35 seconds.
Check that the other party can communicate, and try sending again.
The device of the other party is not a model that supports G3.
Check the device of the other party.
#009
Paper has run out.
Load paper.
The paper deck/paper drawer is not inserted correctly.
Insert the paper deck/paper drawer in all the way.
#010
Paper has run out.
Load paper.
#011
The document to send was not placed correctly.
Place the original correctly and try sending again from the start of the procedure.
#012
Could not send because the device of the other party does not have any paper.
Tell the other party to load paper.
#018
There was no response when redialing.
Check that the other party can communicate, and redial again.
Could not send because the other party was making a call, etc.
Check that the other party can communicate, and try sending again.
Could not send because the settings of the device of the other party do not match.
Check the settings of the other party, and try sending again.
#019
When sending a fax from a remote fax client machine, sending could not be performed because the memory of the remote fax server machine became full.
Try sending again after the other sending to the remote fax server machine is complete.
Delete unnecessary documents and error documents from the remote fax server machine to free up space.
#022
Forwarding could not be performed because the content of the group destination specified as the forwarding destination was deleted or only included a Mail Box.
Specify another destination, and try sending again.
When sending to a destination registered in the address book, sending could not be performed because the destination was deleted from the address book while the machine was waiting to send.
Specify another destination, and try sending again.
Sending from the fax driver is not allowed.
Set <Allow Fax Driver TX> to <On>, and try sending again.
#025
When sending a fax from a remote fax client machine, a line that does not exist in the remote fax server machine was specified.
Check the number of lines in the server machine, and try sending again after matching the remote fax transmission settings of the client machine with the number of lines on the server machine.
#033
The device of the other party does not support confidential communication or subaddresses.
Send without using confidential communication or subaddresses.
#034
The confidential storage location in the device of the other party specified for confidential communication was not found.
Check the confidential storage location in the device of the other party, and try sending again.
The memory was insufficient in the device of the other party.
Ask the other party to free up some space.
#035
The device of the other party does not support the forwarding function or subaddresses.
Directly send to the other party.
#037
Could not receive because the machine had insufficient free memory.
Delete unnecessary documents and error documents to free up space.
Data containing more than 1,000 pages was received.
The machine deletes any pages after the 999th page, and prints or stores the remaining 999 pages. Tell the other party to send the 1,000th and subsequent pages again.
When performing delayed sending or redial sending, the image data of the document to send was not found in memory.
Scan the original again, and try sending again.
Select direct sending when sending again.
Could not send to multiple destinations because the machine had insufficient free memory.
Delete unnecessary documents and error documents to free up space.
Divide the document into two or more parts, and then try sending the document again.
Lower the resolution and try sending again.
#040
When sending a fax from a remote fax client machine, sending could not be performed because the memory of the remote fax server machine was insufficient.
Delete unnecessary documents and error documents from the remote fax server machine to free up space.
Divide the document into two or more parts, and then try sending the document again.
Lower the resolution and try sending again.
#054
The sending process was canceled because the unit telephone number and unit name were not registered.
Try sending again after registering the unit telephone number and unit name.
#080
A subaddress is not set in the device of the other party.
Check the subaddress of the other party, and try sending again.
#081
A password is not set in the device of the other party.
Check the password of the other party, and try sending again.
#082
Polling transmission is not configured in the device of the other party.
Tell the other party to configure polling transmission, and perform polling reception again.
#083
The subaddress and password of the machine and the device of the other party did not match when performing polling reception.
Check that the subaddress and password of the machine and the device of the other party match, and try sending again.
#084
Cannot perform polling reception because the password is not supported by the device of the other party.
Perform polling reception without using a password.
#099
The operation was canceled before it was complete.
Perform the operation again.
An error occurred because the power of the machine was turned OFF while it was operating.
Check whether the power is turned ON, and perform the operation again, if necessary.
#102
The subaddress and password do not match.
Check the subaddress and password of the other party, and try sending again.
#701
The Department ID does not exist, or the PIN was changed.
If you are using User Authentication, assign Department IDs to users. If you are using DepartmentID Authentication, enter the new Department ID and PIN to log in again.
The reception setting in <Allow Printer Jobs with Unknown IDs> is set to <Off>.
Set <Allow Printer Jobs with Unknown IDs> and <Allow Remote Scan Jobs with Unknown IDs> in <Department ID Management> to <On>.
Sending could not be performed because the remote fax client machine failed authentication to the remote fax server machine.
If Department ID Management is set in the remote fax server machine, log in to the remote fax client machine using the Department ID and PIN set in the remote fax server machine.
#702
Sending could not be performed because the memory was full.
Wait a while. Try sending again after the other sending is complete.
Send to several groups of destinations separately, rather than all at once.
#703
Could not write because the image area of the memory is full.
Try sending again after the other sending is complete.
Delete unnecessary files in the Mail Box and Fax/I-Fax Inbox. If there is still a problem, restart the machine.
#704
An unknown error occurred when retrieving destination information from the address book.
Check the destination settings. If there is still a problem, restart the machine.
#705
Sending was canceled because the image data size exceeded the maximum value set in Settings/Registration.
Adjust the maximum data size for sending. Select a lower resolution or reduce the number of images sent at once when using the I-fax function to ensure that the maximum data size for sending is not exceeded. Divide the data, depending on the conditions of the other party.
#706
An address book was being imported/exported from the Remote UI or another sending component was in use.
Try sending again after the other operation is complete.
#711
The memory is full. You may be able to send if you delete unnecessary files in mail boxes.
Try sending again after deleting unnecessary files in mail boxes.
#712
The memory is full. Try executing again after deleting unnecessary files in mail boxes.
Try sending again after deleting unnecessary files in mail boxes.
#713
The document in Mail Box or Fax/I-Fax Inbox was deleted before sending the URL.
Try sending again after saving the required document in the Mail Box or Fax/I-Fax Inbox.
#715
The certificate to use was not found when sending an e-mail with a digital signature attached.
When using a device signature, set the e-mail address of the machine (Setting E-mail/I-Fax Communication), and then generate a certificate for device signatures (Generating a Device Signature Certificate). If a certificate for device signatures has already been generated, generate it again. When using a user signature, register the certificate for user signatures again (Registering a User Signature Certificate).
Check whether an expired certificate or revoked certificate is being used. In addition, check whether the certificate chain is invalid.
#716
The destination public key certificate could not be found.
Register the destination public key certificate in the machine.
Check whether an expired certificate or revoked certificate is being used. In addition, check whether the certificate chain is invalid.
#751
The server is not running or the network is disconnected (either you could not connect to the destination, or the connection was lost before the job could be completed).
Check whether the server is operating normally.
Check the status of the network.
If the destination is using IIS 6.0 with Windows Server 2003 and digest authentication is used as the authentication method of the WebDAV server, set <Use Divided Chunk Send for WebDAV TX> to <On> to send with WebDAV via a proxy using TLS communication.
The IP address is not set.
Check <TCP/IP Settings> in <Preferences>.
<Network> 
<TCP/IP Settings>
<TCP/IP Settings>Could not send to an SMB server (including the Advanced Box of another imageRUNNER ADVANCE series machine disclosed with SMB) because a file server is being browsed using Windows (SMB).
If an error occurs with delayed sending, close the <Browse> screen, and scan and send the document again.
If an error occurs when forwarding a received fax/I-fax file to an SMB server, scan a printed copy of the received file, and send it to the forwarding destination.
You can avoid errors by using FTP or WebDAV as the protocol for sending to the server.
#752
The server is not running or the network is disconnected.
Check whether the SMTP server is operating normally.
Check the status of the network.
The SMTP server name setting for e-mail/I-fax is incorrect or the e-mail address or domain name is not set.
Check the SMTP server name, e-mail address, and domain name settings in <Communication Settings>.
#753
A TCP/IP error (Socket or Select error, etc.) occurred when sending e-mail or when sending a fax from a remote fax client machine.
Check the status of the network cable and connector. If there is still a problem, restart the machine.
#755
Could not send a fax from a remote fax client machine because TCP/IP is not operating correctly.
Check <TCP/IP Settings> in <Preferences>.
The IP address is not set.
Check <TCP/IP Settings> in <Preferences>.
When preparing to start using the machine, an IP address was not assigned using DHCP or Auto IP.
Check <TCP/IP Settings> in <Preferences>.
#759
An error occurred when sending the URL of the Mail Box in which a file was saved.
Contact your administrator.
#761
When sending a PDF/XPS file with a digital signature, the file could not be sent because the certificate or key pair set in the machine was corrupt or could not be accessed.
When sending a PDF/XPS file with a user signature, check whether the user certificate is corrupt. If the user certificate is corrupt, install it again.
When sending a PDF/XPS file with a device signature, check whether the device certificate is corrupt. If the device certificate is corrupt, generate it again.
#762
Could not send to a domain not registered as an allowed domain because <Restrict TX Destination Domain> is set to <On>.
Set <Restrict TX Destination Domain> to <Off> or register the domain as an allowed domain, and try sending again.
#763
When sending a PDF file with a time stamp, an error occurred because the license file was corrupt or the password of the license file was incorrect.
Check whether the license file is corrupt. If the license file is corrupt, set it again.
Set a password for the license file again.
#766
The certificate to use when sending a PDF/XPS file with a digital signature has expired.
Update the certificate or use a certificate that has not expired.
If the certificate has not expired, set the time of the machine correctly.
#767
Could not connect to the time stamp server because the server address in <Time Stamp Settings> was incorrect.
Check the server address set in <Time Stamp Settings>.
Could not connect to the time stamp server because the DNS settings and proxy settings were incorrect.
Check <Proxy Settings> and <DNS Settings> in <TCP/IP Settings>.
Could not connect to the time stamp server because there is a problem with the network line.
Check the status of the DNS server, proxy server, and network.
#769
The number of trials allowed for the send function reached the upper limit.
If you want to continue using this function, purchase the official optional product.
#770
When sending with WebDAV, sending could not be performed because TLS communication was not supported on the WebDAV server side or proxy server side.
Check the WebDAV server settings.
Check the proxy server if you are sending via a proxy.
Sending could not be performed because a validation error occurred when validating the TLS server certificate when sending with WebDAV because <Confirm TLS Certificate for WebDAV TX> is set to <On>.
Check whether the CA certificate used to sign the TLS server certificate on the WebDAV server side is registered in the machine.
Check whether the TLS server certificate on the WebDAV server side is correct.
Check whether the TLS server certificate is a self-signed certificate.
The operation could not be completed because a validation error occurred when validating the TLS server certificate when accessing another server because <Confirm TLS Certificate for Network Access> is set to <On>.
Check whether the CA certificate used to sign the TLS server certificate of the Advanced Box of the other imageRUNNER ADVANCE series machine disclosed as a WebDAV server is registered in the machine.
Check whether the TLS server certificate of the Advanced Box of the other imageRUNNER ADVANCE series machine disclosed as a WebDAV server is correct.
Check whether the TLS server certificate is a self-signed certificate.
#771
The remote fax server address setting is incorrect.
Check <Remote Fax TX Settings>.
The remote fax server is not running.
Check whether the remote fax server is operating normally.
The network is disconnected.
Check the status of the network.
Could not connect to the remote fax server because the DNS server could not be connected to.
Check the DNS server name setting.
Check whether the DNS server is operating normally.
#772
The URL of the Rights Management server is incorrect.
Check <Rights Management Server Settings>.
The Rights Management server cannot be started.
Check whether the Rights Management server is operating normally.
The network is disconnected.
Check the status of the network.
#773
A PDF function that cannot be set is selected when <Optimize PDF for Web> is set to <On>.
Set one of the following: Device Signature, User Signature, or Reader Extensions.
Set <Optimize PDF for Web> to <Off>.
An unsupported PDF function is selected in the forwarding settings when <Format PDF to PDF/A> is set to <On>.
Cancel the encryption setting or visible signature setting.
Set <Format PDF to PDF/A> to <Off>.
#801
A timeout error occurred due to a problem on the mail server side when communicating with the SMTP server to send an e-mail or send or receive an I-fax.
Check whether the SMTP server is operating normally.
Check the status of the network.
An error was returned from the SMTP server when connecting with SMTP. The address setting is incorrect. An error occurred due to a problem on the server side when sending to a file server.
Check whether SMTP is operating normally, the status of the network, the destination settings, and the status and settings of the file server.
You sent to a destination that does not have write privileges.
Check the destination settings.
A file with the same name existed when sending to a file server that does not allow files to be overwritten.
Change the settings of the file server to enable files to be overwritten. Alternatively, contact the server administrator.
Change the filename.
The folder name or password specified when sending to a file server was incorrect.
Check the folder name or password.
#802
The SMTP server name setting specified in the communication settings is incorrect. The DNS server name setting is incorrect. Could not connect to the DNS server.
Check the SMTP server name/DNS server name setting and the status of the network. Check whether the DNS server is operating normally.
#804
When sending to a file server, no folders matched the specified path.
Check the destination.
You do not have access privileges for the folder or file. Alternatively, the folder or file may have been deleted by another operation.
Allow access to the folder on the server side. Alternatively, contact the server administrator.
#805
Could not send to the SMB server because there was insufficient free space on the server side.
Delete unnecessary documents and error documents from the server to free up space. Alternatively, contact the server administrator.
#806
The user name or password specified when sending to a file server was incorrect.
Check the user name or password.
The destination specified when sending an e-mail/I-fax was incorrect.
Check the e-mail/I-fax destination.
#807
You do not have access privileges for the specified directory.
Set access privileges for the server directory or send to a directory that you have access privileges for. Alternatively, contact your administrator.
#809
When sending to an SMB server, a file with the same name already exists and overwriting of files is not allowed.
Change the filename and try sending again.
Change the settings of the SMB server to enable files to be overwritten. Alternatively, contact the server administrator.
#810
A POP server connection error occurred when an I-fax was received.
Check the POP server settings in <Communication Settings>.
Check whether the POP server is operating correctly. Check the status of the network.
An error was returned from the POP server when connecting to the POP server. Alternatively, a timeout error occurred on the server side.
Check the POP server settings in <Communication Settings>.
Check whether the POP server is operating correctly. Check the status of the network.
#813
A POP server authentication error (user account error or password error) occurred when an I-fax was received.
Check the POP server settings in <Communication Settings>.
#818
The received data was in a file format that cannot be printed.
Tell the other party to change the file format and send again.
#819
Data that cannot be handled was received. The MIME information is invalid.
Tell the other party to check the settings and send again.
#820
Data that cannot be handled was received. The BASE64 or uuencode is invalid.
Tell the other party to check the settings and send again.
#821
Data that cannot be handled was received. A TIFF analysis error occurred.
Tell the other party to check the settings and send again.
#822
Data that cannot be handled was received. The image cannot be decoded.
Tell the other party to check the settings and send again.
#827
Data that cannot be handled was received. Unsupported MIME information was included.
Tell the other party to check the settings and send again.
#828
HTML data was received.
Tell the other party to change to a format other than HTML and send again.
#829
Data containing more than 1,000 pages was received.
The machine deletes any pages after the 999th page, and prints or stores the remaining 999 pages. Tell the other party to send the 1,000th and subsequent pages again.
#830
A DSN error notification was received because the I-fax address or destination conditions were incorrect.
Check the specified I-fax address and the destination conditions.
A DSN error notification was received because the size of the file that was sent exceeded the size allowed by the mail server.
Change the setting in <Maximum Data Size for Sending> so that the size of the file to send does not exceed the size allowed by the mail server.
Check the status of the mail server, DNS server, and network.
#832
Could not send DSN mail because e-mail settings and network settings were not specified in <Communication Settings>.
Check <Communication Settings>, <DNS Settings>, and <IP Address Settings>.
DSN mail could not be sent due to a problem with the mail server or DNS server.
Check the status of the mail server and DNS server.
#833
MDN (Message Disposition Notification) mail could not be sent because the TCP/IP settings were not specified.
Check <Communication Settings>, <DNS Settings>, and <IP Address Settings>.
MDN (Message Disposition Notification) mail could not be sent due to a problem with the mail server or DNS server.
Check the status of the mail server and DNS server.
#834
An MDN error notification was received because the I-fax address or destination conditions were incorrect.
Check the specified I-fax address and the destination conditions.
An MDN error notification was received because a problem occurred in the mail server or network.
Check the status of the mail server and network.
An MDN error notification was received because a problem such as a full memory occurred at the other party.
Check the conditions and status of the other party.
#835
The maximum number of text lines that can be received with I-fax was exceeded.
Tell the other party to reduce the number of text lines in the message body and send again.
#838
The license required to use the send function has expired.
Purchase a license for the send function.
#839
The user name or password set in <Communication Settings> is incorrect.
Check the user name and password settings for SMTP authentication (SMTP AUTH) in <Communication Settings>.
#841
An encryption algorithm shared with the mail server does not exist for e-mail and I-fax transmission.
Set <Allow TLS (POP)> or <Allow TLS (SMTP TX)> in <Communication Settings> to <Off>.
Add a common encryption algorithm to the mail server settings.
#842
The mail server requested authentication using a client certificate for e-mail and I-fax transmission.
Set <Allow TLS (POP)> or <Allow TLS (SMTP TX)> in <Communication Settings> to <Off>.
Change mail server settings so that a client certificate is not requested.
Sending could not be performed because a validation error occurred when validating the TLS server certificate when sending with SMTP because <Confirm TLS Certificate for SMTP TX> is set to <On>.
Use the Remote UI to check whether the CA certificate used to sign the TLS server certificate on the SMTP server side is registered in the machine.
Check whether the TLS server certificate on the SMTP server side is correct.
Check whether the TLS server certificate is a self-signed certificate.
#843
There is a great difference between the time of the KDC (Key Distribution Center) server and the time set in the machine.
Correct the time of the machine or the KDC (Key Distribution Center) server.
#844
Failed to perform TLS encrypted communication with the POP server when sending with POP before SMTP.
Check the TLS encrypted communication settings of the POP server.
Set <Allow TLS (POP)> to <Off> in <Communication Settings>. If the problem is not resolved, set <POP Authentication Before Sending> to <Off> in <Communication Settings>, and switch to a setting other than POP before SMTP.
Sending could not be performed because a validation error occurred when validating the TLS server certificate when communicating with the POP server because <Confirm TLS Certificate for POP RX> is set to <On>.
Use the Remote UI to check whether the CA certificate used to sign the TLS server certificate on the POP server side is registered in the machine.
Check whether the TLS server certificate on the POP server side is correct.
Check whether the TLS server certificate is a self-signed certificate.
#845
Failed to perform POP authentication (POP AUTH) when sending with POP before SMTP.
Check the settings in <POP Server>, <POP Login Name>, and <POP Password> in <Communication Settings>.
Check the POP authentication settings of the POP server.
Select <Standard> or <APOP> in <POP Auth. Method> in <Communication Settings>. If the problem is not resolved, set <POP Authentication Before Sending> to <Off> in <Communication Settings>, and switch the communication settings to something other than POP before SMTP.
#846
Failed to perform POP authentication (APOP) when sending with POP before SMTP.
Check the settings in <POP Server>, <POP Login Name>, and <POP Password> in <Communication Settings>.
Check the APOP settings of the POP server.
Select <Standard> or <POP AUTH> in <POP Auth. Method> in <Communication Settings>. If the problem is not resolved, set <POP Authentication Before Sending> to <Off> in <Communication Settings>, and switch the communication settings to something other than POP before SMTP.
#847
Could not save the received file in a Confidential Fax Inbox because the memory of the Mail Box or Fax/I-Fax Inbox was full.
Delete unnecessary files in the Confidential Fax Inbox or Memory RX Inbox.
#848
An error occurred when combining an e-mail that was divided and sent.
The divided data may have been deleted. If you delete divided data, it cannot be combined to form a completed document, even if the remaining data is received later. Ask the sender to send the data again.
#856
The executed operation was canceled because the hard disk area for temporarily saving data became full.
Contact your administrator.
#868
When sending with WebDAV, communication with the destination failed, and access via a proxy was requested (received HTTP Error 305: Use Proxy).
Check the WebDAV server settings.
Check the proxy settings.
#869
When sending with WebDAV, a response indicating that authentication failed was received from the destination (received HTTP Error 401: Unauthorized).
Check the user name or password.
Check the WebDAV server security settings.
#870
When sending with WebDAV, a response indicating that the request was rejected was received from the destination (received HTTP Error 403: Forbidden).
Try sending again after waiting a while.
Check the destination settings.
Check the WebDAV server settings.
#871
When sending with WebDAV, a response indicating that the specified folder was not found was received from the destination (HTTP Error 404: Not Found/409: Conflict/410: Gone).
Check the destination settings.
#872
When sending with WebDAV, a response indicating that access is not allowed was received from the destination (received HTTP Error 405: Method Not Allowed).
Check the WebDAV server settings.
#873
When sending with WebDAV, a response indicating that proxy authentication failed was received from the destination (received HTTP Error 407: Proxy Authentication Required).
Check the proxy settings.
#874
When sending with WebDAV, a response indicating that a timeout occurred was received from the destination (received HTTP Error 408: Request Timeout).
Try sending again after waiting a while.
Check the WebDAV server settings.
#875
When sending with WebDAV, a response indicating that chunk transmission was refused was received from the destination (received HTTP Error 411: Length Required).
Set <Use Divided Chunk Send for WebDAV TX> to <Off>.
Check the WebDAV server settings.
#876
When sending with WebDAV, a response indicating that the size of the data was too large was received from the destination (received HTTP Error 413: Request Entity Too Large).
Check the WebDAV server settings.
#877
When sending with WebDAV, a response indicating that the URI (host name and path to folder) was too long was received from the destination (received HTTP Error 414: Request-URI Too Long).
Check the WebDAV server settings.
#878
When sending with WebDAV, a response indicating that an unexpected situation preventing the request from being executed occurred on the server side was received from the destination (received HTTP Error 500: Internal Server Error).
Check the WebDAV server settings.
#879
When sending with WebDAV, a response indicating that the server does not support the necessary functions to execute the request was received from the destination (received HTTP Error 501: Not Implemented).
Check the WebDAV server settings.
When sending via a proxy with non-TLS communication, set <Use Divided Chunk Send for WebDAV TX> to <Off>.
#880
When sending with WebDAV, a response indicating that communication with an upstream server failed was received from the proxy server (received HTTP Error 502: Bad Gateway).
Check the WebDAV server settings.
Check the proxy server settings.
#881
When sending with WebDAV, a response indicating that requests currently cannot be handled was received from the destination (received HTTP Error 503: Service Unavailable).
Check the WebDAV server settings.
#882
When sending with WebDAV, a response indicating that communication with an upstream server failed was received from the proxy server (received HTTP Error 504: Gateway Timeout).
Check the WebDAV server settings.
Check the proxy server settings.
#883
When sending with WebDAV, a response indicating that the server does not support the necessary functions to execute the request was received from the destination (received HTTP Error 505: HTTP Version Not Supported).
Check the WebDAV server settings.
#884
When sending with WebDAV, a response indicating that disk space required for the request could not be secured on the server side was received from the destination (received HTTP Error 507: Insufficient Storage).
Check the WebDAV server settings.
#885
When sending with WebDAV, an unexpected error response was received from the server.
Check the WebDAV server settings.
Check the proxy server settings.
#886
When sending with WebDAV, a response indicating that the request was invalid was received from the destination (received HTTP Error 400: Bad Request).
When sending via a proxy with non-TLS communication, set <Use Divided Chunk Send for WebDAV TX> to <Off>.
#889
The original could not be scanned or printed because it was embedded with job restriction information.
Check the job restriction information or contact your administrator.
#899
E-mail or I-fax transmission completed normally. However, the transmission may not have been received by the other party because it is relayed by multiple servers.
When performing POP reception, press 
<Check I-Fax RX>, and check whether the machine has received an error mail.
<Check I-Fax RX>, and check whether the machine has received an error mail.When performing POP reception, received error mails are automatically printed when <POP Interval> is set to a value other than 0 minutes or the machine is set to receive error mails via SMTP.
Ask whether the other party received the transmission, as necessary.
#918
Could not recognize the QR code in the original.
Check whether the QR code is in the correct position and scan the original again.
#919
A syntax error or a PostScript error that exceeds device restrictions, etc. was detected.
Set <Print PS Errors> (Settings/Registration) to <On>, submit the job again, confirm the contents of the PostScript error, then execute the job after resolving the error.
#922
The maximum number of sheets that can be saddle-stitched has been exceeded. Saddle-stitching may be able to be performed by reducing the number of sheets.
Check the maximum number of sheets that can be saddle-stitched, and execute again.
#925
A transmission error occurred from the fax driver.
An image size that cannot be sent was specified. Check the size of the image.
#927
A transmission error occurred from the fax driver.
Font that cannot be processed is included in the data received by the machine from a computer. Check the received data.
#928
A transmission error occurred from the fax driver.
The memory is full, or the data size has exceeded the size that can be processed at one time. Delete unnecessary data or check the data size.
#929
A transmission error occurred from the fax driver.
A network error occurred when the machine was receiving data from a computer. Check the network connections and settings.
#931
The job was canceled because saddle folding could not be performed.
Check the setting combinations as well as the type of paper you are using and the number of sheets.
#932
The maximum number of sheets that can be stapled with the Eco (Staple-Free) mode has been exceeded. Stapling with the Eco (Staple-Free) mode may be able to be performed by reducing the number of sheets.
Check the maximum number of sheets that can be stapled with the Eco (Staple-Free) mode, and execute again.
#933
The maximum number of sheets that can be stapled has been exceeded. Stapling may be able to be performed by reducing the number of sheets.
Check the maximum number of sheets that can be stapled, and execute again.
#934
An error occurred for a print job, and the job was deleted because the specified time period elapsed.
Resolve the error and execute the job again.
You can also change the time period before deletion or disable automatic deletion from <Auto Delete Suspended Jobs> (Settings/Registration).
#935
The job was canceled and one copy was output without being bound because the maximum number of sheets of paper that can be bound with the Eco (Staple-Free) mode was exceeded.
Check the maximum number of sheets of paper that can be bound with the Eco (Staple-Free) mode, and execute the job again.
You can specify the procedure to perform when there are too many sheets to staple at once.
#936
The job was canceled and one copy was output without being stapled because the maximum number of sheets of paper that can be stapled together was exceeded.
Check the maximum number of sheets of paper that can be stapled together, and execute the job again.
You can specify the procedure to perform when there are too many sheets to staple at once.
#937
The document was output without being saddle stitched because the maximum number of sheets of paper that can be saddle stitched was exceeded.
Saddle stitching may be possible if you reduce the number of sheets of paper.
You can specify the procedure to perform when there are too many sheets to staple at once.
#995
Reserved communication jobs were cleared.
Perform the operation again, as necessary.