PeopleSoft Reports 'Not Posted'

Question

First of all I know that this a problem which has been discussed many a times here and in other websites. I have tried checking almost all the possible solutions for this and finally found that my problem is different than those already answered.
This is the problem with PeopleSoft CRM(8.8) with PT 8.45.16 and my application is running in Unix box. From process monitor, the reports are going to Posting status and finally going to 'Not Posted' status.Message log says 'PSUNX failed to post files to the report repository' then retries and finally unable to post them.
DSTAGNT Log shows :
(30) [04/15/10 08:25:53 PostReport](3) Number of new entries to process: 1
PSDSTSRV.23261 (30) [04/15/10 08:25:53 PostReport](3) 1. Process Instance: 77514/Report Id: 48766/Descr: Process Scheduler System Purge
PSDSTSRV.23261 (30) [04/15/10 08:25:53 PostReport](3) from directory: crm/appserv/prcs/CRMT2/log_output/AE_PRCSYSPURGE_77514
PSDSTSRV.23261 (30) [04/15/10 08:25:53 PostReport](3) Transfer Log: 61093, check file crm/appserv/prcs/CRMT2/log_output/_PSDSTSRVLOG/transfer_61093.log for status
PSDSTSRV.23261 (30) [04/15/10 08:25:53 PostReport](3) Post Report Elapsed Time: 0.2900
PSDSTSRV.23261 (30) [04/15/10 08:25:54 PostReport](1) =================================Error===============================
PSDSTSRV.23261 (30) [04/15/10 08:25:54 PostReport](1) Unable to transfer all files for Process Instance: 77514, Report Id: 48766 in Report Repo Directory: CRMT2/20100415/48766
PSDSTSRV.23261 (30) [04/15/10 08:25:54 PostReport](2) Number of files to be transferred: 1
PSDSTSRV.23261 (30) [04/15/10 08:25:54 PostReport](2) Number of files to be transferred: 0
PSDSTSRV.23261 (30) [04/15/10 08:25:54 PostReport](2) =====================================================================
PSDSTSRV.23261 (30) [04/15/10 08:25:54 PostReport](1) =================================Error===============================
PSDSTSRV.23261 (30) [04/15/10 08:25:54 PostReport](1) Unable to post report/log file for Process Instance: 77514, Report Id: 48766
PSDSTSRV.23261 (30) [04/15/10 08:25:54 PostReport](2) Process Name: PRCSYSPURGE, Type: Application Engine
PSDSTSRV.23261 (30) [04/15/10 08:25:54 PostReport](2) Description: Process Scheduler System Purge
PSDSTSRV.23261 (30) [04/15/10 08:25:54 PostReport](2) Directory: crm/appserv/prcs/CRMT2/log_output/AE_PRCSYSPURGE_77514
It is trying for 15 times and finally errors out.
Transfer Log shows :
200 Type set to A.
200 PORT command successful.
150 Opening ASCII mode data connection for AE_PRCSYSPURGE_77514.stdout.
226 Transfer complete.
3531 bytes sent in 0.00 seconds (10355.08 Kbytes/s)
221 Goodbye.
File Transfer Successful
Important Findings :
When I look into log_output folder, the output file still exists there
When I look in psreports folder which is my report nodes, I can see the file present there as well with timestamp of the last retry as per DISAGNT log
When I look in the PSDSTSRV service through PSADMIN, it gets loads everytime it tries to post the report and finally when it goes to Not Posted status it comes down to 0 load.
I checked my report node and they look correct.
So in this case, the ftp is finally working and putting the reports to the report repositary but for some reason distribution agent is not getting this information and so it is erroring out. Reports are stored in both log output and report repository.
I tried restarting process scheduler, clearing cache and deleting some old reports but still it is not helping it any way.
Any suggestions from you will be great !!!!

Answer 1

I checked after changing Logfence setting to 5 in process scheduler. It gave me more elaborated logs. As expected the ftp part went fine and the reports were correctly moved to psreports folder. But the process monitor still showing 'Not Posted'. When I looked back to the logs, the interesting message that I saw in Scheduler log as follws :
Invoking service PostReport
PSPRCSRV.21355 (0) [04/20/10 10:56:17](5) (NET.100): Network API tracing TUXEDO: tpalloc {type='CARRAY', subtype=NULL, len=8192}
PSPRCSRV.21355 (0) [04/20/10 10:56:17](5) (NET.100): Network API tracing TUXEDO: tpalloc return {pmem=0x00ed1fc0}
PSPRCSRV.21355 (0) [04/20/10 10:56:17](5) (NET.100): Network API tracing TUXEDO: tpacall {svc=PostReport, idata=0x00ed1fc0, ilen=45, flags=0x00000007}
PSPRCSRV.21355 (0) [04/20/10 10:56:17](5) (NET.100): Network API tracing TUXEDO: tpacall return {svc='PostReport', cd=0}
PSPRCSRV.21355 (0) [04/20/10 10:56:17](4) (NET.133): PostReport asynchronous invocation sent to Application Server
PSPRCSRV.21355 (0) [04/20/10 10:56:17](4) Async service PostReport invoked: elapsed time=0.0000
PSPRCSRV.21355 (0) [04/20/10 10:56:17](4) (NET.113): Client PostReport service request succeeded
PSPRCSRV.21355 (0) [04/20/10 10:56:17](5) (NET.100): Network API tracing TUXEDO: tpfree {pmem=0x00ed1fc0}
PSPRCSRV.21355 (0) [04/20/10 10:56:17](4) (NET.111): Client PostReport service request object destroyed
PSPRCSRV.21355 (0) [04/20/10 10:56:17](3) Number of requests removed from Task Active List: 1
It looks like it is not recognising that the reports are laready posted. PSDSTSRV process is not getting that intimation. Not sure about how it works internally, but looks like it is sending some asynchronous message is sent to App server for this? Is that breaking somewhere ther?
Also I went to the blogs and checked that in my existing installation, we have the setting already there. So, we are good with the overall configuration.
Any insight on this would be great.