Solution : https://service.sap.com/sap/support/notes/946209 (SAP Service marketplace login required)
Summary :
Problems with SAPSprint printing are addressed in this note by suggesting the use of updated SAPSprint versions and troubleshooting techniques including tracing and logging. Initially, SAPSprint was used alongside SAPLPD for printing from Windows front-end and server environments. However, SAPLPD is now redundant with new methods recommended. SAPWIN.DDL is pivotal in both SAPSprint and SAPFprint environments. Users are guided to trace SAPSprint issues rigorously by adjusting the log level, maintaining data stream files, and setting conditions for automatic restart after errors. It's important to keep SAPSprint updated, using patches from specified SAP Notes. The note provides a structured approach to resolve print problems by capturing detailed logs, adjusting file retention policies, and continuity measures.
Key words :
sapwin_<sid><spool-id>_<output request number>, <sid><spool-id>_<output request number>, trap tcp/ip packages larger, error categories communication problems communication problems, job specific trace file logs errors, network guarantees stable data transfer, job-specific log files remain, command 'sapsprint -oi lpdport n', command 'sapsprint oi maxlogfilesize n', relevant spool work process
Related Notes :
| 1069483 | Error occured in CreateDCW |
| 927074 | Patches for SAPSprint |
| 894444 | Tool for server-based printing on Windows (SAPSprint) |
| 85469 | Options for the SAPSprint print server tool |