1 of 1 people found this helpful
I don't see this data being readily available in the database. the only place I can find reference to a "Free Print" job is in the Alerts Table. As I don't have one in my Table I can't say for certain but it looks like the message column doesn't contain any device information. The "message" column looks to contain the Queue the job was sent to.
SELECT * FROM [pharos].[dbo].[alerts] WHERE MESSAGE LIKE '%free%'
There is a reference in the Alerts table? I don’t see any place Administrator or Reports to see those items. ☹
- Paul L.
There looks to be but I can only see in my Alerts Table a reference to the server/queue not the device unfortunately.
Thank you Jeff. Guess (on my behalf) this then becomes a “Feature Request”.
I think it would be worthwhile to be able to get a report that shows the instances when a “Free Print” was triggered, and include what printer had been attempted when the “Free Print” was triggered and why. This would be useful for diagnostic purposes.
- Paul L.
2 of 2 people found this helpful
When a print job fails to release to device for some reason, you should see entries such as the following in the Alerts context in Administrator. Each of the following can be found with Error Code: 29062, so start by filtering Administrator using this Error Code.
"Error releasing print job: Retrying  out of  to release job for Owner [kat] to printer [10.0.2.67]"
"Job failed to release on a Printer: [3 Retries] Could not connect to the printer '10.0.2.36:9100' via RawClient. A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed bec..."
"Job failed to release on a Printer: [3 Retries] Could not connect to the printer '10.0.2.36:515' via LprClient. A connection attempt failed because the connected party did not properly respond after a period of time, or established connection failed beca..."
The 'printer' info in each of these is actually the IP address of the device that the job is being sent to, not the name of the device, but may still be partly useful in identifying devices that are experiencing problems.
I hope this helps a bit.
Thanks. This is helpful. Using Code: 29062 as you suggested, I was able to use the Alert List report to output a Excel (Data only) report, which I then filtered to qroup the data, then converted the Error Message column (Text Columns, Space) which helped to put the printer's IP name in a column of it's own. This made it a lot easier to identify locations where this happens frequently and analyse issues.
A few steps, but I got the info I was hoping for and can look into the probable causes.