From: | "Duffey, Blake" <Blake(dot)Duffey(at)noblis(dot)org> |
---|---|
To: | Khushboo Vashi <khushboo(dot)vashi(at)enterprisedb(dot)com> |
Cc: | Dave Page <dpage(at)pgadmin(dot)org>, "Pgadmin-Support(at)Postgresql(dot) Org" <pgadmin-support(at)postgresql(dot)org> |
Subject: | RE: Query Tool Initialize Error |
Date: | 2018-07-13 15:35:39 |
Message-ID: | DM5PR10MB1786D2C54CB1999855592EC4F9580@DM5PR10MB1786.namprd10.prod.outlook.com |
Views: | Raw Message | Whole Thread | Download mbox | Resend email |
Thread: | |
Lists: | pgadmin-support |
If I try to open http://127.0.0.1:61142/browser/ in an incognito window, I get Unauthorized
Please note the behavior isn’t consistent – it sometimes works and not others
From: Khushboo Vashi <khushboo(dot)vashi(at)enterprisedb(dot)com>
Sent: Friday, July 13, 2018 11:29 AM
To: Duffey, Blake <Blake(dot)Duffey(at)noblis(dot)org>
Cc: Dave Page <dpage(at)pgadmin(dot)org>; Pgadmin-Support(at)Postgresql(dot) Org <pgadmin-support(at)postgresql(dot)org>
Subject: Re: Query Tool Initialize Error
On Fri, Jul 13, 2018 at 8:30 PM, Khushboo Vashi <khushboo(dot)vashi(at)enterprisedb(dot)com<mailto:khushboo(dot)vashi(at)enterprisedb(dot)com>> wrote:
Hi,
Thanks for the logs.
It shows the upgrade check fails, which is not causing the Query tool failure.
So, after enabling the logs, please try to open query tool 2 to 3 times and then send the logs.
Also, see the browser's developer console and if any error, please send the screen-shot for the same.
One more thing:
Try to open the application in the browser's incognito mode or clear the cache/cookies and and then run the application. This may fix your problem.
Have you tried this?
Thanks,
Khushboo
On Fri, Jul 13, 2018 at 8:10 PM, Duffey, Blake <Blake(dot)Duffey(at)noblis(dot)org<mailto:Blake(dot)Duffey(at)noblis(dot)org>> wrote:
From: Duffey, Blake <Blake(dot)Duffey(at)noblis(dot)org<mailto:Blake(dot)Duffey(at)noblis(dot)org>>
Sent: Friday, July 13, 2018 7:26 AM
To: Dave Page <dpage(at)pgadmin(dot)org<mailto:dpage(at)pgadmin(dot)org>>; Khushboo Vashi <khushboo(dot)vashi(at)enterprisedb(dot)com<mailto:khushboo(dot)vashi(at)enterprisedb(dot)com>>
Cc: Pgadmin-Support(at)Postgresql(dot) Org <pgadmin-support(at)postgresql(dot)org<mailto:pgadmin-support(at)postgresql(dot)org>>
Subject: RE: Query Tool Initialize Error
This is on Windows 2012 Server (via Citrix)
I’ll work on getting logs
From: Dave Page <dpage(at)pgadmin(dot)org<mailto:dpage(at)pgadmin(dot)org>>
Sent: Friday, July 13, 2018 4:10 AM
To: Khushboo Vashi <khushboo(dot)vashi(at)enterprisedb(dot)com<mailto:khushboo(dot)vashi(at)enterprisedb(dot)com>>
Cc: Duffey, Blake <Blake(dot)Duffey(at)noblis(dot)org<mailto:Blake(dot)Duffey(at)noblis(dot)org>>; Pgadmin-Support(at)Postgresql(dot) Org <pgadmin-support(at)postgresql(dot)org<mailto:pgadmin-support(at)postgresql(dot)org>>
Subject: Re: Query Tool Initialize Error
In addition to Khushboo's suggestions, can you try a hard-reload and running in an incognito session in your browser please Blake? I want to be sure it's not a caching issue.
On Fri, Jul 13, 2018 at 5:40 AM, Khushboo Vashi <khushboo(dot)vashi(at)enterprisedb(dot)com<mailto:khushboo(dot)vashi(at)enterprisedb(dot)com>> wrote:
This issue is already reported on Windows. Ref: https://redmine.postgresql.org/issues/3433
Are you on Windows? If yes then which version?
Please enable logging and provide the logs. To enable logging ref: https://www.pgadmin.org/faq/#8
On Fri, Jul 13, 2018 at 1:20 AM, Duffey, Blake <Blake(dot)Duffey(at)noblis(dot)org<mailto:Blake(dot)Duffey(at)noblis(dot)org>> wrote:
Launching pgAdmin 4 ver 3.1 against PG 9.5
User selects servers, database, schema
Clicks Tools | Query Tools
Is immediately hit with ‘Query Tool Initialize Error’
Thanks
--
Dave Page
Blog: http://pgsnake.blogspot.com
Twitter: @pgsnake
EnterpriseDB UK: http://www.enterprisedb.com
The Enterprise PostgreSQL Company
From | Date | Subject | |
---|---|---|---|
Next Message | Khushboo Vashi | 2018-07-13 15:38:15 | Re: Query Tool Initialize Error |
Previous Message | Khushboo Vashi | 2018-07-13 15:29:14 | Re: Query Tool Initialize Error |