Solution : https://service.sap.com/sap/support/notes/894444 (SAP Service marketplace login required)
Summary :
This SAP Note addresses the instability issues of using SAPLPD as a print server, particularly post Windows 2000 and suggests transitioning to SAPSprint, which functions as a Windows service. SAPSprint can handle 'S' and 'U' access methods without requiring SAP system changes but necessitates replacing SAPLPD on the print server. Installation encompasses manual SAPLPD removal, downloading SAPSprint via SAP Service Marketplace, and configuring the new service, especially setting user permissions for effective printer access. It includes recommendations on setting options for service operation, troubleshooting, and emphasizes utilizing SAPSprint on dedicated servers for robust print management.
Key words :
windows tcp/ip print service, access method 'u' reason, technical details sapsprint consists, windows service control manager, normal windows uninstall tool, access locally-defined printers, option 'sapsprint -oi keepfile 1', print job specific file, calling 'instsrv saplpd remove', sapsprint windows service starts
Related Notes :
| 1545557 | OMS interface for SAPSprint |
| 947514 | Printed output of Thai ABAP lists shifted after kernel patch |
| 946209 | Analyzing SAPSprint problems |
| 927074 | Patches for SAPSprint |
| 821519 | Front-end printing with control technology |
| 213524 | SAPsprint installation in an MSCS environment |
| 85469 | Options for the SAPSprint print server tool |
| 42268 | Operate SAPLPD as a service on Windows NT/2000/XP |
| 16420 | Problems with SAPLPD |
| 12550 | Problems with remotely connected printers (WAN) |