Error ID |
Meaning |
Solution |
204 |
Print monitoring service startup failure because of database connection problem |
Make sure system installed successfully. Make sure database server is accessable and service in running If the print server is a stand alone server, please make sure the dominating server is specified and configured successfully If we need to test the SQL Server 2000 installed on Win2003, SP3 is required. |
200 |
Print monitoring service startup failure because of license issue |
The problem may be caused by trial version expiration or the USB software dog detection failure. Please check the event log for detailed information Terminating the wizard during installation process will lead to error also. |
201/202 |
Print monitoring service stop because of license issue |
Same solutions as 200 |
1000 |
Print monitoring service starts up in order |
|
1006 |
Print monitoring service stops in order |
|
2091 |
Detailed information of printing task |
It includes all the detailed information of each print task being monitored. |
2071 |
List of printers being monitored is added when print service startsTh up |
This log shows the list of printers being monitored when print service starts up. |
3460/3470/3480 |
Error of print monitoring service occured when controlling print tasks |
The sporadic error can be ignored. Continued errors can be resoved by restarting ther monitoring service. |
3560/3570/3580 |
Error of print monitoring service occured when monitoring print tasks |
The problem is caused by database connection failure. The sporadic error can be ignored. Continued errors can be resoved by restarting service. |
2500/12004 |
Error in service update |
The problem is caused by database connection failure or configuration error. The sporadic error can be ignored. |
4330 |
Database connection testing failure |
Refer ID 200 and ID 204 soluctions |
20102 |
Fail to read registration info from USB software dog |
Make sure USB software dog connects to USB ports correctly. |