Question
Pega Personal Edition v8.6: Postgre not able to connect on 5432
Not able to install Pega Personal edition, tried in multiple laptops but having same issue.
Aug 10, 2021 12:59:21 AM org.postgresql.Driver connect SEVERE: Connection error: org.postgresql.util.PSQLException: Connection to localhost:5432 refused. Check that the hostname and port are correct and that the postmaster is accepting TCP/IP connections.
Note
1. This is first time installation and the idea of older pega versions will not be applicable(might not be below issue).
https://collaborate.pega.com/question/issue-pega-81-installation
Solutions attempted.
1. Tried to check JVM Parameters
***Edited by Moderator Kayla to update Platform Capability tags****
Updated: 16 Aug 2021 0:15 EDT
Central Provident Fund Board
IN
@ykv05 :
Hi Moderators,
Requesting your assitance to check with technical team on this, i can share screenshots and logs if required.
Below is my laptop configuration
Model : Acer, Windows 10
Architecture : 64bit, Ram : 16 GB, HDD 1 TB(available space more than 200 GB)
Thank you.
Updated: 22 Jun 2022 10:06 EDT
Pegasystems Inc.
GB
Can you confirm that you are following all the steps listed here?
Installing the Pega Platform Personal Edition | Pega
In particular:
Click Port Availability to verify that the default ports are available. If there are conflicts, enter a different port number and repeat this step.
-
If you are installing on Windows 10, ensure that the Windows firewall includes exceptions for the ports you select.
Solution 1 : install the latest version of pgadmin then proceed to install.
Also please check if the postgres db starts up correctly first.
You need to make sure you are starting the DB server using below command and then starting the tomcat instance-
D:\PRPCPersonalEdition\pgsql\bin>pg_ctl -D D:\PRPCPersonalEdition\pgsql\data start
Above highlighted could change based on the personal edition installation.
Solution 2: installing the Microsoft Visual C++ 2015 Redistributable Update 3 RC program.
Can you confirm that you are following all the steps listed here?
Installing the Pega Platform Personal Edition | Pega
In particular:
Click Port Availability to verify that the default ports are available. If there are conflicts, enter a different port number and repeat this step.
-
If you are installing on Windows 10, ensure that the Windows firewall includes exceptions for the ports you select.
Solution 1 : install the latest version of pgadmin then proceed to install.
Also please check if the postgres db starts up correctly first.
You need to make sure you are starting the DB server using below command and then starting the tomcat instance-
D:\PRPCPersonalEdition\pgsql\bin>pg_ctl -D D:\PRPCPersonalEdition\pgsql\data start
Above highlighted could change based on the personal edition installation.
Solution 2: installing the Microsoft Visual C++ 2015 Redistributable Update 3 RC program.
The issue may be that the pg_ctl executable is not able to run due to the VCRUNTIME140.dll being missing in the Windows System. This error is not exclusive of the pg_ctl command but it seems to be common for other programs that need that DLL to run correctly.
Check this links for more details about this error:
https://softwarekeep.com/help-center/how-to-fix-the-vcruntime140dll-is-missing-error-on-windows-10
You can download the executable from this site:
https://www.microsoft.com/en-us/download/details.aspx?id=52685
Solution 3: Check that there is not an older version of pega files already existing in your PC.
Remove those files first.
Solution 4: try completely deleting the contents of following directory
C:\PRPCPersonalEdition\tomcat\kafka-data , if you are using a VPN or dynamic IP, the IP address of you machine is cached by Kafka which creates this problem.
Clean restart of Pega PE after clearing off this folder
https://www.pgadmin.org/download/pgadmin-4-windows/
During the installation be sure to test the ports:
After it's installed and running you could use TCPView (or similar utility) to confirm that postgres is running at port 5432:
Solution 5: Check your jvm parameters like heapspace and permgen. Incase of tomcat it would present in setenv.bat/.sh file.