Commonly when setting up a new system, you will attempt to post a report and it will stay in posting status for a long time and eventually return a Not Posted status.  If you review the details on the message log you will find something similar to:

Error: The XML file returned by the webserver is invalid, xml document object creation failed.

When setting up a report node (Home>PeopleTools>Process Scheduler>Report Node) and you use the SchedulerTransfer as the transfer tool, you must ensure that two things are in place.

1. Make sure that the Default Local Node, has a password assigned to it.  Without a password it will always fail.

2. Make sure the user that started the Process Scheduler has the Role: ProcessSchedulerAdmin assigned to their profile.

This should resolve the problem.

When creating a new server the other day, I was attempting to start the application server and a ran into an odd error message that did not seem to have any solution from PeopleSoft’s support or even google for that matter. This error was found in the stderr output file for the application server:

ERROR: dlopen in libpscompat failed for ‘libpsora.so’: libclntsh.so.10.1: wrong ELF class: ELFCLASS32

I couldn’t find anything specifically wrong with the symbolic links in the library directories for Oracle as the sites were suggesting.  The weird thing that kept the red flag waving was ELFCLASS32.  After some more review of the environment I had just created, I found that I had installed the Oracle Database software using a 32bit Linux version instead of the Linux_x86_64 bit version.  This was caused by simply not paying attention when I was downloading the software.  When downloading the software if you try to download from the main site they only let you download 11.2.0.1, but for PeopleTools 8.52.xx you want to be at 11.2.0.3.  After logging into support and search for patchset 11.2.0.3 the page that comes up has a drop down, and there is a Linux version and a Linux_x86_64 bit version (much further down).  After I installed the correct version and recreated the database, the application server started without any issues.

I ran into a weird problem where I was unable to install PIA (PeopleSoft Internet Architecture) through the delivered install tools (PsMpPIAInstall or PSADMIN).  It kept getting about 90% complete and then drop out and report an error saying PIA failed to install.

I was not able to find out much about the error, but what I did find was that I was missing a bunch of libraries specifically in my case WLST classes.  As it turned out I had been cleaning up a bad install of another product and deleted the utils directory from the BEA home.

I re-installed the weblogic 10.3.0.4 version on the server into a new BEA home, and everything worked fine after that.

I found several cases that report multiple reasons for the failure but in the end the only thing that remained constant was re-install and everything works again.  There are several directories that weblogic installs with that are necessary in order to make PIA install work.

Error:  java.lang.RuntimeException: Could not find the OffLine WLST class

When doing the install you can issue the parameter: -debug -DDEBUG=true and that will issue thousands of information rows, but it does give some idea where the issue is.

When you are creating a service for your application/process server in windows using the psadmin tool.  If the user account you are using does not have local administrator access on Windows 2008, it will generate the error:

openSCManager failed access is denied (0X5)

You will need to run the “Command Prompt” link with the option “Run as administrator”. You should be able to right click on the menu item in the start menu and select this option. Once at the command line change to the appserv directory and run psadmin, and then install your windows service.

When configuring the Report Repository using the Scheduler Transfer tool you will want to configure the node using the http/https settings:

Home > PeopleTools > Process Scheduler > Report Nodes

The URL will be the same as it always is, this variable is primarily used for the link in process monitor to view the reports/logs.  The URI host is usually set to the web server name, however, if you are using a load balancer you might wish to use one web server to handle the traffic or configure it to go to an internal site that can handle the balancing.  URI Port will be the port of the webserver, typically the regular access port, but if you are using a balancer and it is redirecting the port may need to setup with the internal port number.  URI Resource is the class that handles the transfers, it should be:

SchedulerTransfer/<piasite>

Be very careful of case here.  See picture as an example.  Lastly, you will want to make sure that the user that is handling the process scheduler in question has the Role: ProcessSchedulerAdmin, and that the default Local Node has been configured to have a password associated with it (Home>PeopleTools>Integration Broker>Nodes).