Thread: PgAdmin 4 not working in Windows 10
<div class="WordSection1"><p class="MsoNormal">Hi,<p class="MsoNormal"> <p class="MsoNormal">I have recently installed thenew Postgres 9.6 RC1, having previously used 9.2, 9.4, and 9.5 extensively for all our business activities.<p class="MsoNormal"> <pclass="MsoNormal">As a test, I performed a pg_upgrade to create a new copy of several databases on 9.6RC1. All fine.<p class="MsoNormal"> <p class="MsoNormal">However PgAdmin 4 always crashed with the usual ‘PgAdmin stoppedworking’ message that it has always been prone to – but this time whenever I try to open ANY database.<p class="MsoNormal"> <pclass="MsoNormal">I spent several hours installed Python in case it needed that to run correctly, andthis seemed to improve things – it now crashes only every 10 minutes or so. But now it’s gone back to crashing wheneverI open a database again.<p class="MsoNormal"> <p class="MsoNormal">So Question 1: Where is the pg_admin log now beingstored if anywhere – if not, where can I set its path so I can see what’s happening?<p class="MsoNormal">Question 2– why doesn’t pgAdmin 4 for windows 10 work?<p class="MsoNormal"> <p class="MsoNormal">Since we use the Express for WindowsDesktop version of Visual Studio 2015, the path to the debugger seems unavailable – have you any suggestions how tofind out what is going wrong?<p class="MsoNormal"> <p class="MsoNormal">I am happy to return to 9.5 for the moment, butI was really looking forward to using the new interface, and implementing it for all our users across the country.<p class="MsoNormal"> <pclass="MsoNormal">Sadly,<p class="MsoNormal"> <p class="MsoNormal">Nigel<p class="MsoNormal"> <p class="MsoNormal"><b><spanstyle="font-size:12.0pt;mso-fareast-language:EN-NZ">Dr Nigel Tucker</span></b><p class="MsoNormal"><spanstyle="mso-fareast-language:EN-NZ">System Architect</span><p class="MsoNormal"><span style="mso-fareast-language:EN-NZ">SpecialisedStructures NZ</span><p class="MsoNormal"><span style="mso-fareast-language:EN-NZ">TelephoneDirect (NZ) +64 (0) 3 482 2473</span><p class="MsoNormal"><span style="mso-fareast-language:EN-NZ"> </span><pclass="MsoNormal"><span style="mso-fareast-language:EN-NZ"> <img alt="SS with Custom" height="255" id="Picture_x0020_1" src="cid:image001.jpg@01D21C74.21FF9DF0"width="453" /></span><p class="MsoNormal"> </div>
Hi,
I have recently installed the new Postgres 9.6 RC1, having previously used 9.2, 9.4, and 9.5 extensively for all our business activities.
As a test, I performed a pg_upgrade to create a new copy of several databases on 9.6 RC1. All fine.
However PgAdmin 4 always crashed with the usual ‘PgAdmin stopped working’ message that it has always been prone to – but this time whenever I try to open ANY database.
I spent several hours installed Python in case it needed that to run correctly, and this seemed to improve things – it now crashes only every 10 minutes or so. But now it’s gone back to crashing whenever I open a database again.
So Question 1: Where is the pg_admin log now being stored if anywhere – if not, where can I set its path so I can see what’s happening?
Question 2 – why doesn’t pgAdmin 4 for windows 10 work?
Since we use the Express for Windows Desktop version of Visual Studio 2015, the path to the debugger seems unavailable – have you any suggestions how to find out what is going wrong?
I am happy to return to 9.5 for the moment, but I was really looking forward to using the new interface, and implementing it for all our users across the country.
Sadly,
Nigel
Dr Nigel Tucker
System Architect
Specialised Structures NZ
Telephone Direct (NZ) +64 (0) 3 482 2473
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
Attachment
Hi Dave,
I am delighted to report that the new release of pgAdmin4 version 1.1 dated Nov 23 2016 has resolved my long-standing troubles with crashes when I open a database with pgAdmin. I had it yesterday running for 24 hours without failure. Up to then this product had been quite unusable on my work PC.
Nigel
Dr Nigel Tucker
System Architect
Specialised Structures NZ
Telephone Direct (NZ) +64 (0) 3 482 2473
From: Dave Page [mailto:dpage@pgadmin.org]
Sent: Thursday, 6 October 2016 9:27 PM
To: Nigel Tucker
Subject: Re: [pgadmin-support] PgAdmin 4 not working in Windows 10
Hi
Please keep the mailing list CC'd, or I won't be able to help any further.
Do you have another machine you can test on?
On Wed, Oct 5, 2016 at 8:27 PM, Nigel Tucker <nigel@specialisedstructures.co.nz> wrote:
Hi Dave,
Sorry – I did as you asked but it immediately refused to open the database and crashed as below:
From Event Viewer:
Faulting application name: pgAdmin4.exe, version: 0.0.0.0, time stamp: 0x57ece68d
Faulting module name: Qt5WebKit.dll, version: 5.5.1.0, time stamp: 0x561c1e4c
Exception code: 0xc0000005
Fault offset: 0x005153f0
Faulting process ID: 0x1a1c
Faulting application start time: 0x01d21f396b0a3b73
Faulting application path: C:\Program Files (x86)\pgAdmin 4\v1\runtime\pgAdmin4.exe
Faulting module path: C:\Program Files (x86)\pgAdmin 4\v1\runtime\Qt5WebKit.dll
Report ID: ff0e2caf-0027-4d23-982e-3a19adf33f61
Faulting package full name:
Faulting package-relative application ID:
Details
pgAdmin4.exe |
0.0.0.0 |
57ece68d |
Qt5WebKit.dll |
5.5.1.0 |
561c1e4c |
c0000005 |
005153f0 |
1a1c |
01d21f396b0a3b73 |
C:\Program Files (x86)\pgAdmin 4\v1\runtime\pgAdmin4.exe |
C:\Program Files (x86)\pgAdmin 4\v1\runtime\Qt5WebKit.dll |
ff0e2caf-0027-4d23-982e-3a19adf33f61 |
Last line in pgAdmin4.Log:
2016-10-06 08:20:03,411: INFO werkzeug: 127.0.0.1 - - [06/Oct/2016 08:20:03] "GET /dashboard/ti_stats/2 HTTP/1.1" 200 –
Cheers
Nigel
Dr Nigel Tucker
System Architect
Specialised Structures NZ
Telephone Direct (NZ) +64 (0) 3 482 2473
From: Dave Page [mailto:dpage@pgadmin.org]
Sent: Thursday, 6 October 2016 3:10 AM
To: Nigel Tucker
Subject: Re: [pgadmin-support] PgAdmin 4 not working in Windows 10
Hi,
Please keep the mailing list CC'd.
Can you please try the standalone pgAdmin installer from https://www.postgresql.org/ftp/pgadmin3/pgadmin4/v1.0/windows/? I want to see if this is related to the build process (the standalone installers use a very different process from the EDB ones, and this looks like it might be a Qt issue from the info you've provided).
It won't interfere with your existing installation, except in that it'll use the same config and log file etc.
Thanks.
On Wed, Oct 5, 2016 at 4:58 AM, Nigel Tucker <nigel@specialisedstructures.co.nz> wrote:
Hi Dave,
I have been successful in running the latest PgAdmin all day up to now/ But it’s now returned to its old tricks. I have restarted the server, tried three times with pgAdmin 4 and each time it gives me a similar error on clicking on a database on the localhost.
Any ideas? I attach the Report.wer file automatically generated.
Event viewer shows:
Faulting application name: pgAdmin4.exe, version: 0.0.0.0, time stamp: 0x57ea0209
Faulting module name: Qt5WebKit.dll, version: 5.5.1.0, time stamp: 0x561c21e5
Exception code: 0xc0000005
Fault offset: 0x0000000000656a0c
Faulting process ID: 0x24a4
Faulting application start time: 0x01d21ebb74b91b8c
Faulting application path: F:\PostgreSQL\9.6\pgAdmin 4\bin\pgAdmin4.exe
Faulting module path: F:\PostgreSQL\9.6\pgAdmin 4\bin\Qt5WebKit.dll
Report ID: 5d8e33d7-643b-4605-b333-e275fa34eb97
Faulting package full name:
Faulting package-relative application ID:
Fault bucket 120562057157, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0
Problem signature:
P1: pgAdmin4.exe
P2: 0.0.0.0
P3: 57ea0209
P4: Qt5WebKit.dll
P5: 5.5.1.0
P6: 561c21e5
P7: c0000005
P8: 0000000000656a0c
P9:
P10:
Attached files:
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER22FE.tmp.WERInternalMetadata.xml
\\?\C:\Users\Plan-It Test\AppData\Local\Temp\WER2EE6.tmp.appcompat.txt
\\?\C:\ProgramData\Microsoft\Windows\WER\Temp\WER2F54.tmp.mdmp
\\?\C:\Users\Plan-It Test\AppData\Local\Temp\WER3466.tmp.WERDataCollectionFailure.txt
These files may be available here:
C:\ProgramData\Microsoft\Windows\WER\ReportArchive\AppCrash_pgAdmin4.exe_56d2f47cc3652cd8762dd8b03fb84c5b4a145b67_1456a217_31405410
Analysis symbol:
Rechecking for solution: 0
Report ID: 5d8e33d7-643b-4605-b333-e275fa34eb97
Report Status: 4104
Hashed bucket: 6fc72a316d292b3487cc89f4b7f90a8d
Cheers
Nigel
Dr Nigel Tucker
System Architect
Specialised Structures NZ
Telephone Direct (NZ) +64 (0) 3 482 2473
From: Dave Page [mailto:dpage@pgadmin.org]
Sent: Monday, 3 October 2016 10:18 PM
To: Nigel Tucker
Cc: pgAdmin Support
Subject: Re: [pgadmin-support] PgAdmin 4 not working in Windows 10
Hi
On Sat, Oct 1, 2016 at 6:13 PM, Nigel Tucker <nigel@specialisedstructures.co.nz> wrote:
Hi,
I have recently installed the new Postgres 9.6 RC1, having previously used 9.2, 9.4, and 9.5 extensively for all our business activities.
As a test, I performed a pg_upgrade to create a new copy of several databases on 9.6 RC1. All fine.
However PgAdmin 4 always crashed with the usual ‘PgAdmin stopped working’ message that it has always been prone to – but this time whenever I try to open ANY database.
I'm not aware that it's always been prone to that. I've seen one or two reports, but that was amongst over 500 issues during development..
I spent several hours installed Python in case it needed that to run correctly, and this seemed to improve things – it now crashes only every 10 minutes or so. But now it’s gone back to crashing whenever I open a database again.
Unless you've modified the config options, then installing Python won't make any difference. The runtime itself (which is the bit that would give the message above) is written in C++, and is linked with the Python interpreter at build time.
So Question 1: Where is the pg_admin log now being stored if anywhere – if not, where can I set its path so I can see what’s happening?
Under the %AppData% directory, e.g. C:\Users\dpage\AppData\Roaming\pgAdmin\pgadmin.log. You can change that in config_local.py (see config.py for the default setting, which you can copy/paste into config_local.py to override).
Note that that is the log for the application server, i.e the Python code that is hosted in the runtime. The runtime doesn't have it's own log, besides what you might find in the event viewer.
Question 2 – why doesn’t pgAdmin 4 for windows 10 work?
It does for thousands of other people (at least we assume it does - they're keeping quiet if it doesn't). Of course there are always exceptions where some unexpected environmental issue causes problems.
Since we use the Express for Windows Desktop version of Visual Studio 2015, the path to the debugger seems unavailable – have you any suggestions how to find out what is going wrong?
It does sound like a runtime issue. You could install Qt, then try compiling/debugging your own build of the runtime. I'd hold on that option for the moment though, as it can take a little effort to setup a build environment.
Before you do anything else though, please make sure you upgrade to PostgreSQL 9.6.0 and pgAdmin 4 1.0 (i.e. the GA versions, not RC1).
I am happy to return to 9.5 for the moment, but I was really looking forward to using the new interface, and implementing it for all our users across the country.
Sadly,
Nigel
Dr Nigel Tucker
System Architect
Specialised Structures NZ
Telephone Direct (NZ) +64 (0) 3 482 2473
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
Attachment
Hi Dave,
I am delighted to report that the new release of pgAdmin4 version 1.1 dated Nov 23 2016 has resolved my long-standing troubles with crashes when I open a database with pgAdmin. I had it yesterday running for 24 hours without failure. Up to then this product had been quite unusable on my work PC.
Nigel
Dr Nigel Tucker
System Architect
Specialised Structures NZ
Telephone Direct (NZ) +64 (0) 3 482 2473
From: Dave Page [mailto:dpage@pgadmin.org]
Sent: Thursday, 6 October 2016 9:27 PM
To: Nigel Tucker
Subject: Re: [pgadmin-support] PgAdmin 4 not working in Windows 10
Hi
Please keep the mailing list CC'd, or I won't be able to help any further.
Do you have another machine you can test on?
On Wed, Oct 5, 2016 at 8:27 PM, Nigel Tucker <nigel@specialisedstructures.
co.nz> wrote: Hi Dave,
Sorry – I did as you asked but it immediately refused to open the database and crashed as below:
From Event Viewer:
Faulting application name: pgAdmin4.exe, version: 0.0.0.0, time stamp: 0x57ece68d
Faulting module name: Qt5WebKit.dll, version: 5.5.1.0, time stamp: 0x561c1e4c
Exception code: 0xc0000005
Fault offset: 0x005153f0
Faulting process ID: 0x1a1c
Faulting application start time: 0x01d21f396b0a3b73
Faulting application path: C:\Program Files (x86)\pgAdmin 4\v1\runtime\pgAdmin4.exe
Faulting module path: C:\Program Files (x86)\pgAdmin 4\v1\runtime\Qt5WebKit.dll
Report ID: ff0e2caf-0027-4d23-982e-
3a19adf33f61 Faulting package full name:
Faulting package-relative application ID:
Details
pgAdmin4.exe
0.0.0.0
57ece68d
Qt5WebKit.dll
5.5.1.0
561c1e4c
c0000005
005153f0
1a1c
01d21f396b0a3b73
C:\Program Files (x86)\pgAdmin 4\v1\runtime\pgAdmin4.exe
C:\Program Files (x86)\pgAdmin 4\v1\runtime\Qt5WebKit.dll
ff0e2caf-0027-4d23-982e-
3a19adf33f61
Last line in pgAdmin4.Log:
2016-10-06 08:20:03,411: INFO werkzeug: 127.0.0.1 - - [06/Oct/2016 08:20:03] "GET /dashboard/ti_stats/2 HTTP/1.1" 200 –
Cheers
Nigel
Dr Nigel Tucker
System Architect
Specialised Structures NZ
Telephone Direct (NZ) +64 (0) 3 482 2473
From: Dave Page [mailto:dpage@pgadmin.org]
Sent: Thursday, 6 October 2016 3:10 AM
To: Nigel Tucker
Subject: Re: [pgadmin-support] PgAdmin 4 not working in Windows 10
Hi,
Please keep the mailing list CC'd.
Can you please try the standalone pgAdmin installer from https://www.postgresql.
org/ftp/pgadmin3/pgadmin4/v1. 0/windows/? I want to see if this is related to the build process (the standalone installers use a very different process from the EDB ones, and this looks like it might be a Qt issue from the info you've provided).
It won't interfere with your existing installation, except in that it'll use the same config and log file etc.
Thanks.
On Wed, Oct 5, 2016 at 4:58 AM, Nigel Tucker <nigel@specialisedstructures.
co.nz> wrote: Hi Dave,
I have been successful in running the latest PgAdmin all day up to now/ But it’s now returned to its old tricks. I have restarted the server, tried three times with pgAdmin 4 and each time it gives me a similar error on clicking on a database on the localhost.
Any ideas? I attach the Report.wer file automatically generated.
Event viewer shows:
Faulting application name: pgAdmin4.exe, version: 0.0.0.0, time stamp: 0x57ea0209
Faulting module name: Qt5WebKit.dll, version: 5.5.1.0, time stamp: 0x561c21e5
Exception code: 0xc0000005
Fault offset: 0x0000000000656a0c
Faulting process ID: 0x24a4
Faulting application start time: 0x01d21ebb74b91b8c
Faulting application path: F:\PostgreSQL\9.6\pgAdmin 4\bin\pgAdmin4.exe
Faulting module path: F:\PostgreSQL\9.6\pgAdmin 4\bin\Qt5WebKit.dll
Report ID: 5d8e33d7-643b-4605-b333-
e275fa34eb97 Faulting package full name:
Faulting package-relative application ID:
Fault bucket 120562057157, type 4
Event Name: APPCRASH
Response: Not available
Cab Id: 0
Problem signature:
P1: pgAdmin4.exe
P2: 0.0.0.0
P3: 57ea0209
P4: Qt5WebKit.dll
P5: 5.5.1.0
P6: 561c21e5
P7: c0000005
P8: 0000000000656a0c
P9:
P10:
Attached files:
\\?\C:\ProgramData\Microsoft\
Windows\WER\Temp\WER22FE.tmp. WERInternalMetadata.xml \\?\C:\Users\Plan-It Test\AppData\Local\Temp\
WER2EE6.tmp.appcompat.txt \\?\C:\ProgramData\Microsoft\
Windows\WER\Temp\WER2F54.tmp. mdmp \\?\C:\Users\Plan-It Test\AppData\Local\Temp\
WER3466.tmp. WERDataCollectionFailure.txt
These files may be available here:
C:\ProgramData\Microsoft\
Windows\WER\ReportArchive\ AppCrash_pgAdmin4.exe_ 56d2f47cc3652cd8762dd8b03fb84c 5b4a145b67_1456a217_31405410
Analysis symbol:
Rechecking for solution: 0
Report ID: 5d8e33d7-643b-4605-b333-
e275fa34eb97 Report Status: 4104
Hashed bucket: 6fc72a316d292b3487cc89f4b7f90a
8d
Cheers
Nigel
Dr Nigel Tucker
System Architect
Specialised Structures NZ
Telephone Direct (NZ) +64 (0) 3 482 2473
From: Dave Page [mailto:dpage@pgadmin.org]
Sent: Monday, 3 October 2016 10:18 PM
To: Nigel Tucker
Cc: pgAdmin Support
Subject: Re: [pgadmin-support] PgAdmin 4 not working in Windows 10
Hi
On Sat, Oct 1, 2016 at 6:13 PM, Nigel Tucker <nigel@specialisedstructures.
co.nz> wrote: Hi,
I have recently installed the new Postgres 9.6 RC1, having previously used 9.2, 9.4, and 9.5 extensively for all our business activities.
As a test, I performed a pg_upgrade to create a new copy of several databases on 9.6 RC1. All fine.
However PgAdmin 4 always crashed with the usual ‘PgAdmin stopped working’ message that it has always been prone to – but this time whenever I try to open ANY database.
I'm not aware that it's always been prone to that. I've seen one or two reports, but that was amongst over 500 issues during development..
I spent several hours installed Python in case it needed that to run correctly, and this seemed to improve things – it now crashes only every 10 minutes or so. But now it’s gone back to crashing whenever I open a database again.
Unless you've modified the config options, then installing Python won't make any difference. The runtime itself (which is the bit that would give the message above) is written in C++, and is linked with the Python interpreter at build time.
So Question 1: Where is the pg_admin log now being stored if anywhere – if not, where can I set its path so I can see what’s happening?
Under the %AppData% directory, e.g. C:\Users\dpage\AppData\
Roaming\pgAdmin\pgadmin.log. You can change that in config_local.py (see config.py for the default setting, which you can copy/paste into config_local.py to override).
Note that that is the log for the application server, i.e the Python code that is hosted in the runtime. The runtime doesn't have it's own log, besides what you might find in the event viewer.
Question 2 – why doesn’t pgAdmin 4 for windows 10 work?
It does for thousands of other people (at least we assume it does - they're keeping quiet if it doesn't). Of course there are always exceptions where some unexpected environmental issue causes problems.
Since we use the Express for Windows Desktop version of Visual Studio 2015, the path to the debugger seems unavailable – have you any suggestions how to find out what is going wrong?
It does sound like a runtime issue. You could install Qt, then try compiling/debugging your own build of the runtime. I'd hold on that option for the moment though, as it can take a little effort to setup a build environment.
Before you do anything else though, please make sure you upgrade to PostgreSQL 9.6.0 and pgAdmin 4 1.0 (i.e. the GA versions, not RC1).
I am happy to return to 9.5 for the moment, but I was really looking forward to using the new interface, and implementing it for all our users across the country.
Sadly,
Nigel
Dr Nigel Tucker
System Architect
Specialised Structures NZ
Telephone Direct (NZ) +64 (0) 3 482 2473
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company