SAP Note 12552 - Request for debugging information for SAPLPD

Symptom:

INFOREQ:
The reported error symptoms are not sufficient for a complete
diagnosis. Please send additional information.

Solution
As described in Note 328252, obtain the most recent SAPLPD (at least 2.53 or 3.04 is required) for the trace output to be meaningful.
If your SAPLPD problem does not result in a crash, call SAPLPD with the option -d ( = 0..9). The file "SAPLPD.DBG" is created
automatically, where all debug information dependent on is
writen. only influences the display in the SAPLPD window. If you are only interested in the file and want to suppress the (slow) output on the screen, use -d0.

If a program exits without warning the last log dates might be missing in the above procedure. In this case, use option -g9 during the start. The option creates the file "SAPLPD_F.LOG". (This method is
considerably slower, since more disc accesses are executed.)


If you have a problem with the 'local print' (not the new front end print via access method 'F') in Transaction SP01 (R/3 Release 3.X), enhance the call parameter in the dialog box for the local print, since SAPLPD is started by R/3 and is not called manually with the paramter.

For front end printing with access method 'F' make sure that SAPLPD was started manually with the correct parameters.
However, if you print via a terminal server, SAPLPD cannot be started manually beforehand. In this case, temporarily add the required option (e.g. -g9) to environment variable LP_CMD). However, this parameter should preceed -P&P (cf. Note 150533).


Immediately produce the error on the respective printer. You can trace the progress in the log window of SAPLPD. When the request ends as "Completed" or "Incorrect" in the R/3 System (SP01) exit the SAPLPD.


Send log to SAP.
You can either print the log on paper for example with WRITE. If you have problems printing the log with WRITE on your local printer, try to correct the problem first, as this could be the same problem that is affecting the SAPLPD.
Please then fax us the log.

Alternatively, you can copy the contents of the file directly into the
'Problem description' section of the SAP Online Software Service or you can store it on the sapservX (Note 40024) per FTP.

Afterwards, delete your local SAPLPD.DBG and SAPLPD_F.LOG files, otherwise the SAPLPD would continue to run in Trace mode.

Reason and Prerequisites

None.

Key word: SAPLPD/info