Printer Defined to Applications Suddenly Stops Printing with Error "enq: (FATAL ERROR): Could not get process credentials. Errno = 2 enq: errno = 2: No such file or directory" (Doc ID 394553.1)

Last updated on OCTOBER 04, 2016

Applies to:

Oracle Application Object Library - Version 11.5.9 to 11.5.10.0 [Release 11.5]
IBM AIX on POWER Systems (64-bit)
AIX5L Based Systems (64-bit)



Checked for relevance on 24-Jan-2011


Symptoms

A PostScript type printer defined in 11i EBS system for concurrent processing output suddenly stops printing and the concurrent requests complete with "Completed, Warning" status. The concurrent program's output does not print on the printer. While this note was created based on an incident for a PostScript type printer, it should apply to any printer type defined within the 11i Application.

The printer was working fine before. There was no printer/printer type/driver/driver escape sequence setup changed from the 11i application point of view.

The print queue from the UNIX side was down, but it was restarted and after substituting the values of predefined 11i apps variables, printing of the same concurrent program's output file from works fine. But unable to print from the Oracle Applications.

$ lp -c -d$PROFILES$.PRINTER -n$PROFILES$.CONC_COPIES -t"$PROFILES$.TITLE" $PROFILES$.FILENAME

The following error message is received, whenever a request assigned the problem printer for output:

---------------------------------------------------------------------------------------------------------
Printing output file....

Request ID : 2445951
Number of copies : 1
Printer : ljpin2sp

enq: (FATAL ERROR): Could not get process credentials. Errno = 2 enq: errno = 2: No such file or directory

AFPPRN received a return code of failure from routine FDUPRN.

An error occurred while AOL tried to spawn the print process
---------------------------------------------------------------------------------------------------------

Changes

The print queue was seen to be down for the printer using # lpstat -a | grep <printer_name>.

The unix sysadmin had restarted the print queue using # smitty unix administration utility.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms