cancel
Showing results for 
Search instead for 
Did you mean: 

pgAdmin v4: The application server could not be contacted.

Level 3 Traveller

pgAdmin v4: The application server could not be contacted.

I'm new to PostgresSQL and to this list! I have installed version 10 64-bit (on Windows 7) I also used stackbuilder to install the ODBC drivers. The SQL shell allows me to logon to the server as postgres but when starting pgAdmin I get: The application  server could not be contacted. This a fatal error of course..... Any hint, tips or "Oh man you should have...." etc will be greatly appreciated.

/Richard

4 REPLIES
EDB Team Member

Re: pgAdmin v4: The application server could not be contacted.

Hi lepluc,

 

Can you check the required pg_hba.conf entry is present for pgAdmin4. 

Also if this is not the issue then, Can you please share the FATAL error which you are receiving?

 

Hope this helps.

 

-Regards 

Dhananjay 

Level 3 Traveller

Re: pgAdmin v4: The application server could not be contacted.

Hi  and thanks for the answer.

Well there is a file pg_hba.conf in the istallation, but not in the pgAdmin 4 subdirectory. The fatal error is a message box with the caption "Fatal Error" and the message "The application server could not be contacted." 

Regards

/Richard

EDB Team Member

Re: pgAdmin v4: The application server could not be contacted.

Hi lepluc,

 

The issue which you are facing may be solved by below workarounds listed below.

1) Start pgAdmin 4 using administrator.

Steps:
1. Right click pgAdmin 4 icon 
2. Select "Run As Administrator"

2) If running the pgadmin 4 by Administrator is not helpful in your case then try clearing out the "C:\Users\{YourUser}\AppData\Roaming\pgAdmin" folder. I believe it was attempting to use the sessions from the prior version and was failing.

 

Note: AppData\Roaming\pgAdmin is a hidden folder.

Hope this helps you.

EDB Team Member

Re: pgAdmin v4: The application server could not be contacted.

Hi lepluc,

 

Please let us know with your feedback that your able to resolve this issue.