Hi Rikard,
Did you ever find a resolution for this? We started to get the exakt same issue
you describe a couple of month ago on a customer when upgrading from v13 to
v17.0 HF2. 4D then told us to update 17.3 HF2, still same problem.
While we no longer have the issue, I'm afraid wecan't actually pin-point
the exact solution for you. We had a number of different problems at
essentially the same time (for months and months) and we had to try a
number of different things before the issues seemed to stop.
The system is currently running using 4D v17R6, on a machine running
Windows Server 2012, with the majority of the clients being Windows 10.
All in 64-bit (obviously as we're running R6), and currently using the
legacy network layer.
We 'think' that the problem went away after a version update, so I'm
wondering if there was something that changed in one of the later R
releases (R4) that hasn't been rolled into the Dot releases....?
Sorry I can't be any more help at the moment. We'll have a chat about it
at this end and if we think of anything else that might help, we'll let
you know.
Cheers
Allan
ustomer is running Windows 10 clients and Windows Server 2012. We use 32 bit
client and 64bit server. The environment was the same when running v13 where
did not have this issue.
Server can be running from 1-2 days until almost 2 weeks before it happens.
We are currently using the legacy network layer and we are now about to change to the
"new network layer" (again recommendation from 4D).
We are quite desperate to find a solution for this.
On 13 Feb 2019, at 23:12, Allan Udy via 4D_Tech <[email protected]> wrote:
Hi all,
I asked in November, and Tim Nevels confirmed he''d seen the issue once, but I
need to ask again:
Has anyone else seen an instance of the 'Reject New Connections' button on the
Application Server page of the 4D Server Admin window, spontaneously changing
to 'Accept New Connections' WITHOUT anyone manually pressing/clicking the
button?
4D Server 17R3 -- also happened with earlier versions of v17. May have happened
with v16 but can't confirm
Windows Server 2012
Has happened on the current server hardware, and also on a different hardware
box.
Clients network, cabling and switches have been seriously over-hauled and
upgraded over the past six months.
We got a call from a client to say that their 15 in-house users had been
disconnected from the (4D) server (again).
When I remotely connected to the live server I could see:
a) there were zero (0) users connected,
b) the HTTP Server page of the Admin window indicated that the server was still
accepting incoming web connections (the counter was ticking over)
c) We logged into the online system, updated some data and submitted the update.
d) We received the emailed update notification from the system, indicating that
the internal web server was still working happily, and that the server code was
still capable of sending email out.
e) the UI of the server Admin window was responsive -- there was no interface
lagging as there often is if the system is experiencing any sort of memory
issue.
f) the New Connection button on the Application Server page of the Admin window
read 'Accept New Connections'. In other words, as far as the Server UI was
concerned, someone had previously gone into the Application Server page and
manually clicked on the 'Reject New Connections' button. !!!!!! I believe no
one actually did that.
g) As soon as I pressed the 'Accept New Connections' the server froze up and I
had to End Task and restart.
Has anyone else seen this behaviour?
We've recently added some internal logging into the On Server Close Connections
database method, and can see in our Logs, that at exactly the same time (to the
second)there were 57 *On Server Close Connections (i.e. DIS*connection*)*logs
recorded as ALL of the logged in Clients disconnected. I wouldn't expect this
to happen if there were some form of network issue....?
This suggests that from 4D Servers**perspective all the clients were
disconnected in an orderly fashion at the same time, almost as though the
Server admin had issued a Shutdown/Quit command and the clients were being
forced to disconnect from the server.
It's almost like the internal 4D Engine is periodically checking some network
(?) or internal condition, and if it fiond it to be true, then the New
Connections button interface text is changed to 'Accept New Connections'....
If anyone has any suggestions as to how this could happen, we'd be interested
to know.
Golden Micro Solutions Ltd, Blenheim, New Zealand
http://www.golden.co.nz<http://www.golden.co.nz>
**********************************************************************
4D Internet Users Group (4D iNUG)
Archive: http://lists.4d.com/archives.html
Options: https://lists.4d.com/mailman/options/4d_tech
Unsub: mailto:[email protected]
**********************************************************************
