Re: Error while starting PgAdmin 5.0

Julien,

The error itself is clear that it is being blocked by the
administrator. From version 5 onwards, pgAdmin4 desktop opens in a chromium
based NWJS container, no browser will be needed for opening the application.

You may need to change a user access control policy which Windows provides.
Currently, I don't have Windows 2019 or Windows 2012 to test, but a
snapshot of Windows server 2016 having nwjs extension entry.

[image: image.png]

I tried installing and executing the application on a non-admin user, and
it was successful.

Maybe chromium extensions are blacklisted on your machine. Whitelisting the
extension may solve your problem. You may need to approach your IT team to
get the help.

On Wed, Apr 28, 2021 at 11:33 AM Julien de Murcia <
demurcia(at)ockham-solutions(dot)fr> wrote:

> Hi,
>
> Here is the information I have:
>
> 1. The problem occurred with both pgAdmin4 5.0 installed from PG13.2 from
> Enterprise db installer, and pgAdmin4 5.2 installed from official website.
>
> 2. pgAdmin4 was not installed on these machines (they were previously
> running pg9.5 with pgAdmin3).
>
> 3. This is likely the issue, but I do not know what to look for exactly. I
> cannot make much experiments on these machines as they are production
> servers, admin restrictions and firewall cannot be disabled, and have no
> direct access to these servers anyway.
>
> 4. As far as I know, no log was generated. I will try to have a customer
> start pgAdmin4 5.x from console.
>
> I understand that this is very little information, my hope is that someone
> with his own server will report the same problem and provide more details.
> It should be easy to identify with the ID of the extension being blocked
> (in the displayed error message ID: cmifjmkpnpkdlfachldmblngbbmojlle). I
> will let you know if I can get more information.
>
> Thanks for your help.
> Le 27/04/2021 à 22:13, Rahul Shirsat a écrit :
>
> Julien,
>
> The above information is still not enough for us to determine the cause of
> the failure.
>
> You may troubleshoot what could be the problem by going through below
> points:
>
>
> 1. What is the download source of your pgAdmin4? (Recommended to
> download through our official website -
> https://www.pgadmin.org/download/)
> 2. Check whether there were any old versions of pgAdmin4 already
> installed, try uninstalling those first, and look for a pgAdmin4.db file in
> %APPDATA\pgAdmin\,
> if it exists, manually delete it as well.
> 3. Look out for all the firewalls / admin restrictions which are
> blocking from opening up the application.
> 4. Try sharing pgadmin4.startup or log files as mentioned in the above
> mail trace.
> 5. Checkout our faq page - https://www.pgadmin.org/faq/ for any other
> troubleshooting.
>
>
> On Tue, Apr 27, 2021 at 7:46 PM Julien de Murcia <
> demurcia(at)ockham-solutions(dot)fr> wrote:
>
>> We had a third case today (on windows 2012 server), with no pgAdmin log
>> generated. All the servers are running Sophos Antivirus, but it was
>> deactivated on the first server with no effect.
>> Le 23/04/2021 à 14:20, Julien de Murcia a écrit :
>>
>> Thanks for the info. Unfortunately, the customers did not find any
>> pgAdmin log files on their servers, but I do not have a remote access to
>> their machines to double check. I will see if this happens on other
>> servers. So far, it happened on two servers, one running on windows 2019
>> server and the other on windows 2008 server. The workaround is to install
>> pgAdmin 4.30.
>> Le 23/04/2021 à 12:17, Rahul Shirsat a écrit :
>>
>>
>> Log file is generated under C:\Users\<USER>\AppData\Local\pgadmin\ with
>> name pgadmin4.log. If the app itself is crashing, the logs inside
>> pgadmin4.startup are useful to determine why it is crashing. You may share
>> both if they exist.
>>
>> On Fri, Apr 23, 2021 at 3:24 PM Julien de Murcia <
>> demurcia(at)ockham-solutions(dot)fr> wrote:
>>
>>> Hi Rahul,
>>>
>>> Are you sure this log file is produced by PgAdmin 5.0 ? I do not have it
>>> on my own computer. It looks like a log file is generated under
>>> C:\Users\<USER>\AppData\Local\pgadmin but it is removed once PgAdmin is
>>> closed.
>>>
>>> Julien de Murcia
>>> Ingénieur développement Ockham Solutions
>>> Software engineer Ockham Solutions
>>> tel: +33 9 77 19 50 26
>>>
>>> Le 23/04/2021 à 10:46, Rahul Shirsat a écrit :
>>>
>>> Hi Julien,
>>>
>>> Could you please share the log files generated at - C:\Users\<USER>\AppData\Local
>>> with name 'pgadmin4.startup' ?
>>>
>>> On Thu, Apr 22, 2021 at 8:17 PM Julien de Murcia <
>>> demurcia(at)ockham-solutions(dot)fr> wrote:
>>>
>>>> Hello,
>>>>
>>>> When starting PgAdmin 5.0 as Desktop app on Windows 2019 server, some
>>>> of
>>>> my customers are getting the following error message:
>>>> "L'administrateur a bloqué l'extension pgAdmin 4(ID :
>>>> cmifjmkpnpkdlfachldmblngbbmojlle)"
>>>> Sorry, the message is in French. AFAIK it comes from Chromium, which is
>>>> complaining about the extension pgAdmin 4 being blocked by the
>>>> administrator.
>>>> Unfortunately, I could not reproduce the issue on my environment.
>>>> According to our users, no log is generated under %AppData%\pgAdmin. Is
>>>> there any log file I could check to understand what is blocking the
>>>> extension ? Is this a known problem (incompatibility with security
>>>> tools
>>>> or rules) ?
>>>>
>>>> Best regards,
>>>>
>>>> --
>>>> Julien de Murcia
>>>>
>>>>
>>>>
>>>>
>>>
>>> --
>>> *Rahul Shirsat*
>>> Senior Software Engineer | EnterpriseDB Corporation.
>>>
>>>
>>
>> --
>> *Rahul Shirsat*
>> Senior Software Engineer | EnterpriseDB Corporation.
>>
>>
>
> --
> *Rahul Shirsat*
> Senior Software Engineer | EnterpriseDB Corporation.
>
>

--
*Rahul Shirsat*
Senior Software Engineer | EnterpriseDB Corporation.