Pgadmin 4 ошибка при запуске - ErrorsMaster.ru - большая энциклопедия ошибок и их решений

При запуске pgAdmin выдает ошибку

The application server could not be contacted

но если запустит pgAdmin 3 все загружается,

При повторном запуске pgAdmin 4 этой ошибки нет,все загружается.

Kosta B.

5,8113 золотых знака14 серебряных знаков24 бронзовых знака

задан 12 июн 2018 в 18:12

Антон ПрохоровАнтон Прохоров

3131 золотой знак2 серебряных знака11 бронзовых знаков

Перезапустите службу postgres.

ответ дан 27 июл 2018 в 6:37

Я не знаю поможет ли это кому-то, но всё же напишу тут, дорогой читатель. Если не помогли такие методы, как:
-попробуйте запустить PgAdmin отмени администратора.
-добавьте путь к bin-папке Postgresql в переменные окружения.
-очистите папку C:Users%USERNAME%AppDataRoamingpgAdmin
-перезапустите службу

То проверьте имя и описание своего компьютера, если заданы значения на русском, то измените их на латинские буквы, затем всё полностью удалите и переустановите, мне помогло.

ответ дан 19 июл 2019 в 17:19

Win7_x64 pgAdmin 4.21 — при такой ошибке помогло задать латинское имя компьютера, с перезагрузкой

ответ дан 31 мая 2020 в 10:15

Источник

Once upon a time I had a Postgres database that worked with pgAdmin. I have a webservice running on a WildFly server that made connections to the DB and everything worked fine.

After a while(a few months) I have tried to open pgAdmin again and it stuck on the loading…

I remove postgres and pgAdmin using Revo Uninstall, then installed postgres 9.6 and opened pgAdmin and it stays in the loading screen forever.

Can anyone help me ? [Using postgres 9.6 with pgAdmin v1.3],

On Event Viewer I saw the following error in pgAdmin :

Faulting application name: pgAdmin4.exe, version: 0.0.0.0, time stamp: 0x580f31f6
Faulting module name: MSVCP120.dll, version: 6.3.9600.18438, time stamp: 0x57ae642e
Exception code: 0xc0000135
Fault offset: 0x00000000000ecdd0
Faulting process id: 0x1de4
Faulting application start time: 0x01d2a7d1566324ba
Faulting application path: C:Program FilesPostgreSQL9.6pgAdmin 4binpgAdmin4.exe
Faulting module path: MSVCP120.dll
Report Id: 984dd9d8-13c4-11e7-832d-5ce0c535006f
Faulting package full name:
Faulting package-relative application ID:

Источник

In this guide, we’ll walk you through the process of troubleshooting the «The pgAdmin 4 server could not be contacted» error. This error usually occurs when you’re trying to use the pgAdmin 4 tool to manage your PostgreSQL databases, but the server is unable to establish a connection with pgAdmin.

Follow the steps below to resolve the issue:

Step 1: Check the PgAdmin 4 Configuration File

First, make sure that your pgAdmin 4 configuration file is set up correctly.

Open the config_local.py or config.py file located in the pgAdmin 4 installation folder. The default location is:

Windows: C:Program FilespgAdmin 4v5web
macOS: /Library/PostgreSQL/pgAdmin 4/web
Linux: /usr/local/lib/python3.x/dist-packages/pgadmin4

Verify that the SERVER_MODE and ALLOWED_HOSTS settings are configured correctly. For example, if you’re running pgAdmin 4 in server mode, your configuration should look like this:

SERVER_MODE = True
ALLOWED_HOSTS = ['*']

If you’re running pgAdmin 4 in desktop mode, your configuration should look like this:

SERVER_MODE = False
ALLOWED_HOSTS = ['localhost', '127.0.0.1']

Save the configuration file and restart pgAdmin 4.

Step 2: Verify the PgAdmin 4 Service Status

Make sure the pgAdmin 4 service is running correctly.

Windows: Open the «Services» application and look for the «pgAdmin 4» service. Ensure that its status is set to «Running.»

macOS: Open the «Activity Monitor» and search for «pgAdmin.» Ensure that the process is running.

Linux: Run the following command in the terminal:

systemctl status pgadmin4

Ensure that the service is «active (running).»

Step 3: Check Firewall and Antivirus Settings

Your firewall or antivirus software might be blocking the connection between pgAdmin 4 and the server. Temporarily disable your firewall and antivirus software, then try connecting again. If the issue is resolved, create exceptions for pgAdmin 4 in your firewall and antivirus settings.

Step 4: Examine Log Files

If the issue persists, examine the log files to identify any error messages or other relevant information. The log files are located in the following directories:

Windows: C:UsersYourUsernameAppDataRoamingpgAdminpgadmin.log
macOS: ~/Library/Application Support/pgAdmin/pgadmin.log
Linux: ~/.pgadmin/pgadmin.log

Frequently Asked Questions (FAQs)

How do I install pgAdmin 4?

Refer to the official pgAdmin 4 documentation for detailed installation instructions for your specific operating system.

How do I update pgAdmin 4 to the latest version?

To update pgAdmin 4, simply download the latest version from the pgAdmin 4 download page and follow the installation instructions.

Can I use pgAdmin 4 to manage multiple PostgreSQL servers?

Yes, pgAdmin 4 supports managing multiple PostgreSQL servers. You can add multiple servers by clicking on the «Add New Server» button in the «Servers» tab.

Why is my pgAdmin 4 interface slow or unresponsive?

This issue might be due to insufficient system resources or an outdated version of pgAdmin 4. Try closing other applications to free up system resources, or update pgAdmin 4 to the latest version.

Can I use pgAdmin 4 with other databases like MySQL or Oracle?

No, pgAdmin 4 is specifically designed for managing PostgreSQL databases. To manage other databases, consider using alternative tools such as MySQL Workbench for MySQL or Oracle SQL Developer for Oracle.

PgAdmin 4 Official Documentation
PostgreSQL Official Documentation
PgAdmin 4 Configuration
PgAdmin 4 Troubleshooting Guide

Источник

Пишет ошибка системы (class oserror), 10013, сделана ошибка доступа к совету методом, запрещённым правами доступа

Добавлено через 20 секунд
Запускаю с админ-правами
Видимо где-то какое-то разрешение не поставлено

Добавлено через 39 минут
Итак решение проблемы было следующим, для тех, кто столкнется:
Заходим в Users/ваш юзер/appdata/roaming/pgadmin, открываем файл логов pgadmin4.txt, смотрим ошибку
У меня была 10013
Причина ошибки либо недостаток прав, либо занятость порта другими процессами
Почистил и поотключал антивирусы, не помогло
Командой netstat -ano узнал id процесса на порту 5432 (порт postgresql), узнал его id (столбец PID)
Дальше ctrl+shift+esc открываем диспетчер задач, вкладка подробности и смотрим, каким процессом занят порт с нужным id (у меня id был 12856), кликаем на процесс и жмём снять задачу
Запускаем заново pgadmin4, у меня все заработало

Источник

I installed PostgreSQL on Windows 10 and the server appears to be in Task Manager. However, I get this error when opening pgAdmin4:

Failed to connect to the pgAdmin application server. Click here to try again.

Any ideas for what the problem is?

asked Jul 6, 2016 at 13:30

Did you try running the pgAdmin application as an administrator ?
I was having the same issue, but ran the application as an administrator and was able to connect.

answered Oct 3, 2016 at 8:24

RitzRitz

1411 silver badge3 bronze badges

I installed pgAdmin 4 via the EnterpriseDB PostgreSQL installer as well as the stand-alone Windows installer and had the same problem both times. Then I came across this: https://www.pgadmin.org/docs4/dev/desktop_deployment.html

It seems the Windows installer configures pgAdmin for server mode, and we need to switch it to Desktop mode. Why the installer does not have an option for this I do not know.

You should be able to getting it working by doing the following:

Modify config_local.py file in web folder, adding SERVER_MODE = False
Install python for windows, checking the box to add it to your path
Install the python packages necessary to run setup.py (see below)
Delete C:Users%USERNAME%AppDataRoamingpgAdminpgadmin4.db since upgrade mode seems to not work.
Run python setup.py from any command prompt

Here are the python packages I think I installed to get setup.py to work

pip install flask
pip install flask_security
pip install flask_babel
pip install django-htmlmin
pip install python-dateutil
pip install flask_sqlalchemy

answered Oct 6, 2016 at 3:44

rougourougou

1811 silver badge2 bronze badges

I had the same problem with pgAdmin 4 1.6 on Windows 7. The solution was simply to delete %appdata%pgAdmin which was created by an earlier version. On systems other than Windows, there probably is a pgAdmin directory in your user directory. Of course, all session settings etc. are gone after deleting this.

answered Jul 14, 2017 at 7:21

I had the same problem with pgadmin 3.0 on windows server 2016. What I did is not actually a solution but solved my problem at, least. I switch to an older version 2.1 that worked like a charm.

answered May 13, 2018 at 15:40

Источник