Skip to Content
Author's profile photo Yogesh Patel

SAPSPrint Install

This document details how to install SAPSPrint on select Print Servers to allow for printing from various SAP applications.

SAP applications have specific requirements to map internally created queues to Windows print queues, and the SAPSPrint service allows this functionality.

Install Steps

Perform the following on print servers.

Launch xSPrint_8-10008892.exe

Note: To download this file

SAP Software Download Center >>Support Packages and Patches  >> Search for Support Packages and Patches : Search for SAPSPRINT


Click Next


Select Installation path and press Next


Provide port number


NOTE: If the LPD Service is installed  under Print Management (Windows TCP/IP Printing), that service defaults to 515.   The SAPSPrint port will need to be changed in that scenario.



NOTE: This starts immediately after install.   Local System gives SAPSPrint access only to locally defined printers.   If there is a requirement to have access to machines not defined on the print server (eg. Remote network, printers locally connected to client, etc) then this service will need to start under a domain account.

I would also like to add that there are also command line options that you can leverage to make the install easier/faster if you are required to install these on numerous print servers in your Windows environment.  I have used the /noDLG option and the entire install is just a progress bar.


Assigned Tags

      You must be Logged on to comment or reply to a post.
      Author's profile photo Former Member
      Former Member

      Dear Yogesh,

      Do you have any guidelines for sizing the SAPSprint server?


      Susanto Sarkar

      Author's profile photo Yogesh Patel
      Yogesh Patel
      Blog Post Author

      As far I know you can install this as windows service and not required and extra processing power for server.

      Author's profile photo Billy Warring
      Billy Warring

      Added the command line options screenshot.

      Thank you for the open collaboration Yogesh!

      Author's profile photo Former Member
      Former Member


      Thanks for this procedure.

      Do you know if on a windows 64-bits there is any specificity?



      Author's profile photo Billy Warring
      Billy Warring

      I believe it installs 32 bit, like SAP GUI; in my environment it has run on 64 bit Windows 2008 R2 systems without issues for a few years.

      Author's profile photo Former Member
      Former Member

      Does anyone have any documentation on the suitability of SAPSprint for volume printing? Is there a Best Practise guide for Output Management? We have previously been advised not to use SAPLPD for volume prints. I wonder if the same guidelines exist for SAPSprint?

      Author's profile photo Billy Warring
      Billy Warring

      I have never noticed issues with SAPSprint for any document types in my environment.

      Author's profile photo Alexander Bolloni
      Alexander Bolloni

      Hello Patrick,

      SAPlpd was indeed very unstable and not suited for mass printing (=print server operations). SAPSprint is a complete re-implementation of SAP (Windows) print service, much more robust and streamlined.

      See note 894444. I am sure many customers are using SAPSprint for print-server style output of SAP print documents, not only for SAPWIN/SWINCF device types.



      Author's profile photo Former Member
      Former Member

      Hello Expert,

      we are using SAPLPD for local printing by windows system, We want to switch to SapSPrint, What we have to do after installing on Print server SapSPrint, We have Unix Based installation of SAP, Printer server is Windows based, all other clients are windows based using windows 8 & 10. My question is what would I have to do after Installing SapSPrint on Windows Print Server and Remove saplpd on all windows client. should I have to to other settings or configurations on SAP Server.



      Author's profile photo Alexander Bolloni
      Alexander Bolloni


      SAPlpd was only necessary on client PCs when frontend printing was done via access method F, which is long obsolete!

      Please always define your frontend printers using access method G, this does not require SAPlpd on client PC, everything necessary is already built into SAPgui for Windows. Once this is in place, remove SAPlpd from client PCs.

      Note that SAPSPrint is not needed at all in frontend printing. It is purely for print servers. This is a common misconception which exists because for SAPlpd, the same tool (=SAPlpd) was required for local and server-based printing. This has changed with the advent of acc method G and SAPSprint.



      Author's profile photo Deepen Shah
      Deepen Shah


      I have an issue with 1 of our shipping printer frequently with printing delay or error. we don't have print server yet. we print directly to network printers using IP. I would like to know if we have 2 printer server by installing SAP Sprint on them, how do I configure printer in SAP? How do I achieve High Availability? Do I need to configure all SAP printers in print server? if not, how do I configure them in SAP to use print server?

      Thanks in advance

      Author's profile photo Billy Warring
      Billy Warring

      If you can avoid using IP addresses in SPAD to point to a print server you should; also my company has also done some brainstorming on how to best setup a HA print server and couldn't find a solution.

      However since SPAD points at a DNS CNAME record there is no change that we have to perform for the printer; if a printer server dies or you have an issue then it's just a matter of updating DNS records (other some other backend print server things).

      If you would like a more in depth details to all of your questions, I recommend opening a discussion within Output Management so others can perhaps provide their solutions.  Feel free to tag me within it if you want.

      Author's profile photo Vinh Tran
      Vinh Tran

      Dear Yogesh Patel,


      Thank you very much for your article.

      I see your NOTE that "If the LPD Service is installed under Print Management (Windows TCP/IP Printing), that service defaults to 515. The SAPSPrint port will need to be changed in that scenario."

      In this case if I changed SAPSPrint port (for example: to 555), should I need to modify any setting in SAP or anywhere to adapt this new SAPSPrint port?

      Could you kindly guide me how to change if any please?


      Thanks for your supporting!


      Author's profile photo Alex Jesu
      Alex Jesu

      Hi Vinh,


      if SAPSprint configured with diff port (like 555).

      you have to update print port number in printer setting.

      Open the printer in SPAD.

      Goto access Method --> destination host -->Click on connection option.

      mention the Port number (555) and save.

      Now print request will us port 555 to communicate


      Author's profile photo Muktha Patel
      Muktha Patel

      Does SAPSprint work on Windows Server 2019 ? are there any know issues ?