Ricoh MP 401 spf User Manual page 195

Message
"The selected paper size is
not supported. This job has
been cancelled."
"Sending data failed."
"The print job has been
cancelled because capture
file(s) could not be stored:
Exceeded max. memory."
"The print job has been
cancelled because capture
file(s) could not be stored:
Exceeded max. number of
files."
"The print job has been
cancelled because capture
file(s) could not be stored:
Exceeded max. No. of
pages per file."
"The selected paper type is
not supported. This job has
been cancelled."
"You do not have a privilege
to use this function. This job
has been cancelled."
"You do not have a privilege
to use this function. This job
has been cancelled."
"You do not have a privilege
to use this function. This
operation has been
cancelled."
Causes
Job Reset is automatically
performed if the specified
paper size is incorrect.
The machine received a
command to stop
transmission from the printer
driver.
The hard disk became full
after a file was stored.
The maximum file capacity
of the Document Server was
exceeded.
The maximum page
capacity of the Document
Server was exceeded.
Job Reset is automatically
performed if the specified
paper type is incorrect.
The entered Login User
Name or Login Password is
not correct.
The logged in user is not
allowed to use the selected
function.
The logged in user does not
have the privileges to
register programs or change
the paper tray settings.
When Messages Are Displayed on the Control Panel
Solutions
Specify the correct paper size, and
then print the file again.
Check if the computer is working
correctly.
Delete the files stored in the Document
Server or reduce the file size to be sent.
Delete the files stored in the Document
Server.
Delete some of the files stored in the
Document Server or reduce the number
of pages that you want to send.
Specify the correct paper type, and
then print the file again.
Check that the Login User Name and
Login Password are correct.
For details about how to set
permissions, see Security Guide
For details about how to set
permissions, see Security Guide
.
.
193