Prev
Next
Forums Infor / Lawson Platforms S3 Systems Administration

Issue with LAPRINT and PO20 issue draft causing headache

 5 Replies
 0 Subscribed to this topic
 27 Subscribed to this forum
Sort:
Author
Messages
Ronnie
Veteran Member
Posts: 152
Veteran Member
7/29/2015 11:12 AM

    Ok,

     

    Here is the situation. We have a user who called on Monday who could not print to her printer. Now the system is freezing in PO20.

     

    Here is what we have figured out:

    I think we have the issue "maybe" narrowed down to a certain user. domainname\user

    The system is fine until she goes to PO20 and does an "issue draft" on any PO which is set to autoprint to a printer. (automatically does a laprint command to her printer that is setup...I don't know where this is set up to autoprint)

    When she does the issue draft on PO20, the system then hangs up and no one can inquire on PO20, etc.

    Also when she does, we have noticed the process of laprint and lawbatch hang in the task manager under processes with her username.

     

    If we go and kill these hung processes everyone can inquire and work again, but once she tries another issue draft the system hangs up and messes everyone up.

     

    We have rebooted our Lawson environment and servers etc.

    Ronnie
    Veteran Member
    Posts: 152
    Veteran Member
    7/29/2015 11:26 AM
      well, the issue does not seem to be user related at all. it seems to be printer related from what I can tell.

      I have narrowed down the issue.



      The issue is DEPOTINV printer.



      The issue happens when the laprint command is ran to this printer.



      I tested an issue draft as Lawson to depotinv...sure enough, the system hung up and the processes were hung on the app server. Once I killed stuck laprint on the server, the system unhung.
      troelofs
      Advanced Member
      Posts: 19
      Advanced Member
      7/29/2015 11:53 AM

        If this is a new printer, it's possible the Windows server is trying to install a print driver for it and the user running the job does not have the correct permissions. Try printing to the printer from a LID session on the server when you are logged in as a Windows administrator. You can also run the laprint command with an option and a ? to query the printer to find out what options it supports. This should force Windows to install the print driver if it is needed. I do this when I have a new printer to define to the server. The command is laprint -o ? your_printer_name

        Ronnie
        Veteran Member
        Posts: 152
        Veteran Member
        7/29/2015 1:08 PM
          I have narrowed down that this is a driver issue.

          our server team changed the driver to two printers to a PCL driver. It fixed their windows issue, but has messed up our lawson printing to those printers.

          So since it fixed their windows issue, our server team is like oh well....Now its a lawson issue.

          Its not really, lawson just obviously does not like this new PCL driver they have used.
          troelofs
          Advanced Member
          Posts: 19
          Advanced Member
          7/29/2015 1:23 PM

            Ronnie,

            When the server team switched the print driver, did they change the printer share name on the network? If so, confirm that your printer definition in prtdef is pointing at the correct printer share name?

             

             

             

            Ronnie
            Veteran Member
            Posts: 152
            Veteran Member
            7/29/2015 1:26 PM
              fixed the issue.

              I logged into our app server. Added those printers to the server (for windows) so that it pulls the updated driver, and tried again and now all is back to normal. the laprint command works fine now and is no longer hanging.