After upgrade of SAPGUI to e.g. SAPGUI 740 patch 12, Frontend print no longer works. The spool has status "Compl." but there is no print at the printer. In the log files from the Frontend PC which can be obtained by the steps described in KBA 1780896, the following errors may be seen:
- A garbled print file name with no printout . e.g. an error entry like: Printfile D:\Users\<user name>\AppData\Local\SAP\SAP GUI\tmp\@øš+ not found.
- A print file name with just a # character as the name. Here the print may or may not occur. Even if the print does occur it could have wrong content by using a different print file with the generic "#" name.with printout. In this case, there is an entry like "Print SAPWIN file C:\Users\<user name>\AppData\Local\SAP\SAP GUI\tmp\#" in the log file
- The log file can be missing part of the name and just have a name like "sapwin_.log". Normally the log file name is sapwin_xxxxxxxxxx.log where xxxxxxxxxx is the generated name based on the params value containing <System ID><Spool number><Output number>(see the Cause section for more details).
KBA , BC-CCM-PRN-PC , Printer Control via Frontend PC , BC-FES-GUI , SAP GUI for Windows , Problem
About this pageThis is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).
Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.