topic Re: Runtime Error:- SPOOL_TEMSE_ERROR in Application Development and Automation Discussions

Runtime Error:- SPOOL_TEMSE_ERROR

Former Member — Thu, 29 Oct 2009 06:55:03 GMT

i am facing a production issue.

A job is getting cancelled. In the ST22 dump analysis i find a unique error.seems it has somthing related to SAP-Basis, but not sure.

The Dump analysis says :- Error in TemSe system.

-->The current ABAP program had to be terminated because the

ABAP processor detected an internal system error.The current ABAP program "YRDSDV2_LO1487_LIEFERUNG" had to be terminated because the ABAP processor discovered an invalid system state.

i went to the source code but the code lines were already commented, so might not be happenning due to the program code.

further information shows:-

While processing in the SAP spool system, an unspecified error occurred when calling the TemSe system.

More detailed description of error: "Error from TemSe "

FYI its a background job.

Application Information:- The termination occurred in the function "lprint" of the SAP

Basis System, specifically in line 2153 of the module "//bas/640_REL/src/krn/runt/abprint.c#57".

The internal operation just processed is "----".

The internal session was started at 20091028150309.

Can anybody please throw any light on this.

thanks in advance.

Re: Runtime Error:- SPOOL_TEMSE_ERROR

RaymondGiuseppi — Thu, 29 Oct 2009 07:08:13 GMT

Try to find an OSS note like [Note 11733 - WRITE or(!) ROLLBACK WORK|https://service.sap.com/sap/support/notes/11733]. Also check if you are using a LOCL printer in a background job or this kind of error.

Regards,

Raymond

Re: Runtime Error:- SPOOL_TEMSE_ERROR

Former Member — Thu, 29 Oct 2009 07:09:52 GMT

Hi Raymond,

thanks for the reply. can you kindly let me know if there is any acton required from my side. i am an abap consulatant, or else ill transfer the issue to the secutiry team.

Re: Runtime Error:- SPOOL_TEMSE_ERROR

RaymondGiuseppi — Thu, 29 Oct 2009 07:28:17 GMT

you may try to execute report in foreground or with another printer to precise the most likely cause of failure.

You may also find more precision on error via transaction SM21 selecting date/time of the dump on the same application server.

If you dont find a solution, the job is for your basis team. Maybe they will be able to apply a newer kernel release or upgrade a printer driver. (Most notes related to abprint.c kernel program are solved by upgrade of the kernel)

Regards,

Raymond