If more than 10 instances of a single print job is being tracked by Argos within 15 minutes of each other and no physical prints are being generated by the device, the issue could be a corrupted spool file or a problem with the software on the device itself.
Review the job details to determine which printer is having trouble and on which computer the jobs are spooling. For devices being tracked through a print queue, the name will be in UNC format with the computer name followed by the printer name (i.e. \\computer_name\printer_name)
Argos Desktop Billing Client:
Argos Communication service health page (http://Argos_ServerName:7080/cs/health)
Argos Manager > Reports & Data > Allocated/Pending/Recycled tabs
- On the server or workstation where the printer is spooling, Click Start > Run, type services.msc.
- Right-click on the Windows Print Spooler service and select Stop.
- Right-click on the Argos Agent service and select Stop.
- Browse to the Windows spool folder (default location is C:\Windows\System32\spool\PRINTERS) and delete all files.
- Back in the Windows services console, right-click on the Windows Print Spooler service and select Start.
- Right-click on the Argos Agent service and select Start.
If clearing the spool folder and restarting services does not resolve the problem, the problem could be with the software on the device itself. Powering the device off completely and restarting should clear out any jobs from the printers memory.
To minimize impact on the affected user, stop the Argos Agent service on the user’s computer until the problem is resolved. Jobs that have tracked but not yet been billed, can be sent to the Recycled tab in Argos Manager to prevent them from prompting the user. Once the jobs have been moved from the Pending queue, restart the Argos Agent service on the user's computer.