Has anyone seen this error?
“An error occurred while polling the print queue: Value cannot be null”
This is the error shown from device hub on the end user’s computer, but sounds like the file or a related field data is just missing when device hub is trying to poll it to print.
This is occurring when trying to print shipping labels.
I may restart Acumatica to see if it clears the queue and new documents succeed.
Question
Device Hub: An error occurred while polling the print queue: Value cannot be null
+6+6I forgot about the Print Jobs screen, I’m clearing them out from there. That should get us going, but still interested to know if anyone has figured out why this happens and how to prevent it?
We get a number of errors with Device Hub that almost all stem from a lost connection between the workstation hosting Device Hub and Acumatica (most often service interruption from our ISP, but also happens with scheduled maintenance on the Acumatica server)
In the end, the solution is always simply closing and re-launching Device Hub. Since upgrading to 23R1, the system typically finds and process failed print jobs, but prior to that we would re-process from Print Jobs (SM206500)
Attached is a GI we use to alert us of failed print jobs - we have a widget on a number of managers dashboards monitoring this so that we can quickly reset Device Hub and reprint when needed
+4
It may be related to this known issue.
“AC-306514: If DeviceHub was configured to return print jobs by polling and a user attempted to print a document via DeviceHub, the system showed the following error message: Print job has no ‘FILEID‘ parameter configured. The print job will be discarded.
Workaround: Configure Device Hub to use push notifications to return print jobs.”
Michael Shirk, Pine View Buildings, LLC - If a member helped you, please *Like* their post. If a member provided an answer to your question, please mark it as *Best Answer*.
+4We had a lot of issues and ended up setting up a task on the machine that hosted device hub to restart it every night.
We had enough issues that we actually implemented a 3rd party print server (PrintNode) which has worked flawlessly.
It required some customization effort to implement, but since then I don’t think we’ve had a single failed print job.
Michael Shirk, Pine View Buildings, LLC - If a member helped you, please *Like* their post. If a member provided an answer to your question, please mark it as *Best Answer*.
+6Thanks for all the suggestions. In my situation the issue is related to specific labels so it’s not a connectivity issue with Device Hub, but if I delete that specific job the rest will print. Then the user just prints the PDF from their local machine for that particular job.
I think it’s more of a bug on the Shipping side than the Device Hub side.
I wish I knew which field was Null. I’ll probably submit a ticket next time this happens and record which jobs so we can try to find a pattern.
https://www.fiverr.com/acudatica
1 person likes this
+13This may be a long shot. Does the label have parameters? Are the parameters added to the Viewer Fields (or something like that; the last tab of the Build Schema dialog)?
Daryl ⚡Contract Acumatica Developer (MVP🏆) for hire ⏩ linkedin.com/in/darylbowman
1 person likes this
Reply
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.