Report node - not posted

Hi,
Reports are not getting posted and found the below message on the message log. Any help on this is highly appreciated.
Error getting report repository file statistics for process instance: 1812 (63,104)
PSUNX failed to post files to the report repository.  Server scheduled to try again on 2013-09-25-13.47.49.112355.  See log /facs/proj/peoplesoft/PT8.52/appserv/prcs/HRCS/log_output/_PSDSTSRVLOG/transfer_1630.log
===========
pshcmadm@fcas111:/facs/proj/peoplesoft/PT8.52/appserv/prcs/HRSND1/log_output/_PSDSTSRVLOG $ view transfer_1630.log
about to submit ftp -vin /facs/proj/peoplesoft/PT8.52/appserv/prcs/HRCS/log_output/_PSDSTSRVLOG/ftp_1630.txt
Connected to fcws110.fcs.facs.com.
220 "WARNING! THIS IS A PRIVATE COMPUTER SYSTEM. USAGE MAY BE MONITORED AND UNAUTHORIZED ACCESS OR USE MAY RESULT IN CRIMINAL OR CIVIL PROSECUTION. Except for some privacy rights granted by applicable law, by signing on to the system you acknowledge: You do not have any expectation of privacy in your use of the system. You are familiar with, understand, accept, and will comply with the provisions of Company Directive."
331 Please specify the password.
230 Login successful.
Remote system type is UNIX.
Using binary mode to transfer files.
250 Directory successfully changed.
550 Create directory operation failed.
250 Directory successfully changed.
550 Create directory operation failed.
250 Directory successfully changed.
550 Create directory operation failed.
250 Directory successfully changed.
550 Create directory operation failed.
250 Directory successfully changed.
550 Create directory operation failed.
250 Directory successfully changed.
550 Create directory operation failed.
250 Directory successfully changed.
550 Create directory operation failed.
250 Directory successfully changed.
257 "/facs/.p_peoplesoft/peoplesoft/PT8.52/psreports/HRCS/20130925/1616" created
250 Directory successfully changed.
200 Switching to ASCII mode.
local: /facs/proj/peoplesoft/PT8.52/appserv/prcs/HRCS/log_output/AE_AEMINITEST_1812/AE_AEMINITEST_1812.stdout remote: AE_AEMINITEST_1812.stdout
229 Entering Extended Passive Mode (|||43865|)
150 Ok to send data.
226 File receive OK.
303 bytes sent in 00:00 (415.00 KB/s)
221 Goodbye.
File Transfer Successful
============

We are getting the not posted issue, only when we enable the custom sign on peoplecode.
Thanks
Soundappan

Similar Messages

  • Reports are not posting with report repository webserver configured for Sin

    Hi Everyone,
    We have configured Single Signon on our Test environment (UADB1) using Sun Authentication Manager. Everything went well, we can login using our LDAP accounts except for one thing. The reports are not posting to the report repository.
    Our setup goes like this. We have used only one webserver for login and for report repository purposes. SSL certificate was configured in the webserver and we are using https in the report node. Both URLs https://dv001.test.com:8450 and http://dv001.test.com:8400 were configured for Single Signon.
    Report Node Definition
    Node Name: uadb1
    URL: https://dv001.test.com:8450/psreports/uadb1
    Connection Information
    https
    URI Port: 8450
    URI Host: dv001.test.com
    URI Resource: SchedulerTransfer/uadb1
    Below is the error I am getting. If I will use another webserver which is not the Single Signon configured as report repository the reports are posting. So, I am thinking this has something to do with the Single Signon setup and SSL. ANy idea? Thanks.
    PSDSTSRV.2093190 (10) [06/13/10 01:05:43 PostReport](3) 1. Process Instance: 9499/Report Id: 8465/Descr: Process Scheduler System Purge
    PSDSTSRV.2093190 (10) [06/13/10 01:05:43 PostReport](3) from directory: /psft/pt849/appserv/prcs/UADB1/log_output/AE_PRCSYSPURGE_9499
    PSDSTSRV.2093190 (10) [06/13/10 01:05:44 PostReport](1) (JNIUTIL): Java exception thrown: java.net.SocketException: Unexpected end of file from server
    PSDSTSRV.2093190 (10) [06/13/10 01:05:44 PostReport](3) HTTP transfer error.
    PSDSTSRV.2093190 (10) [06/13/10 01:05:44 PostReport](3) Post Report Elapsed Time: 0.2300
    PSDSTSRV.2093190 (10) [06/13/10 01:05:44 PostReport](1) =================================Error===============================
    PSDSTSRV.2093190 (10) [06/13/10 01:05:44 PostReport](1) Unable to post report/log file for Process Instance: 9499, Report Id: 8465
    PSDSTSRV.2093190 (10) [06/13/10 01:05:44 PostReport](2) Process Name: PRCSYSPURGE, Type: Application Engine
    PSDSTSRV.2093190 (10) [06/13/10 01:05:44 PostReport](2) Description: Process Scheduler System Purge
    PSDSTSRV.2093190 (10) [06/13/10 01:05:44 PostReport](2) Directory: /psft/pt849/appserv/prcs/UADB1/log_output/AE_PRCSYSPURGE_94

    Duplicated thread : Reports not posting if using Single Signon webserver as report repo
    Nicolas.

  • Performance Report Manager not posting png files

    PRM on 3.5.1u1 will not generate png files for scheduled reports. However, when I run the report manually and post manually from the generated report, it works just fine. Any ideas on what I'm missing (directory ownership hasn't changed or anything like that)?

    Do an unsetenv on DISPLAY environment variable and restart all services on the server layer from the same shell.

  • Report node is not posting

    Hi All,
    for last 4 days onwards im facing report node not posting in my PROD
    Can you please help me on this
    Im geeting bellow errorr is PT->Process scheduler->Process Monitor->Process list
    1)Java exception thrown: java.la ng.SecurityException: illegal URL redirect
    2)HTTP Status Code is: 902 (63,7 2)
    3)HTTP transfer error
    4)PSUNX failed to post files to the report repository. Server scheduled to try again on 2011-10-19-13.41.50.999989. See log
    In process scheduler log file showing below errors :
    Number of new entries to process: 1
    PSDSTSRV.22891 (73) [10/19/11 01:03:54 PostReport](3) 1. Process Instance: 222812/Report Id: 276354/Descr: Process Scheduler System Purge
    PSDSTSRV.22891 (73) [10/19/11 01:03:54 PostReport](3) from directory: /apps/psoft/hrms9/appserv/prcs/PSUAT/log_output/AE_PRCSYSPURGE_222812
    PSDSTSRV.22891 (73) [10/19/11 01:03:55 PostReport](1) (JNIUTIL): Java exception thrown: java.lang.SecurityException: illegal URL redirect
    PSDSTSRV.22891 (73) [10/19/11 01:03:55 PostReport](3) HTTP transfer error.
    PSDSTSRV.22891 (73) [10/19/11 01:03:55 PostReport](3) Post Report Elapsed Time: 1.9200
    In webserv log showing below error :
    ####<Oct 19, 2011 1:10:46 PM IST> <Notice> <Stdout> <prabhav> <PIA> <[ACTIVE] ExecuteThread: '0' for queue: 'weblogic.kernel.Default (self-tuning)'> <<WLS Kernel>> <> <> <1319010046166> <000000> <SchedulerTransfer, authentication failed>
    In appserv log im geeting below error
    PSAPPSRV.15742 (10) [10/19/11 14:36:04 GetCertificate](3) PeopleSoft Token authentication succeeded: ICI_PS@prabhav
    PSAPPSRV.15742 (10) [10/19/11 14:36:04 GetCertificate](1) (NET.502): @prabhav is an Invalid User ID, or you typed the wrong password. User ID and Password are required and case-sensitive. Make sure you're typing in the correct upper and lower case.
    PSAPPSRV.15742 (10) [10/19/11 14:36:04 GetCertificate](1) (NET.346): Failed to execute GetCertificate request
    Please help me on this
    Thanks&Regards
    SHiva
    Edited by: 892205 on Oct 19, 2011 2:37 AM

    What version of peopletools is it. is their a IB setup in place for the above system. can you ping the local node on the system. did u mark the local node on the single sign on tab as local node.
    are their any psswds changed for the IB user on the system.
    Thanks

  • Process Sheduler not posting report.

    Hi All,
    My Environment: Oracle 10gR2, Win 2003 Server, PT8.49.11, HRCS9.0, Weblogic 9.2, Tuxedo 9.1
    I just configured the Process Scheduler and when I run it to post a report it doesnt.
    When I check the Message Log on PeopleSoft page from System Process Request
    it listed this:
    Process request completed successfully.
    HTTP Transfer error
    NULL HTTP response - check Report Repository web server.   
    PSNT failed to post files to the report repository.  Server scheduled to try again on 2009-05-26-15.59.13.999875.  See log And here is an excerpt of the log.
    PSPRCSRV.4100 (0) [05/26/09 15:42:25 PS@HELIUM](3)    Server action mode: Submitting request
    PSPRCSRV.4100 (0) [05/26/09 15:42:25 PS@HELIUM](3)    Number of New Process Request(s) To Start: 1
    PSPRCSRV.4100 (0) [05/26/09 15:42:25 PS@HELIUM](3) (NET.113): Client RunAeAsync1 service request succeeded 
    PSPRCSRV.4100 (0) [05/26/09 15:42:25 PS@HELIUM](0)    Process Instance: 569 was initiated on the Application Engine Tuxedo Server (PSAESRV)
    PSPRCSRV.4100 (0) [05/26/09 15:42:25 PS@HELIUM](3)    Starting process:  569
    PSPRCSRV.4100 (0) [05/26/09 15:42:25 PS@HELIUM](2)         Process Name: PRCSYSPURGE
    PSPRCSRV.4100 (0) [05/26/09 15:42:25 PS@HELIUM](2)         Process Type: Application Engine
    PSPRCSRV.4100 (0) [05/26/09 15:42:25 PS@HELIUM](3)        Parm List:     -CT ORACLE -CD HRCS -CO PS -CP OPRPSWD -R PurgePSNT -I 569 -AI PRCSYSPURGE -OT 6 -FP F:\psft\HR90DevOra\appserv\prcs\HRCS\log_output\AE_PRCSYSPURGE_569\ -OF 2
    PSPRCSRV.4100 (0) [05/26/09 15:42:25 PS@HELIUM](3)    AESRV (Tuxedo) ID:    1
    PSPRCSRV.4100 (0) [05/26/09 15:42:25 PS@HELIUM](3)         Session Id:   580
    PSPRCSRV.4100 (0) [05/26/09 15:42:25 PS@HELIUM](2) =====================================================================
    PSPRCSRV.4100 (0) [05/26/09 15:42:41 PS@HELIUM](3)    Server: PSNT checking status...
    PSPRCSRV.4100 (0) [05/26/09 15:42:41 PS@HELIUM](3)    Server action mode: Ok (looking for requests)
    PSPRCSRV.4100 (0) [05/26/09 15:42:41 PS@HELIUM](3)    Server: PSNT looking for work
    PSPRCSRV.4100 (0) [05/26/09 15:42:41 PS@HELIUM](3)    HeartBeat alarm on.  Checking server state...
    PSPRCSRV.4100 (0) [05/26/09 15:42:41 PS@HELIUM](3)    Checking Process cancels...
    PSPRCSRV.4100 (0) [05/26/09 15:42:41](3) (NET.113): Client ChkAeStatus1 service request succeeded 
    PSPRCSRV.4100 (0) [05/26/09 15:42:41](3)   Number of requests removed from Task Active List:  1
    PSPRCSRV.4100 (0) [05/26/09 15:42:41](3)      Requests found in Process Request table         1
    PSPRCSRV.4100 (0) [05/26/09 15:42:42](3)    Server: PSNT checking status...
    PSPRCSRV.4100 (0) [05/26/09 15:42:42](3)    Server action mode: Submitting request
    PSPRCSRV.4100 (0) [05/26/09 15:42:42](3)    Number of New Process Request(s) To Start: 1
    PSPRCSRV.4100 (0) [05/26/09 15:42:42 PS@HELIUM](3) (NET.113): Client RunAeAsync1 service request succeeded 
    PSPRCSRV.4100 (0) [05/26/09 15:42:42 PS@HELIUM](0)    Process Instance: 570 was initiated on the Application Engine Tuxedo Server (PSAESRV)
    PSPRCSRV.4100 (0) [05/26/09 15:42:42 PS@HELIUM](3)    Starting process:  570
    PSPRCSRV.4100 (0) [05/26/09 15:42:42 PS@HELIUM](2)         Process Name: PSXPARCHATTR
    PSPRCSRV.4100 (0) [05/26/09 15:42:42 PS@HELIUM](2)         Process Type: Application Engine
    PSPRCSRV.4100 (0) [05/26/09 15:42:42 PS@HELIUM](3)        Parm List:     -CT ORACLE -CD HRCS -CO PS -CP OPRPSWD -R PurgePSNT -I 570 -AI PSXPARCHATTR -OT 6 -FP F:\psft\HR90DevOra\appserv\prcs\HRCS\log_output\AE_PSXPARCHATTR_570\ -OF 14
    PSPRCSRV.4100 (0) [05/26/09 15:42:42 PS@HELIUM](3)    AESRV (Tuxedo) ID:    1
    PSPRCSRV.4100 (0) [05/26/09 15:42:42 PS@HELIUM](3)         Session Id:   580
    PSPRCSRV.4100 (0) [05/26/09 15:42:42 PS@HELIUM](2) =====================================================================
    PSPRCSRV.4100 (0) [05/26/09 15:42:57 PS@HELIUM](3)    Server: PSNT checking status...
    PSPRCSRV.4100 (0) [05/26/09 15:42:57 PS@HELIUM](3)    Server action mode: Ok (looking for requests)
    PSPRCSRV.4100 (0) [05/26/09 15:42:57 PS@HELIUM](3)    Server: PSNT looking for work
    PSPRCSRV.4100 (0) [05/26/09 15:42:57 PS@HELIUM](3)    Checking Process cancels...
    PSPRCSRV.4100 (0) [05/26/09 15:42:57](3) (NET.113): Client ChkAeStatus1 service request succeeded 
    PSPRCSRV.4100 (0) [05/26/09 15:42:57](3)   Number of requests removed from Task Active List:  1
    PSPRCSRV.4100 (0) [05/26/09 15:43:12](3)    Server: PSNT checking status...
    PSPRCSRV.4100 (0) [05/26/09 15:43:12](3)    Server action mode: Ok (looking for requests)
    PSPRCSRV.4100 (0) [05/26/09 15:43:12](3)    Server: PSNT looking for work
    PSPRCSRV.4100 (0) [05/26/09 15:43:12](3)    Checking Process cancels...Thanks and regards,
    Texas!

    We are facing weird issues in dev related to process scheduler posting
    Tools : PT 848(17)
    Application : HCM 9.0
    Unix Process Scheulers - Two
    NT Scheduler - One
    Issue : When report ran from Unix 2, reports are not posting. Unix -1 is fine. This only happening in Dev only, Prod and test looks good (Initially happening in all and able to fix in prod and test).
    Error Message :http transfer error, SchedulerTransfer Servlet error (Distribution Server log)
    I' ve verified process schedular config and web server config files they also looks good.
    Initially nodes configuration
    1) HTTP1 (Unix -mysite.psapp.com)
    URL : http://mysite.psapp.com:16004/psreprts/prd
    URI :mysite.psapp.com
    URI Resource : Scheduler/prd
    2) HTTP2 (Unix2 -mysite.psdev.com ) : Same as above
    Note: Not posting in Unix2 (All three dev, tst, prod).
    Modified
    1) No changes
    2) HTTP2 (Unix2--mysite.psdev.com )
    URL : http://mysite.psdev.com:16004/psreprts/prd
    URI :mysite.psdev.com
    URI Resource : Scheduler/prd
    Note: After modifying Prod, test are posting properly, not in dev
    Verified all the below areas Nicolas siggested. Configuration looks good.
    1. did you set your local node as trusted node (peopletools/security/security objects/single signon)?
    Yes
    2. did you set a default user and password in your local node (peopletools/integration broker/integration setup/nodes) ?
    Yes
    3. did you create a report node and how (peopletools/process scheduler/report nodes) especially URI Resource (something like SchedulerTransfer/+dbname+) ?
    Yes
    4. did you give this report node to your process scheduler distibution (peopletools/process scheduler/server - tab distribution) ?
    Yes
    5. if PS user is managing the process scheduler (cf USERID/USERPWD in psprcs.cfg file), does he got the ReportDistAdmin and/or Process Scheduler Admin roles (peopletools/security/user profiles/user profiles/+your_user+ then tab ROLES) ?
    Ans: PS user only has Process Scheduler Admin, even adding does not resolved the issue
    Any suggestions?
    Thanks,
    Kay

  • Work order to cost center settlement does not post to GL module (FI)

    Dear Expert,
    I find the Maintenance Work order to cost center settlement does not post to GL module (FI)?Also, the settlement cost element is primary element define in GL chart of account.
    When an maintenance order is settled with KO88 or KO8G the work order value posted cost center and  the value is display in cost center report but not post to GL module in FI.As I notice only good issue or receive to/from work order is posted in GL but not the settlement of work order.Why?
    Between, Kindly advise what are the report or T-code to view the maintenance order is done the settlement and what are the value is settle for maintenance work order?
    Kindly advice under what circumstance when maintenance work order to cost center settlement is posted to GL(FI module)?
    Please advice.
    Thank you.
    KH

    Hi Kiran,
    The error message clearly says that "Cost Center validity starts from 01.10.2014" i.e. in the future period.
    Change the cost center from period in the past date and try.
    BR, Srinivas Salpala

  • Processes Not Posting After Maintenance

    Hi,
    Periodically, processes will go to Not Posted status after we bounce the servers during our maintenance window. Usually, bouncing the process scheduler and clearing the cache does the trick. However, one in a blue moon, jobs simply will not post. We will spend hours bouncing servers, clearing caches, etc. and nothing works. Then a couple of hours later everything will start to post.
    Any familiar experiences or thoughts on why this occurs?

    The maintenance varies from week to week; it's generally OS-level patching that doesn't require a reboot. I've got an experienced Tech Arch team taking the servers up and down, so I'm confident that the servers are being bounced correctly.
    In the past, when reports have not posted after maintenance we have shut down the process scheduler and cleared cache and reports started posting. More recently, we've bounced the servers for several hours only to have reports start posting on their own afterwards.
    I pulled the stdout log and found the following:
    Java exception thrown: java.net.ConnectException: Connection refused (errno:239)
    HTTP Status Code is: 900 (63,72)
    Error getting report repository location. (63,85)
    SchedulerTransfer Servlet error. (63,74)

  • PeopleSoft Reports 'Not Posted'

    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 !!!!

    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.

  • Reports not posting from one server

    We're on PT 8.48.10, HRMS 8.8. We have two web servers which are load balanced with a Cisco load balancer (don't have specifics on the load balancer model, but I can request it if need be. I know sticky sessions and source address NATing are enabled). We have two app servers and one process scheduler, all on AIX 5.3. ServerA has a web server, app server and process scheduler on it. ServerB has a web server and app server. The report repository is set up to use ServerA's web server. The report repository is on an NFS mount shared between the two servers. Both servers have read/write permissions to the share.
    We recently went to SSL terminating at the load balancer. We are using HTTP distribution, making the URL the VIP address (https://vip.intranet:8380/psreports/hrms), the URI is using http with the URI Host set to ServerA.intranet and URI port 8380 (the SSL port to the load balancer and the actual web server port are the same). The URI resource is SchedulerTransfer/hrms.
    The issue we're experiencing is that if the load balancer puts the user on ServerA, then there is no issue with reports posting. If they get put on ServerB, the reports go to Not Posted status. The message logs shows the following:
    +2:02:37PM PSUNX failed to post files to the report repository. Server scheduled to try again on 2012-02-06-12.02.51.000919. See log+
    +10 2:02:52PM Report Repository URL is: http ://ServerA.intranet:8380/Scheduler Transfer/hrms (63,68)+
    +10 2:02:52PM Error getting report repositor y location. (63,85)+
    +10 2:02:52PM SchedulerTransfer Servlet error.+
    +10 2:02:52PM Successful Http Reply Code: 20 0 - OK (63,57)+
    +2:02:52PM HTTP transfer error.+
    The space in "SchedulerTransfer" is not in the report node setup. The DSTAGNT log didn't give much more detail:
    PSDSTSRV.1167494 (9) [02/06/12 12:02:37 PostReport](3) HTTP transfer error.
    I was thinking that maybe there is something wrong or missing in the /etc/hosts file, but I'm not sure what. Also, I swtiched the report node to be on ServerB, and then ServerA could not post reports. Any ideas or suggestions?

    Hi,
    A few possible things you might want to check:
    1.
    Portal URI in the portal tab of the default local node, is this pointing to the correct webserver url and port
    2. Check firewall rules (ports) between processcheduler and webservers
    3.
    Is psreports on both webservers a valid directory as mentioned in configuration.properties and validate write access on psreports folder
    4.
    URI host and port on Proces Sheduler Report node, is is this pointing to the correct webserver url and port

  • When the reports will be posted to the report node

    Hi ,
    I am wondering that when the reports will be posted to the report node. Whether the reports are posted to the node once the creation of the single report finishes or the post action will be performed until the finish of the process?
    Anyone has this experience ?
    Thanks in advance!

    on a process like PSJob, each individual process is treated as a separate instance. every instance gets posted separately.
    the overall distribution status gets updated once the complete job finishes.
    that is same with single processes or reports. the overall process status can get updated at the end, but the posting of report to the report node will be done as soon as the instance run completes. it does not wait to transfer the complete reports at the end of the job.
    Thanks

  • Requested node not found in configuration file

    The following warning appears when I instantiate the ReportClientDocument object:
    [main] WARN  com.businessobjects.reports.sdk.JRCCommunicationAdapter  - Requested node not found in configuration file
    This looks to me like a configuration issue. How can I get rid of it?

    Please read the rules of engagement and add all of the missing info. I'm assuming you are developing in Java so moved your post to the Java forum.

  • PSNT scheduler not posting

    Hello,
    I have two PeopleTools 8.52.0 process schedulers: PSUNX and PSNT. Both have the same report node assigned for distribution. PSUNX is running on an OEL5 unix application server, PSNT on an XP machine, web server is on a different OEL5 machine altogether.
    Now, I run an identical process (simple application engine test) on both of these schedulers, but only the process running on PSUNX gets posted to the report repository. How is this possible, considering both are setup to use the same report node? The other process, running on PSNT, ends with an error as follows:
    Error converting HTTP response to UCS2
    XML document object creation failed.
    Unable to process HTTP reply from Report Repository.I know this message will pop up when there is an incorrect path or even different case in URL, URI and such in the report node configuration, but that shouldn't be the case here, since one process scheduler works fine.
    Thanks for your thoughts.

    >
    Without saying about the need of 64bit wordsize, Windows XP is not supported as a client within Peopletools 8.52, it's even worse to be a Peoplesoft server.
    Try to use a supported configuration instead, before wasting to much time on issue which potentially cannot be fixed in the given state.
    >
    Unfortunately I don't have the option to upgrade from XP due to licensing and other components, best to leave this station alone as it is. I's not used for any production environment though.

  • Report node and reports repository

    what is the difference between report node and reports repository. I know that Process schedular picks the report from report repository in order to show in process monitor. Does report node and reports repository are same??

    After a report runs to success in runstatusYeah, but the files are send to the report repository even if it is not successful terminated (run status is not sucess). If the files are not sent to the report repository, then the problem doesn't come from the process itself, but from the definition, space availibity...
    When a report has been posted sucessfully (transfered from the process scheduler report repository - on the other hands the log_output dir, to the report repository defined into the report node), the status of the distribution status is Posted.
    The run status and distribution status are independant eachother.
    Nicolas.

  • Problems with report nodes

    when i post the reports,i get the posting message as success but the distribution node status says not posted?
    can someone help me?

    I have done the following and the problem has been resolved
    It seems that your Default local node did not have the authentication option set. You have to set the Authentication option under Node definitions. Go to
    PeopleTools >> Integration Broker > >Node Definitions and set the
    Authentication Option from 'None' to 'Password'. After this restart the
    application server. Also recheck the report node URL and URI host name
    specified on the report node definition page. Apart from this also setup the
    single signon. Go to PeopleTools->Security-> Security Objects -> Single
    Signon and add an expiration time value and for the Message node name insert
    your default local node. After saving all this restart your app
    server, process scheduler and web server.

  • Success but not Posted Process Scheduler

    Hi all,
    I just installed HCM 9.1 PT8.52, Demo DB, Oracle 11g Database and Windows server 2008.
    I installed and configured the process scheduler (followed the steps) and created a windows service for it, that is 'Automatically started'.
    When trying to run a process scheduler, I'm getting a run status 'Success' but the 'Distribution Status' is 'Not Posted'.
    I suppose it is not finding the location or something?
    What should I check?
    Thanks.
    Bechara

    Thank you!
    The ReportDistAdmin role was missing so I added it.
    I shut down process scheduler and re-run it, but I'm still getting 'Not Posted'
    Is there any additional step to do before trying the reports?
    Update
    And the password was missing in the default local node, I added it and it worked!
    Thanks you Hakan!
    Edited by: Bechara IS on Nov 8, 2012 3:39 AM

Maybe you are looking for

  • IWeb Bugs and a wish for the future. :)

    Hi there, Two issues that I've found moving my photoblog to iWeb, and I'm wondering if they are bugs or issues that the community knows about: 1. I've changed the template I used a lot - font colours, background, etc. Now when I create a new blog ent

  • How to write output from Keithley 220 to Excel using Labview

    Hello, I have seen other posts that ask this question and was wondering if anyone has found the solution? I have downloaded the driver and seem to be able to communicate with the instrument. However, I am not very sure how to modify the driver to set

  • Deviate from Master cost center

    Dear All, Can any one plz solve this issue. A position had been assigned to cost center and master cost center.How do we deviate that position from the master cost center? 2). What features do you come across in payrolls employee attributes and CAP P

  • IPhoto slideshow export -- jerky Ken Burns rendering

    Have an iPhoto slideshow of 25 pictures. On some, I used Ken Burns effect to zoom in, out, etc. When I export, the result is a .mov file. Everything looks great when I play it on Quicktime, except for some of the photos on which I had used Ken Burns

  • Ibook G3 running 10.3.9 transfer to a Macbook running 10.7.5.

    I have an old Ibook G3 running 10.3.9 and would like to transfer its files to a Macbook running 10.7.5. I have one Apple cable that looks like a USB on one side and a phone charger on the other. I'd also be willing to do it wirelessly if possible. An