Hi Dave, I do have pgAdmin4 v.1.3 (not v1.5) installed with postgresql-9.6.2-3-windows-x64.exe - and it works well when started directly from its own folder.
I suspect, that those two environments may disturb each other, but cannot see see how. Also: 1) when v1.6 launched from the installer it works well. 2) when v1.6 launched from a shortcut it starts v1.5. 3) When I check from program manager, both 1) and 2) run the same "pgAdmin 4\v1\runtime\pgAdmin4.exe" executable from v1.6 installation path. I will do some checks on another PC today. Thank you and kind regards Pawel On 21 July 2017 at 00:28, Dave Page <dp...@pgadmin.org> wrote: > You don't have the PostgreSQL installer from EDB or BigSQL on that machine > do you? They have their own separate copies of pgAdmin. > > Sent from my iPad > > On 20 Jul 2017, at 23:53, Pawel Hadam <had...@gmail.com> wrote: > > Thank you Dave, > > Full clean-up (all folders and registry) and fresh installation helps > once. On the last screen I select to Launch pgAdmin4 and v1.6 starts > correctly and I can use it. I need to say it is very nice. > > 2017-07-20 23:42:17,891: INFO pgadmin: Starting pgAdmin 4 v1.6... > > > However, when I exit and launch it again, it starts again.... v1.5 in the > server mode and the log files say the same and it still cannot connect to > the server: > > 2017-07-20 23:43:56,013: INFO pgadmin: Starting pgAdmin 4 v1.5... > > > Please see attached config files from C:\Program Files (x86)\pgAdmin > 4\v1\web\ > and log files from C:\Users\pawelhadam\AppData\Roaming\pgAdmin\ > > > I have no idea where v1.5 is still sitting on my PC :( I must be doing > something stupid, I am afraid. > > > Thanks in advance for any more help and kind regards > Pawel > > > On 19 July 2017 at 09:12, Dave Page <dp...@pgadmin.org> wrote: > >> [Narrowing the addressee list] >> >> Hi >> >> On Tue, Jul 18, 2017 at 11:14 PM, Pawel Hadam <had...@gmail.com> wrote: >> >>> Hi Dave, >>> >>> Thank you for this advise. >>> >>> Please find attached my files: >>> >>> 1) C:\Users\pawelhadam\AppData\Roaming\pgAdmin\pgadmin4.log >>> >>> I cannot understand why this log file says "Starting pgAdmin 4 v1.5..." >>> as I have installed v1.6 from pgadmin4-1.6-x86.exe >>> >> >> That certainly screams of 'messed up installation'. It gets that number >> from config.py. >> >> >>> >>> 2) C:\Program Files (x86)\pgAdmin 4\v1\web\config_local.py >>> >> >> I'm surprised it even works with that - it looks like a direct copy of >> config.py, and if you look at the end is basically importing itself. >> >> Please uninstall pgAdmin, and ensure C:\Program Files (x86)\pgAdmin 4 is >> completely removed. I would also suggest removing %APPDATA%\pgAdmin as well >> (note that will delete your config database so you'll have to re-add any >> registered servers). >> >> Then, using regedit.exe, remove the registry key: >> HKEY_CURRENT_USER\Software\pgadmin\pgadmin4 >> >> Once the system is completely cleaned, try a fresh installation. >> >> Regards, Dave. >> >> >>> >>> Thank you and kind regards >>> Pawel >>> >>> >>> On 17 July 2017 at 09:36, Dave Page <dp...@pgadmin.org> wrote: >>> >>>> >>>> >>>> On Fri, Jul 14, 2017 at 1:58 PM, Pawel Hadam <had...@gmail.com> wrote: >>>> >>>>> Thank you Dave and Khushboo for advises. >>>>> >>>>> 1) (re)moving 'pgadmin4.db' - did not help. >>>>> >>>>> 2) I have disabled teredo - did not help. >>>>> >>>>> 3) localhost is resolved to IPv6 address: >>>>> >>>>> $ ping localhost >>>>> >>>>> Pinging ogrodowa [::1] with 32 bytes of data: >>>>> Reply from ::1: time<1ms >>>>> Reply from ::1: time<1ms >>>>> Reply from ::1: time<1ms >>>>> Reply from ::1: time<1ms >>>>> >>>>> 4) I DO use IPv4 as well. >>>>> >>>>> 5) No entries for localhost in hosts file. >>>>> >>>>> 6) On which address/port the server should be listening? >>>>> >>>>> $ netstat -a | grep LISTEN | grep "127.0.0.1" >>>>> TCP 127.0.0.1:3212 ogrodowa:0 LISTENING >>>>> TCP 127.0.0.1:3213 ogrodowa:0 LISTENING >>>>> TCP 127.0.0.1:4370 ogrodowa:0 LISTENING >>>>> TCP 127.0.0.1:4371 ogrodowa:0 LISTENING >>>>> TCP 127.0.0.1:4380 ogrodowa:0 LISTENING >>>>> TCP 127.0.0.1:4381 ogrodowa:0 LISTENING >>>>> TCP 127.0.0.1:5037 ogrodowa:0 LISTENING >>>>> TCP 127.0.0.1:9990 ogrodowa:0 LISTENING >>>>> TCP 127.0.0.1:30000 ogrodowa:0 LISTENING >>>>> TCP 127.0.0.1:49674 ogrodowa:0 LISTENING >>>>> >>>>> 7) ping to 127.0.0.1 works well: >>>>> >>>>> $ ping 127.0.0.1 >>>>> >>>>> Pinging 127.0.0.1 with 32 bytes of data: >>>>> Reply from 127.0.0.1: bytes=32 time<1ms TTL=128 >>>>> Reply from 127.0.0.1: bytes=32 time<1ms TTL=128 >>>>> Reply from 127.0.0.1: bytes=32 time<1ms TTL=128 >>>>> Reply from 127.0.0.1: bytes=32 time<1ms TTL=128 >>>>> >>>>> >>>>> Not sure what else I need to check... >>>>> >>>> >>>> In the web/ subdirectory of the installation, you should find a file >>>> called config.py. Please create a file called config_local.py in the same >>>> directory, containing the following lines (excluding the ==== lines) : >>>> >>>> ==== >>>> from config import * >>>> >>>> # Debug mode >>>> DEBUG = True >>>> >>>> # Log >>>> CONSOLE_LOG_LEVEL = DEBUG >>>> FILE_LOG_LEVEL = DEBUG >>>> ==== >>>> >>>> Then, try to start pgAdmin. That should create a more useful logfile in >>>> %APPDATA%\pgAdmin to share with us. >>>> >>>> Thanks. >>>> >>>> -- >>>> 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 >> > > <config.py> > > <pgadmin4.log> > > <config_distro.py> > > <config_local.py> > >
