Printing issue

[Former Member]

Hi,

We have a strange issue where we get this message when we print documents.

SAP spool error log
      =====================

Print request processing log

The operating system is reporting problems


Error 88 closing file /usr/sap/SID/DVEBMGS<nn>/data/001CCJhB.SID

Errors occurred processing this print request


Error during print request output. l_rc = 8
There may be no printout

File system was not full during that time.

By the way why is storing in the data directory?

Anybody has faced this issue before?

[Laszlo_B · Accepted solution]

Hello,

the print data which will be sent to the printer will be created in the data folder. This file is different from the TemSe data (where the temporary information is stored).

About the error: the operating system reported "error 88" while closing the print file. It would be useful if you could tell which operating system is used on the application server which reported this error.

Regards,

Laszlo

[Former Member · Accepted solution]

OS is AIX.

[Laszlo_B · Accepted solution]

Hello,

error 88 in AIX means "disk quota exceeded". Please check whether the folder "/usr/sap/SID/DVEBMGS<nn>/data" is full - or a disk limit has been reached.

Also: increasing the AIX ulimits might be considered. If this will be used, you can see some information in SAP Note 323816 - "AIX: User limit settings".

Regards,

Laszlo

[Former Member · Accepted solution]

Hi,

Thanks a ton for the info, is error code 88 is it OS error code?

[Laszlo_B · Accepted solution]

Hello,

yes, "error 88" is issued by the OS. SP01 only copies this error code from the OS into the spool log.

This means: AIX needs to be adjusted to solve this problem.

Regards,

Laszlo

[Former Member · Accepted solution]

Hi Laszlo,

Thanks will check with the OS team, but closing a file is a strange issue can this be an issue where its trying to write a big file and its not able to save or close it ?

[Laszlo_B · Accepted solution]

Hello,

from AIX OS side unfortunately I can't tell. However, if the problem would be caused by R/3 itself, then other error messages would be logged too in the System Log / Developer Traces.

If this is not the case (so: no R/3 error messages are logged prior to "error 88"), the OS needs to be revised.

The SCN Space should be able to give further tips about error 88.

Regards,

Laszlo

[Former Member · Accepted solution]

Thanks,

[achmad_dimyati5]

Hi,

Check SM21 to find the error

Check SPAD --> Administration --> Check Inconsistency

Check Temse (SP12) --> Consistency Check

It could be AIX ulimit issue but could be others. SM21 will give you the idea.

Regards,

Achmad

[Former Member]

Hi Achmad,

I dont think so it can be a ulimit issue since we would have installed using the guide as a reference.

Also for a running production system do we run a consistency check.

I have checked all the possibilities somewhat the earlier responses regarding the error codes in AIX makes sense to me.

[achmad_dimyati5]

Hi,

Any info from SM21. How about the result consistency check from SPAD and SP12?