Installing PeopleSoft on your desktop/laptop frankly is very easy as the installation document is pretty comprehensive. However, most of the time the installation won’t go smooth at first go, unless you proactively take care of the few things (list below) right upfront at the minimum -
- Minimum Hardware Requirements
- Ping FQDN (Fully Qualified Domain Name)
- Prior Installation (if any) cleanup
- Appropriate permissions to the BASE_DIR folder
I totally recommend, going over this bear minimum steps (prior to the installation) as this will save a ton of time troubleshooting a failed installation.
Minimum Hardware Requirements
If your desktop/laptop does not meet any of the hardware requirements mentioned above, please do not proceed with PeopleSoft installation.
Ping FQDN (Fully Qualified Domain Name)
PeopleSoft Installation by default captures the FQDN, normally if you are able to ping the hostname one should be able to ping FQDN as well. But, with Windows 10 we see an issue where you can successfully ping hostname but can't ping FQDN. Here are the steps to verify and also fix FQDN ping.
Click on "Start" and type "Command Line", open "Command Line" by right clicking and opening it as "Run as Administrator"
Type command "ipconfig /all"
Concise version of the screen shot shown above where you can see the "hostname" and the "Connection-specific DNS Suffix".
Fully Qualified Domain Name = Hostname + Connection-specific DNS Suffix
In this case, the FQDN is DSKTPHOST.company.com
Let's try and ping, the hostname as well as FQDN, if you are able to successfully ping the host as well as FQDN you can skip this section and go to next step else stick around as we resolve FQDN issue
Ping Hostname
Ping FQDN
As you can see above, I was successfully able to ping the hostname but not able to ping the Fully Qualified Domain Name.
**If you proceed with your PeopleSoft Installation without resolving FQDN ping issue, your installation will surely fail at "Deploying Oracle Database Server" step.
One of the way to fix FQDN ping is by adding the IP details to the host file.
Navigate to C:\Windows\System32\drivers\etc
Open the "hosts" file in notepad (run as administrator)
Add the following entry to the hosts file
Ofcourse, you will have to change the details to reflect the correct IP, FQDN & Hostname.
Save the "hosts" file and then let's try to ping the ping FQDN again.
There you go, we are now able to successfully resolve FQDN
Prior Installation (if any) cleanup
If you have ever attempted PeopleSoft installation on this machine then this is an atmost important step as if you haven't followed the cleanup step you are sure to get an error when attempting for another PeopleSoft environment installation.
So, let's go through the steps to cleanup your prior installation
**This section assumes that you have downloaded the Native OS PeopleSoft PUM image and unzipped the 1st zip file (If you haven't downloaded the Native OS PeopleSoft PUM image, please go through my other blog on Installing PeopleSoft Native OS on Windows Host)
Step1: Run the command "psft-dpk-setup.bat --cleanup" under DPK_INSTALL\setup
Step2: If the script displays a FAILED message, run it again
Step3: If it succeeds, check the BASE_DIR folders to be sure everything has been deleted
**BASE_DIR is the directory where your previous version was installed.
Step4: In either case where the above script was executed Successfully or Failed, I would recommend reviewing/following the steps below.
Step5: Delete all Folders/Files under the BASE_DIR folder
Step6: Delete Services
- Go to "Services" by typing "Services" after clicking on the Start button
- Stop the following services
- OracleServiceCDB<Product>
- OracleOraDB12cHomeTNSListener<Listener_Name>
- ORACLE ProcMGR V12.2.2.0.0_VS2015
- TListen12.2.2.0.0_VS2015(Port3050)
- PsftAppServerDomain<Appserver_domain_name>Service
- PsftPrcsDomain<ProcSched_domain_name>Service
- PsftPIADomain<PIA_domain_name>Service
- Open Command Prompt and execute the following following for each of the services that were stopped on the above step
sc delete <service_name>
Step7: Cleanup Registry
- In the Registry Editor, locate the HKLM\SOFTWARE\ORACLE folder
- Select the following keys and verify that they contain references to the DPK installation locations in BASE_DIR, if yes delete these keys:
- KEY_OraDB12cHome (BASE_DIR\db by default)
- KEY_OraTux1222Home (BASE_DIR\pt\bea\tuxedo by default)
- KEY_OraWL12213Home (BASE_DIR\pt\bea by default)
- In the Registry Editor, locate the HKLM\SOFTWARE\ORACLE\TUXEDO folder
- Select the 12.2.2.0.0_VS2015 key and verify that it contains references to the DPK installation locations in BASE_DIR (BASE_DIR\pt\bea\tuxedo by default), if yes delete this key.
Step8: Cleanup Environment Variables
- Go to "Edit the Environment Variables"
- Remove any references to BASE_DIR folder under "System Variables".
- Ensure that the PathText variable is configured as shown below
PATHEXT=.COM;.EXE;.BAT;.CMD;.VBS;.VBE;.JS;.JSE;.WSF;.WSH;.MSC
Step9: Cleanup inventory.xml
- Open the file C:\Program Files\Oracle\Inventory\ContentsXML\inventory.xml in a text editor
- Locate the lines that reference the DPK deployment
- Delete only the lines referencing the DPK deployment, and save the file
Step10: Remove C:/User/<username>/psft/pt/8.57 (PS_CFG_HOME).
Appropriate permissions to the BASE_DIR folder
If you have performed all of the above steps and if you are still getting failures/errors during PeopleSoft Installation its likely going to permissions issue to the BASE_DIR folder. Hence, make sure you have administrative permissions to the BASE_DIR folder before beginning your PeopleSoft Installation.
**I'm not elaborating this section as there are various blogs to assign administrative permissions or taking ownership of a folder on Windows 10.
Hopefully, this blog will help you save ton of time troubleshooting.
Best of Luck with your PeopleSoft Installation|
Please let me know if this post was helpful in the comments section below!
Please let me know if this post was helpful in the comments section below!
No comments:
Post a Comment