Page tree
Skip to end of metadata
Go to start of metadata


This Wiki provides an overview of the SAPSprint Service


  • SAPSprint Service 
  • Printing Through SAPSprint 
  • Installing SAPSprint 
  • Setting the SAPSprint Log Level

SAPSprint Service


SAPSprint is a transfer program for print output using a Microsoft Windows operating system. SAPSprint replaces SAPlpd as an implementation of a print server and is required only for remote printing with Microsoft Windows [Extern]. In this case, the host spool system (Microsoft Windows spooler) and the spool system (application server with a spool work process) are on different hosts. That is why the SAP spool system requires an external process that transfers the output requests from the SAP spool server to the Microsoft Windows spooler. This process is provided by the SAPSprint service.


SAPSprint comprises the program sapsprint.exe which contains the implementation of the Windows service and the receiver for print data from the SAP system. The SAPWIN data stream is processed in the sapwin.dll component. The sapwin.dll component is also used by the new front-end printing, as described in SAP Note 821519. SAPWIN processing errors therefore affect both print methods. Patches for SAPSprint and the new front-end printing are available in SAP Notes 927074 and 841175 respectively.



SAPSprint runs as Windows service. In general, you do not have to change the default configuration settings of SAPSprint as Windows service except for one: You should change the local system account to a domain account. For this, open the list of services in your Windows system, right-click on the SAPSprint service, and choose Properties. On the Log On tab, check the option This account and enter a domain user account.


SAPSprint preserves the features of SAPlpd as a transfer program:

      • You can use SAPSprint in all Microsoft Windows systems.
      • Like the line printer daemon lpd, SAPSprint accepts print data and forwards it to the host spooler.
      • SAPSprint also interprets the special SWIN/SAPWIN data stream and converts it to GDI calls for Microsoft Windows. The system then uses the printer drivers that are available for Microsoft Windows and/or the printers. sapwin.dll contains the SAPWIN interpreter.

  • SAPSprint is implemented as a multithreaded Windows service and adds the following features:
      • Error Bypassing
        If an error occurs when printing on a device, this does not prevent printing on other devices defined in the system. In comparison, SAPlpd blocks output to all devices until the error is cleared manually. For more information, see Printing Through SAPSprint [Seite 7]
      • Error autorecovery
        SAPSprint is by default configured to restart automatically after an error and thus is more robust than SAPlpd.
      • Logging and print file retention
        You can configure SAPSprint to log information about print jobs as well as to retain print files after they are printed.
      • Command Line Administration
        SAPSprint does not have a graphical user interface. You can set various configuration options for SAPSprint through a command line. By entering SAPSprint -? in the command line, you can view the most important configuration options. In comparison, SAPlpd was administered by directly accessing the Windows Registry Editor. You find a description of all configuration options in note 85469.

Enhanced Features

To be able to print Interactive Forms (previously also known as PDF-based forms) on a printer with any device type, you can additionally install the component SAPPDFPRINT. SAPPDFPRINT allows you to address any printer when printing Interactive Forms, in a similar way to using SAPWIN-based device types. SAPPDFPRINT requires either a Microsoft Windows print server with SAPSprint or SAP GUI for front-end printing. More information about this is available in the SAPPDFPRINT documentation, which is part of the delivery.

SAP Sprint or SAP GUI must be of the same release as SAPPDFPRINT.

Note that you should install SAPPDFPRINT before SAPSprint or SAP GUI, since SAPSprint or SAP GUI then automatically recognize this component.


Install SAPSprint. For more information, see Installing SAPSprint

Printing Through SAPSprint

SAPSprint as a Service

SAPSprint is a multithreaded Windows service. For every output request to a particular device, SAPSprint opens a new thread.

               The number of threads which SAPSprint can start is limited and depends on the operating system.

If an error occurs while printing on a device, only the thread to this device is affected. If the thread is blocked, it remains blocked until SAPSprint is restarted. As a result, jobs sent only to this device will fail until the service restart. However, you can safely print on another device defined in the system as the figure below shows.


In comparison, SAPlpd has a single process for all output requests. If an error occurs while printing to a device, it prevents output to any other device defined in the system until you restart SAPlpd manually.








Installing SAPSprint


SAPSprint is release-independent and you can update it between releases. You install SAPSprint on the print server.

  • SAPSprint is downloaded and saved locally. The SAPSprint installation is a single executable file ( xSprint.exe ). You can download it from You find detailed download and install instructions in note 894444.
  • The installation host is running Microsoft Windows as the operating system.

  • An implementation of the TCP/IP network protocol that supports WinSockets (the WINSOCK interface).

  • You have write permissions to a directory on the file system.

  • SAPlpd is uninstalled. If SAPlpd is installed, uninstall it by deleting the SAPlpd installation directory.If SAPlpd is installed as a service using the srvany tool, remove the service by executing the following command: Instsrv SAPLPD remove .

  • If you want to print Interactive Forms (previously known as PDF-based forms) using SAPPDFPRINT, you should install this program before SAPSprint or SAP GUI, since SAPSprint or SAP GUI will then automatically recognize SAPPDFPRINT. More information about this is available in the SAPPDFPRINT documentation, which is part of the delivery.




1. Run the xSprint.exe .

2. When prompted, specify the following:

       a. SAPSprint installation directory

       b. LPD port

            The value determines the TCP/IP port that SAPSprint waits on. Port 515  is the standard port for printing using the S and U access method. Leave the default value 515 . Change the port number only if the Windows TCP/IP print service is also running on the installation host.

       c. LPD log path

           Specifies the path to the log directory. The log directory contains log files and print jobs files. You can configure log files and print job files to be preserved or deleted by setting SAPSprint log level [Seite 9] after the installation.

Related Documents (Size: Heading 2)

Insert SAP Help links or other WIKI content link.
Please hyperlink the title of the related document

Related SAP Notes/KBAs (Size: Heading 2)

Insert links to any related SAP Notes/KBAs that support your topic or are related. Please hyperlink ONLY SAP Note or KBA number.

  • No labels