pgAdmin won't start (eternal loading)

Question

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 Files\PostgreSQL\9.6\pgAdmin 4\bin\pgAdmin4.exe Faulting module path: MSVCP120.dll Report Id: 984dd9d8-13c4-11e7-832d-5ce0c535006f Faulting package full name: Faulting package-relative application ID:

Answer 1

I had the same problem and I resolved it following the steps on link https://www.pgadmin.org/faq/#12

When I launch pgAdmin 4 v4.28 or later on Windows, the loading page never closes. Why? pgAdmin 4 v4.28 includes additional security features, one of which is intended to prevent security issues caused by Content Sniffing.

Unfortunately some Windows systems are mis-configured such that this causes Javascripts used by pgAdmin to fail to load. Opening the developer tools on your browser will show an error similar to this:

Refused to execute script from 'http://127.0.0.1:57313/static/vendor/require/require.min.js?ver=42800' because its MIME type ('text/plain') is not executable, and strict MIME type checking is enabled.

(index):39 Uncaught ReferenceError: require is not defined at (index):39 This will occur when the value of the registry key at HKEY_CLASSES_ROOT.js\Content Type is set to text/plain. To resolve the issue, use the Registry Editor and reset the value of HKEY_CLASSES_ROOT.js\Content Type to: text/javascript

Finally, restart the pgAdmin server.