Print monitoring service can not be started

Several reasons could lead to the Print Monitoring Service startup failure and the common reasons are incorrect installation, database connection failure, trial version expiration or software dog detection failure. Please follow the steps below to find the solutions:
All operations will be recorded in the Event Log. To check log can find the main error reasons mostly. Right click on the tray icon

on the bottom right of the screen-->Event Log.
1. Rigth click on the tray icon on the bottom right of the screen-->select system settings-->test settings. If the testing could success, that means database connection is OK; if it fails, the possible reasons could be:

Reason	Diagnosis	Solutions
Fail to connect to the main server is caused by the firewall on the print server or the dominating server which blocks the communication.	Test Settings displays failure. Check Event Log to see if there is a following Error No. 5020: An unknown error occurs in system module CommonU.GetConfigFromMasterServer, error message is AppUrl=http://JAMES:8200/setup Socket Error # 10061 Connection refused.	Turn off the firewall, or open the TCP port 8100, 8200 UDP port 8201-8209
PrintUsage Application Service on Web manager site does not start		Start the Webmanager server PrintUsage Applicationservice
Dominating server's computer name cannot be recognized.		Input dominating server's IP address, or add the corresponding IP address of the dominating server to HOST file.
There are problems connecting to the database server.	Test settings displays failure. Check Event Log to see if there is an error No. 4330 and analyze the problem according to the error message.	Make sure database service started If database is MSSQL, make sure authorization mode is SQL Server and Windows mode
Database server name could not be correctly resolved.		Use IP address as the database server name when installing manager server. Add the corresponding IP address of the dominating server to local HOST file.

2.Check for error No. 204 in the Event Log:
It is caused by connection failure between Print Monitoring Service and database. Please followstep 1 to find the solution.
3. Check for error No. 200 in the Event Log
The error is related to software license and the possible reasons are:

Reason	Diagnosis	Solutions
Trial version expiration	License displays trial version expired. No. 200 log information is: TRIAL_USE_EXPIRED or LICENSE_EXPIRED_REGCODE	Purchase the full version.
Incorrect installation	Trial version Date/Time displayed in license area is some date of 2002 or 2003. It will randomly change to another date after clicking Apply button. Message of error No. 200 in Event Log is: CANNOT_GET_REGCODE_FROM_DB	Reinstall the system and make sure the installation is successful. It takes about 10 to 30 minutes to import users for large domain. Don't cancel during the process.
Software dog detection failure	Only occurs in office version Message of error No. 200 in Event Log is: NO_DONGLE_DETECTED	Make sure software dog is pluged into the USB port. You can plug the USB software dog in and restart PrintUsage Application service