Scribd
Upload
70 views

2233302 - Network Problems Printing to Remote Print Server

Uploaded by

stephane.srong
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
70 views

2233302 - Network Problems Printing to Remote Print Server

Uploaded by

stephane.srong
Copyright
© © All Rights Reserved
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 2

SAP Knowledge Base Article

2233302 - Network Problems Printing to Remote Print Server


Component: BC-CCM-PRN (Basis Components > Computer Center Management System (CCMS) > Print and
Output Management), Version: 13, Released On: 23.04.2024

Symptom
Printing from SAP to a remote print server is not working. There are network related errors reported, such as:
1. In the SAP spool log:
Unable to establish connection to Berkeley LPD
3 connection attempts terminated with network errors
Unable to connect to output processor
Request postponed x times
Host <xxx> cannot be reached or (SAP-)LPD is not running there
The host spool is reporting errors
2. In the SM21 system log:
Connection to SAPLPD Broken
Connection to SAPLPD or LPD Broken; Computer <print server>
Unable to Establish Connection to SAPLPD or lpd
3. In the spool work process trace file:
S *** ERROR => Cannot read from connection (read timeout) [rspoclpd.c 546]
S {root-id=005056AE34D31ED59DE5D9AAE60F21E8}_{conn-
id=00000000000000000000000000000000}_0
S S#: (2015102008320400) xxxx: Cannot connect to lpd. Job delayed.
S *** ERROR => Lost connection to lpd [rspoclpd.c 565
4. In the spool event log:
Error Data transfer Could not pass request to host spool system
(SAP)LPD cannot accept request (Queue <printer> disabled?)
5. Via SPAD
'Unable to reach the remote host spool system' is reported from SPAD remote system check.

Cause
Local issues external to SAP. For example:
Network issues (most common cause).
Individual printers offline or not responsding.
Firewall setting or other settings blocking the connection.
Using a single overloaded print server with too many printers installed (eg. 1,000 printers on one print server).
For problems with individual printers like the error "(SAP)LPD cannot accept request (Queue <printer> disabled?)" in
point 4 above, the printer needs to be installed and available on Windows OS level. Printouts to the printer must be
working directly from Windows before they can work from SAP.
For SAPSprint there may be some configuration issue as outlined in Resolution point 4 below.
Printing directly to the printer (i.e. not through a print server / host spooler).

Resolution
1. These types of network related problems are generally external to SAP and need to be resolved locally. Please work with
your network administrator to check why the connection to the remote print server or printer is reporting problems and
resolve the issue locally.
2. From the SAP side there are the following general network connection analysis and troubleshooting notes which can
assist in this process:
10758 - SAPSprint or SAPLPD cannot be reached. What should be done?
500235 - Network Diagnosis with NIPING
26086 - TCP/IP Connection to partner broken
3. If you are printing with access method U directly to a network printer (i.e. not through a print server), this is not
recommended or supported as described in note 64628. The printer tries to simulate a print server but it is not able to
buffer enough incoming requests when the volume is high or with very large spool requests. Printing directly to the
printer may result in spool errors and long delays in printing. It may also result in some spools, or some pages from
spools, not being printed. Refer to note 64628:
64628 - Using network printers from R/3
4. For SAPSprint:
i. There are additional trace files available which can help further with analysing the problem. These trace files are
described in KBA 1780925:
1780925 - Collect SAPSprint windows log file
ii. Check and ensure the problem is not related to the default SAPSprint port 515 as described in KBA 2141173:
2141173 - Problems printing to SAPSprint default port 515
iii. It is generally recommended to always use the latest release and patch version available:
894444 - Tool for server-based printing on Microsoft Windows (SAPSprint)
iv. Ensure you have installed SAPSprint correctly as described in note 894444 and in the online documentation. In
particular ensure that the service runs with the correct user. Note 894444 extract:
"...The service should run using an administrator or domain user that has the relevant authorizations for the
required printers..."
894444 - Tool for server-based printing on Microsoft Windows (SAPSprint)
Help Portal - SAPSprint Service
v. Ensure you have not selected the 'Save output as file' option in the SAPSprint Processing tab of the SAPSprint
Options Editor. If this option is set, print output will be redirected into a file instead of being printed. The default
is always 0 so for this to be a problem it would have to have been set manually. You would also see this in
the sapsprint.dbg file as "SaveAsFile = 1" if it has been set.
5. Refer to note 2326576 for reactivating print jobs that failed due to connection problems:
2326576 - Delayed print jobs do not print after connection problem to PrintServer

Keywords
Spool, Error log, (SAP)LPD, Cannot, Network, Printing, Problem, Queue, Disabled, Unable to establish connection to
Berkeley LPD, Connection attempts terminated with network errors, Unable to connect to output processor, Request
postponed, Host cannot be reached or (SAP-)LPD is not running there, The host spool is reporting errors, Connection to
SAPLPD Broken, Connection to SAPLPD or LPD Broken, Unable to Establish Connection to SAPLPD or lpd, ERROR =>
Cannot read from connection (read timeout) [rspoclpd.c 546], ERROR => Lost connection to lpd [rspoclpd.c 565], SAP)LPD
cannot accept request (Queue disabled?), Unable to reach the remote host spool system, Remote Printing, Access Method U,
SP01, SPAD, SAPSprint

Products
Products

SAP NetWeaver all versions

This document refers to


SAP Note/KBA Component Title

2141173 BC-CCM-PRN Problems printing to SAPSprint default port 515

1780925 BC-CCM-PRN Collect SAPSprint windows log files

927074 BC-CCM-PRN Patches for SAPSprint

894444 BC-CCM-PRN Tool for server-based printing on Microsoft Windows (SAPSprint)

64628 BC-CCM-PRN-SPO Use of network printers from R/3

500235 BC-NET Network Diagnosis with NIPING

26086 BC-NET TCP/IP Connection to partner broken

2326576 BC-CCM-PRN Delayed print jobs do not print after connection problem to PrintServer

10758 BC-CCM-PRN-SPO SAPSprint cannot be reached. What can be done?

SAPSprint Service

This document is referenced by


SAP Note/KBA Component Title

2597749 Spool status "Waiting in host spooler"

You might also like