Issues during label printing

[Former Member]

Hi folks,

I am facing issues related to label printing. We have recently migrated the print servers from Windows 2003 32 bit to Windows 2012 64 bit and we have made changes in SPAD to point it to the new print queues. We had normal HP printers and also Zebra Label Printer. When we test printing some prints are getting completed but few fail with the reason "Incorrect (Failed to connect to LPD)".

These are the errors which i get in the logs.

      SAP spool error log

      =====================

Print request processing log

The operating system is reporting problems

Host 192.168.187.201 cannot be reached or (SAP-)LPD is not running there

The host spool is reporting errors

Unable to establish connection to Berkeley LPD

3 connection attempts terminated with network errors.

For more information, look in the system log or developer trace

Errors occurred processing this print request

Error during print request output. l_rc = 2

There may be no printout.

Even the prints which are successful are also having the messages in the log as below but gets printed.

      SAP spool error log

      =====================

Print request processing log

The operating system is reporting problems

Host 192.168.187.201 cannot be reached or (SAP-)LPD is not running there

The host spool is reporting errors

Unable to connect to output processor

We are using Berkerley protocol U in SPAD. As this is affecting Production printing i have reverted to the old print server. Is there anything which i am missing here to check. Please could you provide some suggestions which you might have come across. I have seen various threads and it points to using SAPSprint instead of SAPLPD but the fact is when i revert it to the older print server it works fine.

Thanks in advance for your valuable suggestions.

Rajesh Mohan

[hemanth2 · Accepted solution]

Hi Rajesh ,

Hope you are doing good.
Do ensure that your output devices in SPAD that print through the Windows print server are still setup correctly.  Check for the printer in the access method tab that 'Host printer' is correctly set to the printer name as it is on the Windows print server and that 'Destination host' is correctly set to the Windows print server.  Please check the note 10758 for this, and also please check note

946209 section "General notes about communication problems".

  # 10758  - SAPSprint or SAPLPD cannot be reached. What should be done?

  # 946209 - Analyzing SAPSprint problems

If the issue persists, set the SAPSprint trace level as it is shown in the note 1780925:

   # 1780925 - Collect SAPSprint windows log files
This log will have more details.

Thank you and have a nice day :).

_____________

Kind Regards,

Hemanth
SAP AGS

[Former Member · Accepted solution]

Hi Hemanth,

I checked the notes which you had mentioned already but in vain. Also i have checked the connection between SAP and the print server. The problem happens only when a mass printing is given where few prints are lost due to connection getting broken. Is there any parameter or any printer setting which maintains number of connections at a particular time.

Thanks and Regards,

Rajesh Mohan

[Former Member · Accepted solution]

Hi Hemant,

I have solved this issue. All i did was i have maintained the IP Address of the windows print server instead of maintaining the IP Address of the print queue. When they started giving the prints of huge volume then the SAPLPD connection didnt get broken and worked like a charm.

Thanks for your support. I am closing this thread and marking it as answered.

[former_member182657]

Hi Rajesh,

Could you check once with Acces method F & G and share the results.

Regards,

Gaurav

[Former Member]

Hi Gaurav,

We wont be able to use these two methods since print queues are maintained in another server so it has to be accessed by the Berkerley protocol. The same works fine when i switch to the old print server (Windows 2003).

Thanks and Regards,

Rajesh Mohan

[former_member182657]

Hi Mohan,

Could you please share the result by choosing check connection for the printer with tranx code SPAD.I also suggest you for SCN link SAP Printing Issue - LPD Response Format Invalid | SCN

Regards,

Gaurav

[Former Member]

Hi Gaurav,

I checked the connection through SPAD it says "Remote host spool system available". Also i tried the commands telnet to check if the port is open.

a)Below mentioned is the print server ip.

telnet 192.168.187.31 515

Trying...

Connected to 192.168.187.31.

Escape character is '^]'.

b)Below mentioned is the printer ip

telnet 192.168.187.201 515

Trying...

Connected to 192.168.187.201.

Escape character is '^]'.

c) Here we can see in the first row that the connection has been established on port 515 from my SAP server to the printer.

netstat -an | grep 515

tcp4       0      0  *.515                  *.*                    LISTEN

tcp        0      0  192.168.3.71.41523     192.168.187.201.515    ESTABLISHED

tcp4       0      0  192.168.3.71.3232      192.168.140.40.51588   ESTABLISHED

tcp4       0      0  192.168.3.71.3232      192.168.140.199.51594  ESTABLISHED

tcp4       0      0  192.168.3.71.1527      192.168.3.71.42515     ESTABLISHED

tcp4       0      0  192.168.3.71.42515     192.168.3.71.1527      ESTABLISHED

tcp4       0      0  192.168.3.71.41653     193.42.50.114.515      TIME_WAIT

tcp4       0      0  192.168.3.71.41654     193.42.50.114.515      TIME_WAIT

tcp4       0      0  192.168.3.71.41655     193.42.50.114.515      TIME_WAIT

tcp4       0      0  192.168.3.71.41656     193.42.50.114.515      TIME_WAIT

tcp4       0      0  192.168.3.71.41662     193.42.50.114.515      ESTABLISHED

[former_member188883]

Hi Rajesh,

Can you start the SAPLPD program and minimize the program.

Post this check the printing results.

Regards,

Deepak Kori

[Former Member]

Hi Deepak,

The printing are actually performed by the users so it wont be possible to get the relevant logs but i would be able to provide the logs from SP01 when a print is made. Let me know if this will suffice.

I have also noted some errors in the Spool trace files but dont know if that might help here.

Thanks and Regards,

Rajesh Mohan