Pharos Administrator Alert Error Message: "No Popup data available"

When I review the Pharos Administrator Alerts log I see the following error message:

Error 29074 "No Popup data available"

Error 29049 "Direct queue error on job '' for '': No popup data available

Jobs do not appear at on the printer when this error message occurs.

There are two possible configurations that cause the problem

Third Party Charging Only Questions

If you have configured the spool queue setting "Must Use Popups" to "Yes" and the question group is a third party charging question group then print jobs will fail with the errors above. This is by design in Pharos 7.2 and customers should set this option to "No" to resolve the issue.

Long Printer Queue Name

The problem is caused by either a long printer queue name or a space in the queue name when it is created in Pharos Administrator. When the Pharos Package is created or installed on a client workstation. The Popup Client does not report any error but because of the long queue name an Alert is generated and the print job is not delivered to the Pharos queue. To resolve this issue, edit the name of the Pharos Spool Queue, removing spaces and/or making the name shorter, and recreate the packages. Pharos recommends queue length of less than 32 characters and names that contain no special characters such as spaces, semicolons, quotes, or question marks.