Jamie's Blog

PeopleSoft xmllink 302 : Site moved temporarily

Problem:

After refreshing one of our environments the xmlink http://server/xmllink/fmsqa stopped working and was throwing an error like “302 : Site moved temporarily”.

Solution:

After troubleshooting this was caused by an incorrect password in the XML Link section of the Webprofile -> Security Tab.

After changing the userID and Password to the  correct one for the QA environment. This problem went away and they where able to access the xmllink using the excel spreadsheet.

Have Multiple PeopleSoft Environments Opens In Internet Explorer

Problem:

We had some users who needed to have a QA and PROD PeopleSoft environment open at the same time. When they would launch the second window it would log them off of the original peoplesoft environment.

Solution:

If you launch a “new session” in IE 8 it saves the cookies in the different location. This enables you to sign on to as many new peoplesoft sessions as you would like without losing your existing one.

COBOL Program PSPBARUN aborted (2,-1)

Problem:

Received the following error when running an on demand COBAL execution

COBOL Program PSPBARUN aborted (2,-1) At BENEF_PB_WRK.ODEM_SCHED_ACTY_PB.FieldDefault ODEM_RemoteCall PCPC:335 Statement:4

Resolution:

After checking the COBAL license server everything appeared fine. I Rebooted and cleared cache of the application servers which fixed the problem.

PeopleSoft Directory Creation Failed (63,49)

Problem:

After the report ran successfully it was unable to report to the Report Repository.

Errors:
Directory Creation Failed  (63,49)
PSUNX failed to post files to the report repository.  Server scheduled to try again on 2010-07-07-13.17.32.000234.  See log
Java Exception: Error while wr ite to file:java.lang.Security Exception: Directory Creation Failed  (63,49)
SchedulerTransfer Servlet error.

Resolution:

After logging into the Windows report repository it was apparent that the drive was full. We cleared off some files that freed up some space. I was able to click repost and everything finished successfully.

PeopleSoft: Could not create shared cache (0,0)

Problem:

When trying to sign into PeopleSoft the error Could not create shared cache (0,0)

Resolution:

Verify there is enough free space on the  file systems
Common directories to look at: * /u01/app/ptools849/psoftXXX/appserv/XXXX%APPDOMAIN%/LOGS
You can also run “df -m|more” when inside of /u01/app/ptools849/psoftXXX to see which directories are using the most space

Change Assistant PSEMAgent clear peer ids and cleanup

Problem:

Having issues with PSEM Agent and environments not showing up. Browsing to the hub website “http://XXXXX.XX.com/PSEMHUB/hub” there are many items listed that do not exist anymore.

Solution:

The Following will cleanup the files and afterwards you should be able to start the agents and see the environments in change assistant without any problems

@ECHO OFF
REM *********
REM The File clears the contents of the EMF Hub and Agents and Change Assistant
REM *********
PIA ServicePeoplesoftStart

Rem THIS IS FOR THE PC RUNNING CHANGE ASSISTANT
move “C:\Program Files\PeopleSoft\Change Assistant\envmetadata\data\matchers.xml” c:\matchers.xml
del /q /s “C:\Program Files\PeopleSoft\Change Assistant\envmetadata\data\*.*”
move c:\matchers.xml “C:\Program Files\PeopleSoft\Change Assistant\envmetadata\data\matchers.xml”
rmdir /q /s “C:\Program Files\PeopleSoft\Change Assistant\envmetadata\PersistentStorage\”
rmdir /q /s “C:\Program Files\PeopleSoft\Change Assistant\envmetadata\scratchpad\”
rmdir /q /s “C:\Program Files\PeopleSoft\Change Assistant\envmetadata\transactions\”

REM THIS IS FOR THE AGENTS
move %1\PSEMAgent\envmetadata\data\matchers.xml c:\matchers.xml
del /q /s %1\PSEMAgent\envmetadata\data\*.*
move c:\matchers.xml %1\PSEMAgent\envmetadata\data\matchers.xml
rmdir /q /s %1\PSEMAgent\envmetadata\PersistentStorage\
rmdir /q /s %1\PSEMAgent\envmetadata\scratchpad\
rmdir /q /s %1\PSEMAgent\envmetadata\transactions\

REM THIS IS FOR THE HUB
Stop Peoplesoft PIA Service
rmdir /q /s %1\webserv\peoplesoft\applications\peoplesoft\PSEMHUB\envmetadata\data\environment\
rmdir /q /s %1\webserv\peoplesoft\applications\peoplesoft\PSEMHUB\envmetadata\data\proxies
del /q /s %1\webserv\peoplesoft\applications\peoplesoft\PSEMHUB\envmetadata\data\*.*
rmdir /q /s %1\webserv\peoplesoft\applications\peoplesoft\PSEMHUB\envmetadata\PersistentStorage\
rmdir /q /s %1\webserv\peoplesoft\applications\peoplesoft\PSEMHUB\envmetadata\scratchpad\
rmdir /q /s %1\webserv\peoplesoft\applications\peoplesoft\PSEMHUB\envmetadata\transactions\

PeopleSoft Invalid Access ID and password for signon — see your security administrator.

Problem:

When trying to connect to Data mover or Application designer the following error (“PeopleSoft Invalid Access ID and password for signon — see your security administrator.” ) comes up even though you are inputting the correct user/pass combination.

Resolution:

Verify that the connect ID and Connect password is correct in the Configuration Manager. This ID allows PeopleSoft to connect to the database to verify that the user/pass is correct.

PeopleSoft Error Crystal Reports Print Engine error text: Error in File e:\XX\XX.rpt: Access to report file denied. Another program

Problem:

PeopleSoft Crystal Report was not processing and error out. Looking at the message log I noticed the following messages:
Crystal Reports Print Engine error text: Error in File e:\ptools849\psofthcm\crw\eng\pbc_0004.rpt:
Access to report file denied. Another program

looking at the crystal trace file to view more detailed information I noticed:
4     328    37007      05/07/10 10:04:02   Using report: E:\PTOOLS849\PSOFTHCM\CRW\ENG\PBC_0004.RPT
5     328    37007      05/07/10 10:04:02   About to RunReport()
6     328    37007      05/07/10 10:04:02   About to open print engine
7     328    37007      05/07/10 10:04:02   Print engine opened. About to open job
8     328    37007      05/07/10 10:04:03   Job opened
9     328    37007      05/07/10 10:04:03   Logon info set
10    328    37007      05/07/10 10:04:03   Parameters: -CTORACLE -CDHCMPRD -COHHARVEY -CPUnavailable -I37007 -RP”PBC_0004″ -OT6  -OP\\server\files\Departments\Finance\Payroll\xxx\xx\x\file-20100507 -LGENG.txt -OF14 -ORIENTL

Resolution:

The report file did exist and access was granted to the report file. However, the output path of the crystal report was on the network share. I had to grant access to the process scheduler service account to write the output file.

PeopleSoft Java Exception: Error while wr ite to file:java.lang.Security Exception: Directory Creation Failed (63,49)

After running a process the Distribution Status goes to Error and the reports/logs do not post. This was occurring for some reason after domain controllers were restarted.

Problem:
4:17:08PM Java Exception: Error while write to file:java.lang.Security Exception: Directory Creation Failed  (63,49)
4:17:08PM SchedulerTransfer Servlet error.

Resolution:

make sure the correct smb file share name is in the correct web profile configuration. We changed the domain name netbios name and it caused our PeopleSoft report repository node that is connected to the DFS to error out.

WebLogic SSL Configuration Document

This document will assist in enabling SSL directly on the webservers if you are unable or do not have a front end load balancer to offload SSL.

FILES
ssl-how-to-WebLogic92