16 May 2013

Process Scheduler Trouble Shooting



GUIDE LINES FOR TROUBLESHOOTING:

1.       Check DB server is up & running or not.
2.       Check DB Listener is up & running or not.
3.       Check tns names.ora file is configured or not (using netca)
4.       Check App server domain configuration menu(psappsrv.cfg)
5.       Check psprcs.cfg file I,e Process Scheduler config file.
6.       Check http & https port numbers in config.xml file

Error: The appserver is down at this time
·         Jolt is no( we can’t logon to PIA)
·         Jolt is yes(In App domain 4 to configure)
7.       Jolt is to establish the connection b/w  App server & web server.
8.       We have to check config properties.

PROCESS IN QUEUED NOT SUCCESS ERROR:
1.       Process scheduler is down.
2.       Cleaned UP IPC Resources: These are the OS Resources such as queues, shared memory & semaphores.
·         When app server shut down all IPC Resources must be removed from the system.
·         In some cases App server may not possible to boot. We have to do clean IPC.
Using : tmipcrm –y  /apps/psoft/PT8.48/PSDEMO/PSTUXCFG   ->This will remove IPC Resources.
3.       Check the process scheduler logs.
4.       We will set the trace files when the process running.
5.       PSADMIN network id was locked due to logging failover attempts 3 times.
6.       PSNT not selected in process monitor.

TICKETS:
1.       When we are running SQR programs Run status is error & distribution status is posted.
a)      (1) SQR executables are in prprcs.cfg
(2) we have to check psprcs.cfg
     Sqr=c:\PT8.48\bin\sqr\ora\BINW\sqrw.exe
     It wil look for executable path.
(3) we have to check report node, distribution node, integration broker.

MAIN REASONS REPORTS ARE NOT POSTING:
1.       Found wrong password for IB setup for HRMS IB Gateway on Financial system.
2.       Account lockout issue. We have corrected by setting connect password.
3.       The PS went down due to which process were sitting in queue state.
4.       Cleaned IPC resources on process server & nvision is processing now.
5.       Some person had changed the super user pwd, so the  jobs are not going posted.
6.       Admin N/W id was locked out due to which reports were running into error.
7.       Reconfigured the PSNT server & cleared cache(now crystal reports are working fine)
8.       The PSNT PS could take only 3 App engine process at a time rest of them were queued.
9.       After bouncing the PSNT server the status is running.
10.   After adding SQR executable to the psprcs.cfg file. It is working fine & the process are going to success.
====================================================================


Process Scheduler Reports Have Posting or Not Posted Status.



Cause

This issue may be caused by one or more incomplete or improper configurations of the Process Scheduler, Server Definition, Report Node, Default Local Node, Single Signon Security, Web Profile, or OS level security.
Solution

Please confirm the following required configurations:

1) Peopletools > Integration Broker > Integration Setup > Nodes > Default Local Node must have Password Authentication 

2) Peopletools > Security > Security objects > Single Signon > must list the Default Local Node 

3) Peopletools > Process Scheduler > Report Node contains the correct configuration 
 3.1) If using HTTP, on the Report Node Definition page, the "URI Host" field must contain a fully qualified domain name. 
 3.2) If using FTP, the "FTP Address" field should have the fully qualified domain name. 

4) The PeopleSoft User ID that you use to start the Process Scheduler Server must include the
"ProcessSchedulerAdmin" role. ( From PSPRCS.CFG > "UserID" ) Said UserID should have the role in PeopleTools > Security > User Profiles > User Profiles > {UserID} > Roles tab 

5) If you specify the Authentication Token Domain name during the PeopleSoft Pure Internet Architecture installation, you must also include the domain name on the "URI Host" field. 

6) Verify that the Operating System account starting your Webserver has full control or all priveleges to the directory location specified as your ReportRepositoryPath= in your Webserver's configuration.properties file.

6.1) If your Webserver is on Microsoft Windows and is started as a Windows Service, on the "Log On" tab for the Windows Service properties, ( Start > Settings > Control Panel > Services > {Your PIA Service} > "Log On" tab ) 

6.2) Make sure you select the "This Account" radio button and select either a local or domain user with administrative rights. 

7) Navigate to PeopleTools > Web Profile > Web Profile Configuration > Search > {Select your Web Profile-Often "DEV"} > "General" tab 

7.1) Authentication Domain : {Your DNS value. Example .dns.com}
7.2) Report Repository Path : {This value overwrites value in configuration.properties file} 

8) If any configuration changes are made, please bounce the application server, web server, and process scheduler and clear cache before restarting.

 Step 1

Navigate to PeopleTools ->Process Scheduler ->Report Nodes

Create a new node HRDEMO01 (DB_NAME)
Configure the report node for FTP
URL : http://<systemIP>:<httpport>/psreports/<sitename>
Home directory: (directory of psreports)
Operating System: UNIX
FTP Address: (IP of Linux Box)
FTP ID/password : (psoft user or user having write permission on psreports)

Save the settings

Step 2

Navigate to Process Scheduler -> Servers,
Search for PSUNX Server and open and go to Distribution tab
 In the distribution Node Name select the node definition created in step 1
Specify other values
Bounce back the process scheduler




 

No comments:

Post a Comment