blockcopy

Thursday, July 8, 2021

Unable to get PeopleSoft landing page after sign in due to error CPCServletService::DoService -> nPcmReturn=24: Failed to start the Java Virtual Machine.

Unable to get PeopleSoft landing page after sign in due to error CPCServletService::DoService -> nPcmReturn=24: Failed to start the Java Virtual Machine.

If you get following set of errors even after application services bounce then please try this solution.

Error:

PSAPPSRV.29571 (13) [2021-07-08T06:41:20.869 XXX@172.IP (IE 11.0; WIN10) ICScript] OYwwgOA89L98oA 3980798699840058369 XXXX(1) Could not load the JavaVM library jvm
PSAPPSRV.29571 (13) [2021-07-08T06:41:21.161 XXX@172.IP (IE 11.0; WIN10) ICScript] OYwwgOA89L98oA 3980798699840058369 PEOPLE1 (1) CPCServletService::DoService -> nPcmReturn=24: Failed to start the Java Virtual Machine. (2,766) PT_SECURITY.iScript.OnExecute  Name:getSIDHTML  PCPC:199  Statement:6
Called from:PT_FAV.AddToFav.OnExecute  Name:getSIDHTML  Statement:32
Called from:PT_FAV.AddToFav.OnExecute  Name:setHTML  Statement:120
Called from:PT_FAV.AddToFav.OnExecute  Name:AddToFav  Statement:23
Called from:PT_POPUP.Popup.OnExecute  Name:Popup  Statement:15
Called from:PT_BRANDING.IframeHeader.OnExecute  Name:setAddToFavPopupHTML  Statement:101
Called from:PT_BRANDING.IframeHeader.OnExecute  Name:SetAddFav  Statement:98

Solution ->

First check the what JAVA_HOME is set. Make sure JAVA_HOME directory exists.

Check PATH, LIBPATH and Shell profile ( of Linux server) and make sure jdk path is accurate.

Update correct JDK path , exit from your id and login back and rev-verify if environment variables are pointing to correct JAVA_HOME path.

Shutdown App services , configure App Server, clear cache and bring up services.

This should fix the issue.

Wednesday, May 5, 2021

Integration Gateway Message Unmarshalling: Could not Parse the XML message String. (158,10415)

Integration Gateway Message Unmarshalling: Could not Parse the XML message String. (158,10415) 

You will notice following error while pinging / testing node from Integration Gateway or Node definition. If you see following error in Logs then this solution will work. 

errorLog.html :
com.peoplesoft.pt.common.XmlException: [Parsing error] msg: Fatal Error: at file null line: 2 column: 359 message: An invalid XML character (Unicode: 0xb) was found in the CDATA section. 

Solution: 
Simply remove special characters from password and try again. It will work.

Wednesday, February 24, 2021

Unable to open opatch lsinventory due to error is not accessible. Please set appropriate JAVA_HOME and run again.

  Error :
    Unable to open opatch lsinventory due to error <JDK> is not accessible.
    Please set appropriate JAVA_HOME and run again.
     
  Solution:
      This error occurs when listing Weblogic Patches.
      This error occurs because of invalid path of JAVA_HOME.
      TO fix this change JAVA_HOME path in hidden file .globalEnv.properties present at $ORACLE_HOME/oui
     
      JAVA_HOME=<Latest JAVA_HOME Path>
   JAVA_HOME_1_8=<Latest JAVA_HOME Path>

Monday, December 14, 2020

Weblogic Server error OPatch failed with error code 255

Weblogic Server error OPatch failed with error code 255 If you get following error when attempting to list patches using opatch then try this solution. Note that I faced this error for Weblogic Server 12.2.1.3 after executing opatch lsinventory command. OPatch failed with error code 255 Solution: Most likely issue is due to JAVA and JRE path. If you are using Linux then export following two path and try again running opatch. export JAVA_HOME= export ORACLE_HOME= Please let me know if this helps you.

Monday, May 18, 2020

DeleteService failed - The specified service has been marked for deletion. (0x43

DeleteService failed - Error while deleting application server NT service


If you get following error while deleting PeopleSoft Application service then


DeleteService failed - The specified service has been marked for deletion. (0x43


Just sign-out or log off user session and connect to server again. The service will go away.



Tuesday, April 28, 2020

Windows Installer error during PeopleTools 8.57 installation on Windows and Linux Server through DPK

Error during PeopleTools 8.57 installation on Windows and Linux Server through DPK

Following error occurs sometimes when you are installing PeopleTools using DPK.


This error occurs during Puppet installation. It is because we have space in directory names where we have extracted DPK first zip file. E.g. d:\install dpk\setup.bat it should be d:\install_dpk\setup.bat
Hope this helps.

PeopleTools 8.57 installation on Windows Server through DPK

PeopleTools 8.57 installation on Linux Server through DPK

PeopleTools 8.57 has to be installed through DPK. Except PeopleTools everything else you can install manually in classic way. Following step will guide in details for PeopleTools 8.57 installation on Windows Server through DPK.

1. Extract first zip file of the linux DPK setup files inside DPK_INSTALL folder
 
2.Before you proceed for PeopleTools installation you will need to install Puppet software through admin user. If you wanted to installed PeopleTools through admin access then you don't need to install Puppet separately. Use following command if you wanted to install only Puppet using root user. Here we are proceeding to install puppet with PeopleTools installation.
 
3. Open the Windows Command prompt with admin rights. Change directory to DPK_INSTALL/setup
D:/DPK_INSTALL/setup>psft-dpk-setup.bat --env_type midtier --deploy_only --deploy_type tools_home

Starting the PeopleSoft Environment Setup Process:
 
Validating User Arguments:                                            [  OK  ]
Validating PeopleSoft Supported Platform:                             [  OK  ]
 
Extracting the Zip File PEOPLETOOLS-WIN-8.57.03_2of4.zip:             [  OK  ]
Extracting the Zip File PEOPLETOOLS-WIN-8.57.03_3of4.zip:             [  OK  ]
Extracting the Zip File PEOPLETOOLS-WIN-8.57.03_4of4.zip:             [  OK  ]
 
 
Verifying if Puppet Software is installed:
 
Puppet 5.3.5 is not installed on the Windows Host. If PeopleSoft
environment needs to be set up on this host, Puppet 5.3.5
must be installed.
 
Do you want to proceed with the Puppet 5.3.5 Installation? [Y|n]: y
Installing Puppet Software on the Windows Host:                       [  OK  ]
Installing eYAML Hiera Backend on the Windows Host:                   [  OK  ]
 
Preparing the Windows 2012ServerR2 VM for PeopleSoft Environment:
 
Checking if PeopleSoft DPKs are Present:                              [  OK  ]
 
The base folder is used to extract the PeopleSoft DPKs. It is also
used to deploy the PeopleSoft components. This folder should be
accessible on the Windows VM, must have write permission and should
have enough free space.
Enter the PeopleSoft Base Folder: D:/PS/PT857Base
Are you happy with your answer? [Y|n|q]: y
 
Checking if the Base Folder has Enough Free Space:
The PeopleSoft base folder [D:/PS/PT857Base] has only
X GB of disk space available. Please ensure it has at least
25 GB of free space for midtier.
 
 
 
Validating the PeopleSoft DPKs in the Windows VM:
Validating the PeopleSoft PeopleTools Server DPK:                     [  OK  ]
Validating the PeopleSoft PeopleTools Client DPK:                     [  OK  ]
 
Validating the Manifest Information in PeopleSoft DPKs:               [  OK  ]
 
Extracting the PeopleSoft DPK Archives in the Windows VM:
Extracting the PeopleSoft PeopleTools Server DPK Archives:            [  OK  ]
 
Setting up Puppet on the Windows VM:
Generating eYAML Hiera Backend Encryption Keys:                       [  OK  ]
Updating the Puppet Hiera YAML Files in the Windows VM:               [  OK  ]
Updating the Role in Puppet Site File for the Windows VM:             [  OK  ]
 
Enter the PeopleSoft database platform [ORACLE]: ORACLE
Is the PeopleSoft database unicode? [Y|n]: Y
 
Are you happy with your answers? [y|n]: y
Encrypting the Passwords in the User Data:
Updating the Puppet Hiera YAML Files with User Data:                  [  OK  ]
 
The bootstrap script is ready to deploy and configure the PeopleSoft
environment using the default configuration defined in the Puppet
Hiera YAML files. You can proceed by answering 'y' at the following
prompt. And, if you want to customize the environment by overriding
the default configuration, you can answer 'n'. If you answer 'n', you
should follow the instructions in the PeopleSoft Installation Guide
for creating the customization Hiera YAML file and running the Puppet
'apply' command directly to continue with the setup of the PeopleSoft
environment.
 
Do you want to continue with the default initialization process? [y|n]: n
 
You have decided not to continue with the default PeopleSoft environment
setup process. Any customizations to the PeopleSoft environment should be
done in the Hiera YAML file 'psft_customizations.yaml' and place it under
[D:/PS/PT857Base\dpk\puppet\production\data] folder. After making the
necessary customizations, run the following commands to continue with the
setup of PeopleSoft environment.
 
1. cd /d D:/PS/PT857Base\dpk\puppet\production\manifests
2. "C:\Program Files\Puppet Labs\Puppet\bin\puppet.bat" apply --confdir=D:/PS/PT857Base\dpk\puppet site.pp --debug --trace --detailed-exitcodes --logde
st /some_valid_path/to/log/psft_dpk_setup.log
 
Exiting the PeopleSoft environment setup process.
 The PeopleSoft Environment Setup Process Ended.
 

4.  Created following psft_customizations.yaml file and placed in data folder
 
---

ps_home:

db_type: "%{hiera('db_platform')}"

unicode_db: "%{hiera('unicode_db')}"

location: "D:/PSHOME"
 
5. Run the following command and PeopleTools 8.57 with patch will get installed.
 cd /d D:/PS/PT857Base\dpk\puppet\production\manifests
"C:\Program Files\Puppet Labs\Puppet\bin\puppet.bat" apply --confdir=D:/PS/PT857Base\dpk\puppet site.pp --debug --trace --detailed-exitcodes --logde
st d:/psft_dpk_setup.log
 
6. Next step is to configure the pscfg and attempt to connect target database through Application Designer.