27.04.2013 Views

SAP Basis

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

ADM100 Lesson: Appendix - Troubleshooting Example<br />

Task 3 Example 1: <strong>SAP</strong>LPD<br />

<strong>SAP</strong>LPD could not be started.<br />

1. Start the program ZPRINTERROR in your <strong>SAP</strong> system.<br />

a) Start transaction SA38 and enter the program ZPRINTERROR.<br />

Choose F8 to Execute.<br />

2. Performanotherfrontendprintwithimmediateoutput. Printthe<br />

output of transaction SM51.<br />

a) This time, <strong>SAP</strong>LPD should not be started, and no print output<br />

should be produced.<br />

The procedure corresponds to task 2.2.. The solution is described<br />

there in detail.<br />

3. Analyze the error. To do this, compare the trace information and<br />

the information from transaction SP01 with the information for the<br />

successful front end print from the previous task.<br />

a) The report ZPRINTERROR entered in the <strong>SAP</strong> system that the<br />

system should look for <strong>SAP</strong>LPD in the directory under<br />

the <strong>SAP</strong>gui directory. That is, <strong>SAP</strong>LPD is not found.<br />

The procedure corresponds to tasks 2.3 to 2.6. The solution is<br />

described there in detail. The only difference is that you find the<br />

following entry in lprintg.log:<br />

TCP_START called<br />

Trying to start \<strong>SAP</strong>LPD.EXE -I<br />

Trying to start \<strong>SAP</strong>LPD.EXE -I -r51x<br />

Setting lock for <strong>SAP</strong>LPD<br />

Releasing lock<br />

TCP_START finished<br />

(x=6 for the DEV system (=DEV), x=7 for the QAS system<br />

(=QAS)). The system is therefore searching for <strong>SAP</strong>LPD<br />

in a directory in which it does not exist.<br />

Continued on next page<br />

2003/Q3 © 2003 <strong>SAP</strong> AG. All rights reserved. 577

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!