Printer Setup

Does anyone know what are Lawson’s Best Practice on Printer setup?
Is it Preferred to install every printer and print driver installed local on the Lawson Application Server and point PRTDEF to the printers using the Lawson Server Name as the print server
OR
Is it Preferred to point the PRTDEF to the path of a valid Network Print Server ?

Find more posts tagged with

Infor Lawson Technology Group - Discussion

Comments

unknown

Good question Kathy. If users are on Portal then they could print to any available network printer to them. Generally speaking, only printers should be set up which are expected to receive print-out directly from a Lawson job. For example, pick list or labels.

dscheppa

Our automated jobs and pik tickets are sent to a Printer assigned to that location.
We have been experiencing 100% CPU spikes from rundll32.exe hung and have tied it back to the printers. During these times the server is rendered useless and we are looking for a better solution. We support multiple locations and every location has a print server with a list of printers to point to. I'm thinking pointing to the network print server would remove the I/O stress from the local server.

Lawson said the rundll32 hangs because it is waiting on the status of the printer and I looked and we did have a couple printers needing Toner. Could this really cause this horrific interruption? I asked for their best practices and they replied they don't have one!

richardd

We use a network print server. No response issues.

plancor

We are experiencing the exact same issue. I, too, opened a case with Infor and was told that the problem was outside of the Infor software, so they wouldn't help resolve the problem. We print pick lists to a specific Lawson defined printer at one location only. This problem happens often enough that it is unlikely that the printer would need toner that often. In our case, the CPU spikes, but doesn't stop all other processing - everything else just gets really SSSSLLLLOOOWWW. Once the rundll32 processes are ended, everything goes back to normal. I would love to hear of a solution to this problem.

dscheppa

I will add a snapshot of my printers and the correlation of hung processes and the Printer status not ready -is a real time event. Plus I found the message in the windows Application event logs. We are now testing one site at a time moving the printers to a network printserver and off the local Lawson Server.

unknown

We also use our Print Servers and have no issues. When we first started with Lawson we used the Lawson servers as the print server and had similar issues. Since we changed over to use our standard print servers we are fine and we print pick tickets every 15 minutes.

lxiong3

Kathy,

Yes, we actually had something similar happen. We had an issue where MSCM par counts were not being captured. After reviewing the logs, we found that a print job was transmitted to an offline printer causing any additional activity in MSCM to be halted for all facilities until that SYNC record was processed. We went back and disabled any printers that were no longer in use to avoid any further incidents and will be looking at a way to monitor/alert this type of issue in the future. Here's the explanation we received from GSC:

The HHSync scheduler processes all SYNC records in sequential order based on the SYNC_ID value. If a SYNC record involves a printer (as noted in the DATA XML), then a print request to that printer is made during the processing of the SYNC record by the scheduler. Normally when the printer has finished printing, a notification is returned to the scheduler of this fact and the scheduler moves on the next SYNC record. However, if no response is received from the printer after the scheduler has sent the print request, then the scheduler sits and waits -- expecting that a response will be returned from the printer. If the printer is off-line or does not return a response, the HHSync scheduler will simply hang waiting for a response that will never occur.

0911060553270289.pdf

Copyright © 2025 Infor. All rights reserved.