SAP OSS Note 16534 version 0017 contains details of a know issue related to Job terminates due to SPOOL_INTERNAL_ERROR
. This includes any associated symptoms and instructions on how to fix it, see below for full details. Also check out the comments section to view/add related contributions, questions or screen shots, based on real life experience of this oss note and problem.
...For more information about the SAP support system known as OSS please check out the SAP OSS NOTES SECTION, whih includes how to download & implement them onto your SAP system using transaction code SNOTE.
Batch job terminates due to errors in the spooler
SysLog F82: Invalid writer count
No handle for an open TemSe object
Some error in TemSe management
Runtime error "SPOOL_INTERNAL_ERROR" occurred
Transaction termination 00671
Cause of the problem and Pre-requisites
Spooler consistency check RSPO0043 or RSPO1043 is used in the productive
system with a "lock-delete duration" that is too low.
The problem can arise both during online checks in the SPAD and in the
To date, there has been no other definitive cause.
Important: RSPO0043 is obsolete. Use only RSPO1043 for the spooler TemSe
The spooler consistency check RSPO1043 deletes the write locks on spool
requests that are older than a certain duration. This duration
(the "age" of the write locks) is specified as the parameter
"Release locks after... minutes".
The standard value for RSPO1043 is 10080 minutes, that is, seven days.
The problem cannot occur with this standard value since there a
re normally no batch jobs that have a runtime up to seven days.
(Although RSPO0043 has a standard value of thirty minutes, it should no
longer be used, see above.)
Select the parameter "Release locks after... minutes" so that it is
large enough so that no write locks of spool requests of current b
atch jobs are affected during the daily execution of RSPO1043.
(The corrections specified in this note set 10080 as the default for
write locks in RSPO0043.)
Spool, RSPO0043, RSPO1043