E-TUX/RD: Receive Error: "PostReport could not be sent because of a blocking condition within Tuxedo", Reports Stuck in Posting (Doc ID 641428.1)

Last updated on JULY 25, 2023

Applies to:

Symptoms

Report posting stops completely or slows down to the point that process output starts to "back up" on the affected Process Scheduler.  In the Process Monitor, all completed reports are stuck with a status of Posting.

The Schdlr_mmdd.log file may show:

"PSPRCSRV.48548 [01/14/04 00:00:02](1) (NET.333): The service PostReport could not be sent because of a blocking condition within Tuxedo on the client."
"PSPRCSRV.5132 [02/17/05 14:48:53](4) Service PostReport FAILED"

The Dstagnt_mmdd.log file may show:

DSTAGNT_DATE.LOG shows the following message.
PSDSTSRV.185146 [01/14/04 00:00:33 PostReport](1) =================================Error===============================
PSDSTSRV.185146 [01/14/04 00:00:33 PostReport](1)           Unable to find the directory  PSHOME/appserv/prcs/DOMAIN/log_output/AE_APS_SFL_127470 to post files from for
PSDSTSRV.185146 [01/14/04 00:00:33 PostReport](2)              Process Instance: 127470, Report ID: 127327
PSDSTSRV.185146 [01/14/04 00:00:33 PostReport](2) =====================================================================

These messages will be repeated continuously in the logs.  If the Process Scheduler and/or Distribution Agent services are bounced, these messages will continue to be posted to the logs.

Changes

Cause

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.