cancel
Showing results for 
Search instead for 
Did you mean: 

spool_internal_error

Former Member
0 Kudos

Hello guys

i am getting following error in st22 i.e spool_internal_error.

error analysis mentiod .

Error analysis

When calling the SAP spool system, an (unspecified) internal

error occurred.

More detailed description of error: "spool overflow "

Further information:

See below under "Spool error information".

How to correct the error

Probably the only way to eliminate the error is to correct the program.

-

You may able to find an interim solution to the problem

in the SAP note system. If you have access to the note system yourself,

use the following search criteria:

-


"SPOOL_INTERNAL_ERROR" C

"ZDPS_CHKPROT" or "ZDPS_CHKPROT"

"START-OF-SELECTION"

-


Kindly assist it that how to proceed further .

Accepted Solutions (0)

Answers (6)

Answers (6)

Former Member
0 Kudos

This message was moderated.

JPReyes
Active Contributor
0 Kudos

Are your REORG jobs working?...

There should be no need to increase the number range if the jobs are scheduled

Read,

Note 16083 - Standard jobs, reorganization jobs

@Anil,

RSPO0041 is obsolte now, you should use RSPO1041

Note 130978 - RSPO1041 - Replacement for RSPO0041

Regards

Juan

Former Member
0 Kudos

Sounds like Temse,,, Also before changing any number ranges, do a consistency check in Tcode SPAD.

Former Member
0 Kudos

Hello Guys ,

Let me knw step by step to increase the number range ???

Former Member
0 Kudos

This message was moderated.

Former Member
0 Kudos

Proceed as follows:

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

2. In the "To No." column, change the upper limit of the interval SPO_NUM to 999,99

Former Member
0 Kudos

Raj,

generally the spool number range would be 32K. if your spool count goes beyond that you could get this error.

Try to increase the number range .

even the spool cleanup job will fail as this will try to create spool in the system which is already overflowing. the best option would be to manually delete few old spools and schedule the job again.

Former Member
0 Kudos

Hi,

As regarding with the spool you menctioned you have to go through some checks.

normally we do find spool dumps occuring in some durations (timings) for this

1) first go to sm13 i.e. up date stats and check whether there are any update failures and check the cause for the failure

if the cause is due to spool you have to go to the next step.

2) go to sp01 and remove your name which is appering and insted of your name give * and execute and there might be more spool requests.

3) here you have to select the previous days of spool requests and delete all the spools before dooing this you normally take the priour approval from your seniour consultant.

4) after this go to sp12 and run the tmese consistency check and delete the apprioriate entries only like here you are deleting from TST01 and TST03 tables.

5) normally you schedule the default background SPOOL jobs at the interval of 10 min as pre to your business.

TIP:- if you do not have authorization for spad in production you can go to sp11 and from here you can toogle every corner regarding to spool.

Have a good time.

With Regards,

Prashanth

former_member227283
Active Contributor
0 Kudos

Hi,

Check whether the Background job:SAP_REORG_SPOOL, has been scheduled on regular basis or not.

For overcoming the current problem, run the report RSPO0041 with client no as *.

Also set the number range of SPO_NUM from 32000 to 999999 in client 000 and your productive client.

Thanks

Anil