sss.pgh.pa.us
> [postgresql.org]
> <https://urldefense.com/v3/__https:/www.postgresql.org/message-id/5665.1202148155*40sss.pgh.pa.us__;JQ!!CKZwjTOV!ynTEucv4RZeRFy0jb8ofk_Qs3LMS2aWNT8QSkc5n7RFIeJfgBOaUp0uAxwuQRhP0xWo5Yj51N2IcQ8R3mUaXZA$>
> ).
>
> At this time IT says it is not a fire wall issue as there are no rules
> setup for dropping connections. We
On 6/26/24 12:56, Tarras, Tim wrote:
Windows Defender is turned off and a 3rd party AV is being used. We did ask
about that and were told that would not be the issue. I would also think that
I would be dropping the connection when I am on the Server itself which is not
the case.
I have atta
; pgsql-general@lists.postgresql.org
Subject: Re: [External] Dropping connections
On 6/26/24 10:44 AM, Tarras, Tim wrote:
> Hello,
>
> Underlying DBMS error [no connection to the server::SQLSTATE=å]
> [xxx.xxx.GDB_Items][STATE_ID = 0]
>
> X's replace actual names.
&
On 6/26/24 10:44 AM, Tarras, Tim wrote:
Hello,
Underlying DBMS error [no connection to the server::SQLSTATE=å]
[xxx.xxx.GDB_Items][STATE_ID = 0]
X's replace actual names.
Working with ESRI we found the following information in the logs :
"*An existing connection was forcibly closed
ire wall issue as there are no rules setup
for dropping connections. We are at a loss as to what the culprit is.
I will also be posting this in PostgreSQL community to get their input.
Thank you for your help with this.
This email and any files transmitted with it are confidential and are