Reports not posting issues-

PostReport fails giving errors in PSDSTSRV log -

PSJNI: Could not load the JavaVM library jvm
PSJNI: EnvImplementation::Ctor: Failed to get JvmHandle
HTTP transfer error.
HTTP Status Code is: 904

The stderr logged below entry -

dlopen in libpscompat failed for 'libjvm.so': ld.so.1: PSDSTSRV: fatal: libjvm.so: open failed:

We started with updating the Java with the latest available version, but no luck. Later it was found that we had installed JDK instead of JRE. Removing the JDK and installing the JRE fixed this issue J

If you need the older Java versions, this is the link to Java archive downloads:
http://www.oracle.com/technetwork/java/javasebusiness/downloads/java-archive-downloads-javase6-419409.html


There are 2 scenarios when we observe report posting issues-
1- All the reports are not NOT posting, or
2- A particular report is not being posted.

If all the reports are not posting then it might be an infrastructure issue, bouncing PRCS may help as well.

Error: The XML file returned by the web server is invalid. XML document object creation failed.
we see this error entered in process instance's message log by looking through process monitor page. This is an issue with SchedulerTransfer servlet which requires authentication. When a report needs to get transfer to report repository, distribution agent use SchedulerTransfer servlet for this purpose. SchedulerTransfer servlet checks for the default local node and if there is no authentication there, it will get fail. The Default Local Node must have the Authentication Option set to 'Password'. Here, change Authentication option for default local node (IB>IB Setup>Nodes) to "Password". Supply userid and password. This userid must have ProcessSchedulerAdmin and ReportDistAdmin roles attached to it. Application server needs a restart post this change.


Here are the things to check if reports are not posting-
1) Check logs for SCHDLR and DSTAGNT.
2) Check message log through process monitor, check HTTP status codes (if any)
3) Default local node must have Password as authentication option.
4) Report Node settings must be correct.
5)  The OS account to start webserver must have all the permissions (777) set to access Report Repository.

status = 'Posting' - Check whether there is enough space on the Report Repository, verify that PSPRCSRQST, PS_CDM_LIST and PSPRCSQUE table counts are in sync.
 

By default, the Log Fence value is set to 3, change it to 5 in psprcsrv.cfg to get more detailed log information.


* psadmin is the only role which doesn't have any permission list attached to it. The privileged associated with this role are hard coded in application code.