SPOOL INTERNAL ERROR is very common in SAP landscape. whenever spool reaches to their limit so it’s start failing the jobs & prints & due to this everything get stopped in SAP system.

SAP is having a default limit of 32000 spool in SAP system as per SAP Note 48284.

You need to check the limit by logging into 000 client – SNRO – Object – SPO_NUM & check interval.

if there is an heavy usage of SPOOL in your organization. you can use 2 things to resolve the issue.

1. Schedule daily cleanup job (RSPO1041) in the system with variant value less then 7 days.
2. Increase the limit of spool count from 32000 to 60000.

if you system is having this issue & you are not able to run the report in background, then delete the old spool in DIALOG mode for temporary cleanup via SPAD. once it’s clean then you can schedule the job again with change variant.

SAP Spool Issues


Question: In SP01 what is the difference between print directly & print with changed parameters?

1)     The setting that uses spool with “Print directly to the printer.” You might choose this setting if you have a lot of jobs waiting in the spool and want to print something else in a hurry, and is defined for the user-id
For Print a Spool Request with changing its Parameters.
To change the request before printing it, for example, to send the request to a different printer or change the number of copies to print, choose Print with changed parameters. You can change the following settings before printing:
a) Output Device: If possible, only send the output to an output device that uses the same device type as the output device for which the request was originally created. The device type indicates the printer type used, such as PCL.
b) Start Time: To set a later time for printing, choose this button

Question: If a spool request is in waiting status for a long time, what does it mean?

2)     Status Waiting may also indicate that there is a problem with the spool work process that is assigned to a printer. Check the following:

a) Find out which printer an output request has been sent to. To do this, select the relevant spool request in the Output Controller and choose. You can find the printer name in the Output device field.

b) Find out which spool work process is responsible for the printer. Enter the name of the printer to which the output request was sent in the Output Device field on the Devices/serverstab and choose enter. Display the definition and note the SAP application server name that appears in the Print server field. If you have only a single spool server in your SAP system, then you can omit this step.

c) Use the CCMS System Monitor or in transaction SM51 to display the application servers in your SAP system. Check that the application server that you noted from the Print server field is running and that the server offers the service Spool. If the server is not running or if the Spool service is not active, then you have found the source of the problem.

d) If the print server is running and the spool service is active, then check the activity in the spool work process.

In transaction SM51, mark the print server in question and click on Processes. In the process display, look for the spool work process and note the name of the active user. If User SAPSYS is active, this indicates that the spool work process is busy with internal spool activities or is requesting the status of a print request from a host spool system. Choose CPU repeatedly to check the CPU time that the spool work process requires. If the same CPU time is always displayed, then it is likely that the spool work process is waiting for a status query to time out. It is likely that you have to then find the reason for the delay in output request processing.

Question: If a user wants to reprint his document again what should to do ?

3)  The user needs to give the spool request number in sp01 and then print it or Users should have Tx SP02 for their own spool requests (not SP01 which is a BASIS Tx). User can browse & reissue an output request for a particular spool (unless they deleted it, or it time expired and got reorg’d).

Question: What I have done to use users OS level printer as SAP printer. I mean if a user has given a print if SAP couldn’t able to find printer it will be in error status. In this case I want to reprint that document from users OS level default printer.

4) There are two things for this:
a) You have to define the local printer same as for your OS in SAP and maintain that as local in spad.
b) The user needs to give the spool request number in sp01 and then print it going forward.


You could configure a front-end printer (host spool method G) in SPAD. Printer name is generally LOCL. Understand now that you will have more problems by introducing front-end printing, and not fewer. Users will become accustomed to using it and will insist you fix it when some desktop patch or network change breaks it. I know it SEEMs like a good idea; remember I tried to warn you. Host spool method M is a more easily supported alternative (print-to-email and they can use the resulting attachment as they like).

Question: What are the regular spool problems and resolutions?

5) Many and varied. Users do not typically distinguish between ‘spool problems’ and ‘printing problems’. Make sure the housekeeping jobs run:

Question: In my project I had faced a prob in SOLMAN. The system was giving short dump “SPOOL_INTERNAL_ERROR” and while checking it, system was issuing message “SPOOL OVERFLOW”.

6) As the solution I applied resolution provided in SNote no. 48284, which asked me to raise the upper limit for spool requests using TC=SNRO. The complete procedure is:

1. Log on to the system in client 000 and call transaction SNRO.

2. Select the object SPO_NUM and choose the button: Number ranges.

3. On the next screen, choose: Change Intervals.

4. In the “To number” column, change the upper limit of interval 01 to 999,999, for example.

Question: Sometime printing is working perfectly & then suddenly all printing get stop. We have seen in SAP spool error log is:

“Unable to open file /usr/sap/<SID>/DVEBMGS40/data/009v1WwD.<SID> for writing (error 28)

Errors occurred processing this print request

There may be no printout”.

 After restarting it works fine for some time but again printing got stuck.

7) There are 2 things for this:

a) Do TemSe reorganization; remove inconsistencies & Restart SPO processes in SM50.

b) Error in UNIX Index Nodes (Inode stores basic information about a regular file, directory, or other file system object.)

We were facing out of index nodes issue. The directory where all the batch logs were getting accumulated had run out of number of files it could accommodate even though space was available. When we moved the batch logs to another directory issue was resolved.


More will come soon.