Hi Aditya,
Yes, you were right. Quick heal was blocking the port. Now it is working
after some configurations in quick heals. Thanks for you support.
On Tue, Jan 7, 2020 at 1:12 PM Aditya Toshniwal <
aditya.toshni...@enterprisedb.com> wrote:
> Hi Vivek,
>
> That's strange. It should not take tha
On Tue, Jan 7, 2020 at 2:50 PM Vivek Parmar wrote:
> Hi Aditya,
>
> Yes, you were right. Quick heal was blocking the port. Now it is working
> after some configurations in quick heals. Thanks for you support.
>
Glad it worked !!
>
> On Tue, Jan 7, 2020 at 1:12 PM Aditya Toshniwal <
> aditya.tosh
Hi Aditya,
It is still not working. I tried with 3000 value too. Here are the logs:
07.01.2020 12:41:46 Checking for system tray...
> 07.01.2020 12:41:46 Starting pgAdmin4 server...
> 07.01.2020 12:41:46 Creating server object, port:53102,
> key:70fc2f32-3034-4b33-bf21-6c23cd3138b8,
> logfile:C:/
Hi Vivek,
That's strange. It should not take that amount of time.
Can you try disabling firewall once ? I suspect the port used by pgAdmin is
blocked by firewall.
On Tue, Jan 7, 2020 at 12:51 PM Vivek Parmar wrote:
> Hi Aditya,
>
> It is still not working. I tried with 3000 value too. Here are
[please do not remove pgadmin-hackers from cc]
Hi Vivek,
Seems like pgAdmin is timing out on your system. It is taking longer than
90 secs for server to start. It generally happens on windows systems where
sqlite3 (which is used by pgAdmin config) takes a lot of time to initialize.
Try the follow
Hi Vivek,
Kindly also share - C:/Users/vivek/.pgAdmin4.4018626542.log
On Mon, Jan 6, 2020 at 9:01 PM Vivek Parmar wrote:
> Hi Aditya,
>
> Here it is:
>
> 06.01.2020 16:47:22 Checking for system tray...
>> 06.01.2020 16:47:22 Starting pgAdmin4 server...
>> 06.01.2020 16:47:22 Creating server obj
