# Infor LN Reports Stuck in the Print Queue: Device and Spooler Fix > Source: https://netray.co/erp-help/ln-report-stuck-print-queue-device-offline > Publisher: Netray (netray.co), AI and integration engineering for ERP and manufacturing systems. > Section: ERP Help ## Short answer Infor LN reports and forms stay queued and never reach the printer when the target device definition points to a printer that is offline, or the print listener on the print server has stopped. Check the device's status in Common > Printing > Devices, confirm the underlying OS printer is reachable, and restart the print listener if jobs remain queued after the printer itself is fixed. Most cases trace back to a genuinely offline printer, not an LN bug. ## Kind error ## System infor-ln ## Erp Infor LN (Baan ERP) ## Module Printing & Device Management ## Query infor ln report stuck in print queue device offline ## Alternate Queries - infor ln print job not printing - baan device offline error printing - infor ln spooler not sending to printer - infor ln report writer output stuck queued ## Applies To Infor LN 10.x printing and report management (Report Manager, device-based printing); applies to physical, PDF and preview device types ## Steps ### Clear a stuck print queue and get output flowing again **Items:** Open Common > Printing > Devices and check the status and definition of the device the stuck report is targeting. Confirm the physical printer or print server share behind that device definition is actually online and reachable from the LN application or print server, not just from a user's workstation. Check whether the print listener or spooler process on the print server, the component that pulls queued jobs from LN and sends them to the OS print queue, is still running. Look at the OS-level print queue on the server for the target printer; jobs can be stuck there (paused, in an error state, out of paper or toner) even after LN has handed them off successfully. If a specific device consistently fails, test with a different, known-good device definition to isolate whether the problem is the device definition or the printer and network path itself. Restart the print listener service if it has stopped, then confirm previously stuck jobs either resume automatically or need to be resubmitted from the report's own history. For reports rendered through Report Writer, SSRS or a PDF output device, confirm the rendering service itself is running, since a stalled rendering step can look identical to a stuck print queue from the user's side. ## Sections ### How LN printing is put together **Body:** Infor LN does not send output directly from a session to a Windows or network printer. It writes the job to a device, a logical definition mapping to a physical printer, a PDF file location, a preview window, or an external rendering engine such as SSRS. A print listener process on the designated print server picks up jobs queued for physical devices and forwards them to the OS print queue. This layered design means a stuck report can fail at any of several points: LN never queued it, the device definition points somewhere invalid, the listener is not running, or the OS-level printer itself is offline or in an error state. Working through the layers in order, LN queue, listener, OS queue, physical printer, finds the actual break point fastest. ### Device definitions versus the physical printer **Body:** A device definition in Common > Printing > Devices is just configuration, it has no awareness of whether the underlying printer is actually turned on or reachable. If a printer is replaced, renamed, or moved to a new print server, the device definition has to be updated manually; LN will keep queuing jobs against a device pointing at a printer that no longer exists. This is the single most common real-world cause of a stuck queue: an IT change to printer infrastructure, a print server migration, a renamed share, a firmware update that changed the printer's network name, that nobody reflected in the corresponding LN device definition. ### When it is a rendering problem, not a printing problem **Body:** For sites using SSRS or another external rendering engine for report layouts, a job can appear stuck in the print queue when the actual holdup is the rendering service failing to generate the output in the first place. Check the rendering service's own status and logs separately from the print listener if the device and printer both check out fine. ## Pitfalls - Only checking whether the printer is reachable from a user's desktop, rather than from the LN application or print server itself, which may be on a different network path. - Restarting the entire LN application server to fix a printing problem when only the print listener service needed a restart. - Not updating the device definition after a printer or print server change, leaving jobs queuing against a target that no longer exists. - Missing an OS-level print queue that is paused or in an error state, after confirming the printer itself has power and paper. - Treating a rendering engine failure, for SSRS or similar, as a printing problem and troubleshooting the wrong component. ## Ai Angle For a recurring printing issue, a grounded LN assistant can pull the device definition, the print listener's last known status and the OS queue state into one answer when a user reports a stuck report, instead of the help desk walking through each layer manually for every ticket. Over time it can also spot patterns, for example the same device failing after every print server change, and flag it to the admin before the next report gets stuck too. ## Faq ### Which session manages printer devices in Infor LN? **Answer:** Common > Printing > Devices defines the logical devices that LN sessions and reports print to, including the device type, physical printer, PDF, or preview, and, for physical devices, the print server and OS printer it maps to. ### Why does printing work for some users but not others? **Answer:** Users are often printing to different device definitions, either their own default device or one chosen at print time. If only some users are affected, compare the specific device each of them is targeting rather than assuming a site-wide printing outage. ### Do I need to restart LN to fix a stuck print queue? **Answer:** Usually not. The print listener or spooler service on the print server, and the OS print queue for the specific printer, are almost always enough to check and restart. A full LN application server restart is rarely necessary for a printing issue alone. ### How do I stop this from recurring after printer infrastructure changes? **Answer:** Build a step into your IT change process that includes updating the relevant LN device definition whenever a printer, print server, or network printer name changes, rather than treating LN configuration as a separate, easily forgotten step. ## Search terms infor ln print queue stuck, infor ln device offline error, baan print listener not running, infor ln printing devices session, infor ln report not printing, infor ln spooler troubleshooting, baan erp print server configuration, infor ln ssrs report stuck, infor ln common printing devices --- Talk to an engineer: https://netray.co/contact?intent=erp_ai | Machine catalog: https://netray.co/agent/catalog.json