A B Неисправность Причина Примечание

Fujiko-ODA The true disposal method is indicated as a machine. — Especially a different portion from the disposal method of a former machine is. system fail/sub system fail (I have a person in charge indicate Fail which requires hard / mechanism part exchange) Fujiko-ODA True detection conditions are indicated as a machine. — Especially the portion the detection conditions of a former machine are indicated to be as they are is. It is cautious of system fail/sub system fail

001 300 Top Cover Open
Top or Top+Rear Cover Open is detected

001 301 Rear Cover Open
Only Rear Cover Open is detected

001 302 OCT Cover Open
OCT Cover Open is detected

001 306 Imari: Left Hand Dup Cover
GINGA: Duplex Cover Open
Topo: Duplex Cover Open If not repaired in Duplex Cover Close, a sensor check is carried out, and it is Duplex Cover exchange after that Duplex Cover Open is detected

001 398 Top Cover Open If not repaired in power supply OFF/ON, it is LV Fan exchange When LV FAN does not turn at regular number of rotations

003 205 (Copy/Scan/Print improper Fail)
BILLING FAIL (By PWB exchange)
Imari: Three billing counter disagreement Power OFF/ON, and the following is performed when a trouble continues
Diag (DC132) disposal is performed and a Billing value is arranged
When after disposal occurs, ESS PWB (PL13.1) is exchanged When all the billing counters currently held to two or more places differ

“SubSystemFail” – ChainLink corrected the classification of Fault in unknown Imari

003 206 “Copy/Scan/Print improper Fail”
BILLING FAIL
Imari: Billing counter automatic restoration cannot be carried out, but it is at the one billing restoration time Power OFF/ON, and the following is performed when a trouble continues.
SEEPROM of ESS PWB, or the abnormalities of NVM.
Or the abnormalities in EEPROM of MCU PWB.
When a NVM battery is not faulty, ESS PWB (PL13.1) or MCU PWB (PL13.1) is exchanged When uncorrectable at the time of the correction at the time of one billing counter disagreement

“SubSystemFail” – ChainLink corrected the classification of Fault in unknown Imari

003 346 Imari: (IOT) The Scope-FD transmitting error which Controller detects (parity error) Power OFF/ON, and the following is performed when a trouble continues
(1) Check connection of MCU PWB connection harness
(2) Poor soft adjustment Re-installation of software is carried out
(3) When also generating the above-mentioned correspondence, exchange MCU PWB (PL13.1) Since ACK was unreceivable by two resendings, it is communication generating (the parity error was detected by HARDWARE by the side of IOT)

* It changed from — 340 ChainLinkj of SubSystemFail of Imari must be [ 340 ] from 350

003 347 Imari: (IOT) The Scope-FD transmitting error which Controller detects Since ACK was unreceivable by two resendings, it is communication generating (HARDWARE by the side of IOT, the error was detected)

* It changed from — 340 ChainLinkj of SubSystemFail of Imari must be [ 340 ] from 350

003 348 Topo: (IOT) Transmitting error which Controller detects. It is inaccurate command detection at the time of transmission

003 349 Topo: (IOT) Transmitting error which Controller detects. Transmitting undershirt run

003 350 Topo: (IOT) The other various transmitting error which Controller detects

003 354 Imari: (IOT) The Scope-FD reception error which Controller detects (parity error)
Hana: It Parity-error-generates during status reception from IOT Power OFF/ON, and the following is performed when a trouble continues
(1) Check connection of MCU PWB connection harness
(2) Poor soft adjustment Re-installation of software is carried out
(3) When also generating the above-mentioned correspondence, exchange MCU PWB (PL13.1) It generates, when NAK which notifies communication generating is received (the parity error was detected by HARDWARE which the UART itself has)

* It changed from — 340 ChainLinkj of SubSystemFail of Imari must be [ 340 ] from 350

003 356 Imari: (IOT) The Scope-FD reception error which Controller detects (overrun error)
Hana: It Overrun-error-generates during status reception from IOT It generates, when NAK which notifies communication generating is received (the overrun error was detected by HARDWARE which the UART itself has)

* It changed from — 340 ChainLinkj of SubSystemFail of Imari must be [ 340 ] from 350

003 360 IOT-ESS initialization error Initialization Fail of IOT Driver

This ChainLink is set when “communication establishment with IOT is not completed” in initialization (iotifInit) of an IOT driver

003 362 It PAGE-SYNC-generates before the completion of (image output) video output preparation Power OFF/ON, and the following is performed when a trouble continues
1. Exchange the harness which connects ESS and IOT
2. Exchange of ESS PWB PageSync is active before writing in at the time of an IOT output until it becomes FIFO full about output data

003 363 It is a PAGE-SYNC end error during a (image output) video output PageSync was generated before outputting the size specified at the time of an IOT output

003 364 (Image output) DMA transfer error Power OFF/ON, and the following is performed when a trouble continues
1. When exchange (PL13.1)
2. DC355 Diag diagnosis of RAM is performed and a trouble continues, it is exchange (PL13.1) of HDD
3. ESS PWB (PL13.1) Although the data specified at the time of compression/extension was inputted, it generates, when compression/extension is not completed

ID=153 and duplication — It also leaves this, although “Video DMA Fail” (3-364) is overlapped

003 367 An error of others from Decompress (extension) Power OFF/ON, and the following is performed when a trouble continues
1. Exchange the harness which connects ESS and IOT
2. When Not Restoring by IOT-PWB Exchange, it is Exchange of Following 2.ESS PWB - Unjust detection of LINE SYNC (Ginga)
1) V-SYNC inaccurate during an IOT output and the H-SYNC signal were generated
2) Overrun of data generates generating (it generates in the parameter setting mistake to Panther4) 2 only during debugging. 1) The error factor of the main

003 368 GINGA: (Image output) PCI Bus Error Power OFF/ON, and the following is performed when a trouble continues
1. Exchange of ESS PWB - In the fault of a PCI bus, abnormalities occurred in access of PCI

003 370 Marker code detection error Power OFF/ON, and the following is performed when a trouble continues
When only a specific document is generated
- A possibility of being the fault of S/W is high
1. It may be outputted by changing printing mode (standard/high-definition/– highly minute)
2. It may be outputted by changing RAM size
A. Change the RAM size to install
B. Change the operating size of RAM. (Setting change of a port, receiving buffer size, etc. are changed.) When generating by almost all documents in O unspecified.
- A possibility of being the fault of HW is quantity When it elongated by the size specified at the time of extension, an end code (FF02) was not found in compression data

003 371 GINGA; Establishment of the communication between ESS and IOT which Controller detects was not completed Power OFF/ON, and the following is performed when a trouble continues
1. Exchange the harness which connects ESS and IOT
2. Exchange of Exchange 3.MCU PWB of ESS PWB - The ACK packet from the IOT side was unreceivable to within a time to the synchronous packet which transmitted from the Controller side

003 372 The DLL transmitting error which GINGA:Controller detects (inaccurate parameter directions) Power OFF/ON, and the following is performed when a trouble continues
1. Exchange of ESS PWB - Detect unjust directions of unjust directions of unjust directions of unjust directions of an IOT port number, and timeout time, and a pointer, and transmission size

003 600 Imari: Billing Master Counter restoration Only registration to History When automatic restoration of Cont NV-E is performed. (Counter necessity)

003 601 Imari: Billing Master Counter 1 restoration When automatic restoration of Cont NV-S is performed. (Counter necessity)

003 602 Imari: Billing Master Counter 2 restoration When automatic restoration of IOTdc NV-E is performed. (Counter necessity)

003 747 The print parameter directed [ in which were directed and the error was print-parameter-made ] is unusual A print parameter is changed and re-printed The directed print parameter is unusual

UI Cont receives this notice of error from PFlite at the time of initialization and execution, and notifies to UI at it.
It is not Sub System Fail. In Imari, it treats as “Job Fail”
(Print log) print parameter trouble occurred.
Directions specified by the job at the time of print execution of a confidential print (paper tray)

003 946 Tray 1 Out Of Place If it is the same as that of user disposal and is NG, they are a tray detection sensor or tray exchange Unentered

Feeder Status
* Offer HID 980420 information by Centre Ware

003 947 Tray 2 Out Of Place

003 948 Tray 3 Out Of Place

003 949 Tray 4 Out Of Place

003 950 Tray 1 Empty When a trouble continues by supply of a paper, Sensor is checked with reference to general-purpose Sensor FIP Unentered

Feeder Status
* Offer HID 980420 information by Centre Ware

003 951 Tray 2 Empty

003 952 Tray 3 Empty

003 953 Tray 4 Empty

003 954 Tray SMH Empty When a trouble continues by supply of a paper, Sensor is checked with reference to general-purpose Sensor FIP It ..(ed) and those of a tray without a paper were detected

Feeder Status
* Are there HID 980420 *HID 980508 which it will be at what time

003 955 Since the inner shot has fallen out, paper cannot be fed The same as that of user disposal Unentered

003 958 Size mismatch Imari: SMH size — incongruent The right paper is set It ..(ed) and the paper which carried out print directions differed from the paper in a tray

Job
* HID 980515
It stops at normal output 1

003 959 size mismatch Tray 1 size — incongruent which sets the right paper.
When a trouble continues, Sensor is checked with reference to general-purpose Sensor FIP The paper which carried out print directions differed from the paper in a tray 1

003 960 size mismatch Tray 2 size — incongruent The paper which carried out print directions differed from the paper in a tray 2

003 961 size mismatch Tray 3 size — incongruent The paper which carried out print directions differed from the paper in a tray 3

003 962 size mismatch Tray 4 size — incongruent The paper which carried out print directions differed from the paper in a tray 4

003 965 ATS/APS No Paper
APS/ATS NG (No Paper) The paper directed on a print has no paper

003 966 ATS/APS No Destination Error
ATS/APS NG (except No Paper) A setup is changed. When a trouble continues, Sensor is checked with reference to general-purpose Sensor FIP The paper directed on a print is undetectable

003 985 The stop check of SMH Paper size / the direction of a paper / paper kind is checked, and a discharge key is pushed It ..(ed) with a certain obstacle and the run from a tray was interrupted

004 362 NVM R/W Fail(U6-4) If not repaired in power supply OFF/ON, it is NVM tip exchange At the time of Write Check NG generating at the time of NVM (EEPROM) writing
Or the right value is not acquired in NVM R/W

004 363 comm: Drum K Motor Drive Fail(U1-4) The Imari service manual, the Chapter 2 troubleshooting, 004 to 363 reference
Fuhjin

004 922 No Toner K The same as that of user disposal CRU life operation was set as the stop by the panel, and after IOT detected Toner Warning, data transmission was performed by 100 sheets

XXXXX displays a color. When two or more color exchange is required, it is displayed as “toner cart …”
* HID980619

006 355 Poor ROS MOT rotation
ROS Motor Abnormality was detected

Since LouiseSE and the resource value were doubled, it adds newly

007 311 MSI Down Broken
MSI Unit was separated after the power supply injection
MSI Unit Fail was detected
Local Fail

007 313 Tray Module communication FailGINGA/Topo: Tray3/Tray4 module was separated.
Topo: Only the option tray 4 is applied The abnormalities in communication with an option tray (trays 2-4, TTM 3 and 4) occurred. Connection is checked. When there are no abnormalities in connection, it is tray exchange Power Off – On.
Topo: Only the option tray 4 is applied When it judges that the reply from communication with RemoteCPU is an error
Ginga: When the abnormalities in communication with an option tray (1TM/3TM) are detected
Topo: Only the option tray 4 is applied

007 950 GINGA: Tray1 size mismatch (subscanning length error) The same as that of user disposal As a result of measuring and acting as paper length by the Reg sensor, it detects differing from the paper length set up (specification)

007 951 GINGA: Tray2 size mismatch (subscanning length error)

007 952 GINGA: Tray2 size mismatch (subscanning length error)

007 953 GINGA: Tray3 size mismatch (subscanning length error)

007 954 SMH size mismatch (scanning [ sub] length error) Imari-MF: Subscanning length / main scanning width error As a result of measuring and acting as paper length by the Reg sensor, it detects differing from the paper length set up (specification)

Imari: It adds by IOT related subcommittee #23.
The error which IOT dc notifies to IOT sc.
Subscanning length is inspected after a Feed start, when short, it is begun to put on a paper (it points out printing and discharging to the middle), and when long, it becomes jam (Regi Sensor On Jam).

007 969 From the tray of the quality of paper which Topo:APS-quality-of-paper-Mismatch(es) and is different to printing (it indicates by the message and becomes a Confirm screen)
By the message which tells “whether it prints in the paper of which tray”, since the misapprehension “it will be correctly printed if a paper to print on Tray N is set” is caused, are cautious of the contents of a message

A B Неисправность Причина Примечание

Fujiko-ODA The true disposal method is indicated as a machine. — Especially a different portion from the disposal method of a former machine is. system fail/sub system fail (I have a person in charge indicate Fail which requires hard / mechanism part exchange) Fujiko-ODA True detection conditions are indicated as a machine. — Especially the portion the detection conditions of a former machine are indicated to be as they are is. It is cautious of system fail/sub system fail

008 153 (IOT JAM) Feed Jam 1 (Early Feed Jam )
The paper arrival to a Reg position is too early Needlessness The paper arrival to a Reg position is too early

008 155 (IOT JAM) Regi Sensor On Jam
Reg Sensor is in On state in Warming up

008 156 (IOT JAM) Regi Sensor Off Jam
A paper does not come for a Fuser position from a Reg position within regulation time

008 176 Tray 1 Regi Sensor On Jam
Imari: REGI SNR ON JAM (Tray)
GINGA: Tray1 Missfeed Jam The same as that of user disposal Even if it carries out regulation time progress from a Tray1 Feed start, a Reg sensor does not turn on

Sensor of IOT Sub detects only by one. Although a display is different for every tray, this will display for the Jam Zone information sent apart from Chain Link.
(Imari: Jam detection specifications K4) No.2 / Regi Sensor On Jam / Feed Tray#1-4

008 180 Comm: Duplex In Sensor On Jam
(C6-1) Dup Miss Feed Jam Duplex In Sensor is not turned on in Duplex conveyance operation

Since the timer of operation from a sensor changes with paper sizes at the time of Duplex Module printing, there is two kinds of REGI SENSOR ON JAM.
(Imari: Jam detection specifications K4) No.2 / Regi Sensor On Jam/ DUP

008 314 Between DCSYS-DM Duplex Unit was separated after the I/F unusual power supply injection
Duplex Unit Fail was detected

009 413 Toner Black 1 Near Empty The same as that of user disposal When Dispense Motor of Black becomes circumference sky of regulation time closely

Toner Status
* HID 980420 *HID 980430

009 460 Toner Black Quality Life End (only display) Needlessness CRU life operation was set up for not stopping by the panel, and after IOT detected Toner Warning, data transmission was performed by 100 sheets

009 670 New Toner Detected – K

009 671 New Toner Detected – C

009 672 New Toner Detected – M

009 673 New Toner Detected – Y

009 909 Topo: EP Cartridge Type Missmatch The same as that of user disposal Unentered

009 910 Topo: EP Cartridge Not Installed

009 938 GINGA: Black Toner Cartridge Detached When K toner cartridge is not set

030606 Delete from Comm (Fu/Ta/Sh)

010 105 Fuser Exit Sensor On Jam
Imari: F/U EXIT SNR ON JAM (at the time of F/U discharge)
GINGA: Exit In Jam Ginga: After RegRoll turns on, even if it carries out regulation time progress, an Exit sensor does not turn on

With no “Imari: Jam detection specifications K4″ correspondence

010 106

010 112 GINGA: Exit Out Early Jam Ginga: After an Exit sensor turns on, an Exit sensor does not turn off within regulation time

010 128 Duplex Pre Regi Sensor On Jam Topo: The paper arrival to a Reg position from a Duplex Sensor position is too early

010 132 Duplex Path 1 Sensor On Jam A paper is not discharged from a Duplex Sensor position within regulation time, or Duplex Sensor is in On state in Warming up

010 164 Regi.SNR On Jam (C6-2) “Dup Miss Feed Jam” (not wait) Topo: A paper does not come for a Reg position from a Duplex Sensor position within regulation time
sheeta: Duplex Out Sensor is not turned on in Duplex conveyance operation

010 347 “OCT failure”: Offset Fail (OCT)
Failure detection / wearing detection cannot be carried out in the “Imari” present condition

010 398 Fuser Fan Fail (U4-9) If not repaired in power supply OFF/ON, it is FUSER Fan exchange The logical sum OR of a FUSER FAN lock signal and a LVFAN lock signal is taken, and it considers as a FAN LOCK FAIL signal
Ginga: When Fuser FAN does not turn at regular number of rotations

Discharge and Billing all the papers that have already Feed(ed)

010 420 Fuser ASSY Change Soon
GINGA: Fuser Unit Pre Warning The same as that of user disposal When PV reached the regulation value and becomes a life closely

011 108 OCT Jam 1 (paper attainment is not carried out at OCT) [ from an Exit Sensor position / to an OCT Sensor position / in a paper ] within regulation time

011 109 OCT Jam 2 (paper attainment is not carried out at OCT) A paper is not discharged from an OCT Sensor position within regulation time, or OCT Sensor is On state in Engine Warming up

012 300 Faceup Tray was opened during printing
When Cover Interlock Open of FaceUpTray was detected in JOB, Faceup Tray was opened during printing in Standard mode or OCT mode

012 301 Faceup Tray was closed during printing
Faceup Tray was closed during printing by Faceup Tray

012 951 OCT_FULL_STACK
Full Stack (OCT) was detected

012 952 FaceUP Tray Open Although the output to Facedown Tray or OCT was specified, it detected that Faceup Tray was open

012 953 FaceUP Tray Close Although the output to Faceup Tray was specified, it detected that Faceup Tray had closed

012 965 FIN STAPLER PIN NEAR EMPTY
Imari: Stapler Near Empty
GINGA: Stapler Near Empty
Topo: Stapler Near Empty Low Staple Sensor OFF When ON of Low Staple Sensor is detected at the time of – power supply injection and Interlock Close in one of the following cases and ON of Low Staple Sensor is detected just before – Staple Head Close operation implementation

012 969 IOT Center Tray Full H-Tra IOT Full Paper Sensor continues and it is between 1sec(s) OFF H-Tra IOT When Full Paper Sensor detects ON by continuation between 10sec(s)

Since a Center tray turns into a tray different from a base when Light Finisher is attached, 7-969 assigns a code independently

016 450 SMB host name duplication A host name is changed PC which has the same host name existed on the network

016 452 IP address duplication An IP address is changed PC which has the same IP address existed on the network

016 453 IP address acquisition failure from a DHCP server An IP address is set up (the acquisition from a DHCP server is not performed) IP address acquisition went wrong from the DHCP server

016 454 Renewal of Dynamic DNS-dynamic goes wrong Needlessness Needlessness

016 460 A FULL state is detected at the time of HD access. The error of which FULL is canceled also for the waiting for time

016 500 SMTP Server Address Resolution Fail for Mail IO -

016 501 POP Server Address Resolution Fail for Mail IO -

016 502 POP Authentication Fail for Mail IO -

016 503 SMTP Server Address Resolution Fail for Redirector -

016 504 POP Server Address Resolution Fail for Redirector -

016 505 POP Authentication Fail for Redirector -

016 701 A PLW deconstructivism memory is insufficient Imari: Since a PLW memory is fixation, if it can lower resolution, it will be lowered The shortage of a memory was detected at the time of ART EX use

Imari: The memory for “print log” PLW processing of a job is insufficient

016 702 1 page was uncompressible A memory is extended, resolution is lowered or it is made printing guarantee mode (printing guarantee mode — PLW) in PCL, “a PCL heap memory / band buffer ratio” is made 1:2 or more setup (Chainlink 801-916 of “O2AP”) Shortage of the print page buffer which has not been compressed 1 page was detected

016 703 Un-establishing and the invalid confidential box number were specified at the time of E-Mail reception 1. Establish an E-mail transmitting
2. Relevance box to effective box At the time of E-mail reception, un-establishing and an invalid confidential box state are detected, and a job end is carried out

016 704 Confidential box full (the number of the maximum documents was exceeded around one box) is detected, and a job end is carried out An unnecessary document is deleted and processing is performed again At the time of HD access, a FULL state is detected and a job end is carried out

016 705 Security accumulation cannot be carried out without HD It checks whether it has equipped with HDD.
When a trouble occurs at the time of wearing, it checks whether operation of a security print is wrong Security accumulation could not be carried out without HDD, but registration of a security print went wrong

016 706 The job end of having exceeded confidential and the number of the maximum users of a proof print is detected and carried out Unnecessary document/user are deleted and it is execution of a re-print At the time of HD access, a FULL state is detected and a job end is carried out

016 707 A proof print is impossible (conditions in which a proof print is possible, such as HD-less/HD failure, do not gather) It checks whether it has equipped with HDD
When a trouble occurs at the time of wearing, it checks whether operation of a proof print is wrong You could not accumulate without HDD but registration of a proof print went wrong

016 709 PLW Command Error
An error is detected by PLW deconstructivism Job is canceled and it performs again The ART EX command error occurred during PLW processing

016 710 Delayed Print Fail

016 716 The file which carries out a spool by the “TIFF file injustice” TIFF exceeded disk capacity With no necessity

016 719 A PCL deconstructivism memory is insufficient PCL memory size is increased The shortage of a memory is detected at the time of PCL use

016 720 PCL Command Error
An error is detected by PCL deconstructivism Job is canceled and it performs again A PCL command error occurs during PCL processing

016 721 Other errors I have the same job performed again, the state of an error is checked, and it looks for support of Support G The error which is not expected during print processing

016 726 A “automatic judging error” Auto SW automatic judging was not able to be carried out Fixed selection of the Decomposer is carried out Print language automatic judging error

016 728 Tag which is not mounted in a “TIFF file injustice” picture file deployment library is included -

016 729 The number of “TIFF file injustice” colors and the number of pixels were specified exceeding the maximum of the effective range -

016 730 “ART command error” The command which is not supported by ART was detected A non-supporting command is deleted and re-printed out of data ART IV command error

Although the “gtemul” command is a command of the meaning of “changing to the print mode of an option cartridge”, in multi-PDL, a print language change cannot do it
Error log needlessness “print log” ART command error. Processing was stopped

016 731 “TIFF file injustice” TIFF data is way piece by the middle -

016 732 “Form composition error” In emulation, when the specified form is not registered, the data itself is not printed - Deconstructivism detects that the specified form is not registered

016 744 It is contained in PDF to which the function which is not supported was sent A visitor is requested to have you print via a driver from Acrobat Reader In PDF1.3, Transparency or JBIG2 was contained in the PDF file

016 748 At the time of confidential box access, a FULL state is detected and a job end is carried out The capacity of HDD is vacated and it is execution of a re-print At the time of HD access, a FULL state is detected and a job end is carried out

In Print Job, since the job end only of a part to have been stored in HD is printed and carried out, what is defined as “un-giving a definition / Job Fail” is used
In Copy Job, since a message is displayed and it waits for user directions, what is defined as “Others/Notice” (3-981) is used
Description of the “Fault item” sequence is united above and corrected

016 749 The syntax error of a “JCL/PJL syntax error” JCL/PJL command was detected A command is corrected The syntax error of a JCL/PJL command was detected

016 751 PDF Error The same as that of user disposal When a syntax error, use of the command non-given a definition, a parameter error, breakage of a PDF file, and the internal error of PDF deconstructivism occur during PDF Bridge processing

016 752 PDF Short of Memory The shortage of a memory was detected during PDF Bridge processing

016 753 PDF Password Mismatched Password protection is carried out. When the password of UI panel setup and the password specified by XPJL (it sets up by Contents Bridge) are not in agreement by the case where a PDF file is processed

016 754 PDF LZW Not Installed LZW compression technology was used in the state where the “Contents Bridge extension kit” is not installed. PDF file processed by PDF Bridge

016 755 PDF Print Prohibited Printing prohibition specification was carried out when a PDF file is processed

016 757 Auditron – Invalid User

016 758 Auditron – Disabled Function

016 759 Auditron – Reached Limit

016 760 The error occurred in “PS Decompose error” deconstructivism pause processing A job is broadcast again (the check of execution environment / data is required at the time of a recurrence) The error occurred in deconstructivism pause processing

016 761 “Image output” FIFO EMPTY error It prints in speed priority mode. When this cannot be printed, either, it prints in printing guarantee mode Picture extension error (FIFO EMPTY error)

016 762 “Decomposer absence” The functions (a print language, print utility etc.) which are not mounted were required (decomposer specified in PJL or Auto SW is not mounted) Fixed selection of the Decomposer is carried out The functions (a print language, print utility etc.) by which print language non-carrying mounting is not carried out were required (decomposer specified in PJL or Auto SW is not mounted)

016 764 SMTP server connection error Needlessness SMTP-server response code: 421 or 451

“Result code” of an error log character sequence is prescribed by RFC

016 765 SMTP server HD full The same as that of user disposal SMTP-server response code: 452

016 766 The problem of an SMTP server file system SMTP-server response code: 552

016 767 E-mail address address injustice SMTP-server response code: 550 or 551

016 768 Transmitting agency address injustice (login error) It error-answers by the “MAIL FROM:” command of an SMTP protocol

016 769 An SMTP server un-corresponds to DSN Response code of the “EHLO” command of an ESMTP protocol: There is “no DSN” in the support command list received from 502 or the server

016 781 Server connection is not made at the time of “network connection error at time of network scan” transmission 1. Main part From 2. transmission place server which sets up correctly a “subnet mask” and a “gateway” “ping” etc. 3.Win 95 which checks that M/C can be seen From a UNIX machine to a transmission place server It checks that it is connectable by ftp Connection establishment with a FTP server goes wrong

016 796 Control of mail printing by user setup
Imari-MF PL2/AP or subsequent ones
In E-mail reception, since the mail which does not have an appending document in the state of a setup of “not printing a header and the text” was received, mail was canceled
In the case of the above-mentioned case, it leaves Mail IO to the purport and error history report which canceled mail at ChainLink
A mounting top job is not generated

016 797 Output place injustice of reception mail - It is after change Imari-MF PL2/AP to 127 – 027
Job is not generated
E-mail to Box and E-mail to Fax drop(ed). When E-mail is received by this specification

016 798 No TrustMarking Option - When Decomposer call(ed) S-Image lib, the error without HD came on the contrary

016 799 Print Instruction Fail detected in PLW
When a print parameter error (003-747) is found by PLW

016 981 A FULL state is detected at the time of HD access. The error of which FULL is not canceled for the waiting for time, either finishing [ 1 page or more accumulation ] HDD partition size of the service which corresponds if nonavoidable with user disposal is made large

016 982 A FULL state is detected at the time of HD access. The error of which FULL is not canceled for the waiting for time, either (1 page cannot be accumulated) HDD partition size of the corresponding service is made large When HDD is judged to be full by the job, the precedence accumulation job, and the interruption job