Print Error: Internal Error

Some popular errors and the reasons for those errors:

Internal Error (-6723) occured
This error occurs if fields from the system layout are deleted while creating the custom template. Create the custom template without deleting the system layout fields. If the fields are not required, they may be marked as hidden fields.

Internal error (-4007) occured
If this error occurs when printing  more than one copy from the printer window, press on print preview and then print the report.

Internal error (-101) occurred
Internal error is misleading here. This error occurs if the printer/print driver is wrong/missing/corrupted. Install a correct printer and/or driver. It could also be because of insufficient authorization in case you are printing from a workstation/citrix.

Internal Error (-50) occured
If you are trying to print to the local workstation as a pdf file or any other format, ensure that the destination folder has write permission on your user ID/group.

Internal error (1) occurred
If you are trying to print/preview a draft, instead of double-clicking on the document, highlight the document and then print/preview

Clean up of old repositories from SDM

When you deploy patched or support packs , all the previous versions are retained as a backup under SDM repositories. If you wish to clean them up, for example to Gain disk space, you can follow these steps from program directory

./StopServer.sh
./sdm.sh jstartup mode=standalone
./sdm.sh gc sdmhome=/usr/sap/SID/inst#/SDM/program
./sdm.sh jstartup mode=integrated
./StartServer.sh

Work Processes held by the program SAPLSENA

The program SAPLSENA is the lock handler that takes care of locking and unlocking operations in an SAP system.

If a process is held by SAPLSENA for a long duration, it means that an application program is making a large number of lock requests. A large number of work processes are occupied because the DEQUEUE function module is called separately for each request.

You can analyse the lock situation by following the steps provided in the SAP note 653996.

You may have to run the application program ( by controlling selection criteria) to limit the number of lock requests. Alternately you can adjust the enqueue parameters (enqueue/tablesize, enqueue/snapshot_pck_size, enqueue/snapshot_pck_ids etc.).

Changing redo log files location or size online

You may want to change the redo log file size or it's location online (in case you are facing space issues on the existing disk drive).

Before changing the redo logs, take a full backup.

Drop the first redo log by using the SQL command
alter database drop logfile '<path to the redo log file>';

Now create it with your preferred location or size using the command
alter database add logfile '<preferred path and name of the log file>' size <preferred size>M;

Repeat this on the rest of the redo logs. You will encounter ORA1515 error at the point when you are deleting a redo log file that is currently in use. You can wait or skip the redo log file for now and proceed later with this redo log file. You may also force log switch to let you change the current log file using the command
alter system switch logfile;

Execution of SLIC_LIKEY_CHECK aborted with rc 2

If a check of maintenance certificates fails with the following error:
Execution of SLIC_LIKEY_CHECK aborted with rc 2

Increase the value of the parameter slic/buffer_entries_dig_sig to 15 (or higher if it is already set to the benchmark value as per SAP note 1280664)