Alert Codes for Uniprint, Off-The-Glass, and SignUp

To find out more about a coded alert, please use the Pharos Administrator Help system. To do this, select Help in the top menu bar of the Administrator, and then select Help Topics from the dropdown list. You may search on a particular alert code or get an overview of all Uniprint Suite alert codes by searching on "Alert Index".

 

License Server Alerts

Alerts sent by the Pharos License Server are also written to the Events Log of the PC on which the Pharos License Server is running.

Message
“'_' license limit has exceeded the expiry date.”
Discussion
The license on the named Pharos component has expired. Contact licensing@pharos.com for a new license for this component.

Message
“Early Warning: Running low on '_' license limit.”
Discussion
The Early Warning limit configured on the named Pharos component has occurred. Contact licensing@pharos.com for a new license for this component.

Message
“Critical Warning: Running low on '_' license limit.”
Discussion
The Critical Warning limit configured on the named Pharos component has occurred. The License Limit is about to expire. Contact licensing@pharos.com as soon as possible for a new license for this component.

Message
“Attempt to exceed '_' licensed for.”
Discussion
Someone tried to make more use of a component than the system is licensed for.

Message
“Unable to retrieve info on limits not known at compile time.”
Discussion
Registry information is corrupted. It must be reinstalled.

Message
“Unable to start Limit Information Database.”
Discussion
The Pharos License Server cannot start.

Message
“Dongle failure. License server shutting down.”
Discussion
Contact Pharos.

Message
“Limits can't fit into the dongle.”
Discussion
Updated License Limits no longer fit into the dongle. Contact Pharos for a dongle with more memory.

Message
“No matching OpenRequest found.”
Discussion
There is a bug in the Client making the request.

Message
“Item 'X' in list is illegal.”
Discussion
There is a bug in the Client making the request.

Message
“Error when trying to compose a reply packet '_'.”
Discussion
A network fault has occurred/ out of memory.

Message
“Error: Dongle reports error 'DongleError'”, where 'DongleError' is one of:

  • “No Dongle or License Key found”
    The Pharos License Server could not find a license. Check dongle is inserted correctly, that it is in the correct port and that the port is working.
  • “Dongle is corrupted”
    Licensing information in the Dongle is corrupted.
  • “Cached license info is corrupt”
    The cached copy of the Dongle's information kept in the Pharos License Server is corrupt.
  • “Unknown format for data in Dongle”
    The license format has changed. Pharos License Server needs to be updated.
  • “Dongle is faulty”
    Contact Pharos.
  • “Dongle needs replacing, it's almost worn out”
    A Dongle has a finite life. Contact Pharos for a new one.
  • “The Dongle has been removed. Please replace”
    The Dongle has been removed, or is loose or is incorrectly plugged in. Ensure that the dongle is securely plugged in, that it is in the correct port, that the port is OK.
  • “The License Key is invalid.”
    Someone has tried to break the licensing system. Restore the License Key to its original form as supplied by Pharos.
  • “The License Key has expired.”
    Contact licensing@pharos.com for a new license.
  • “Unspecified Error.”
    Some problem has occurred with the Dongle/ License Key other than those specified above.
  • “No Error/ Error has been corrected.”
    Reported problem has been fixed.
  • “Error: Can't read limits in Dongle.”
    The license format has changed. Pharos License Server needs to be updated.


Alerts written only to the Events Log

A limited number of alerts are written only to the Events Log.

Message
“Unable to connect to DB Server.”
Discussion
The Pharos License Server is unable to contact the Database Server to log an alert.

Message
“Unable to send Alert to DB Server.”
Discussion
The Pharos License Server contacted the Database Server but the Database Server would not log an alert.