Thanks, Jeff. I’ll be sending out 1 v17.1 build next month and hope to see the
same thing. I still have the issue several times a week in v16r6.
Thanks.
--
Cannon.Smith
Synergy Farm Solutions Inc.
Aetna, AB Canada
> On Mar 11, 2019, at 5:19 PM, Jeffrey Kain wrote:
>
> No, not at all since
No, not at all since v17.0 initial release.
> On Mar 11, 2019, at 7:07 PM, Cannon Smith
> wrote:
>
> Thanks. Good to know it has been solid otherwise.
>
> P.S. Have you seen the delayed process not waking up issue since moving to
> v17.1?
Thanks. Good to know it has been solid otherwise.
P.S. Have you seen the delayed process not waking up issue since moving to
v17.1?
--
Cannon.Smith
Synergy Farm Solutions Inc.
Aetna, AB Canada
> On Mar 11, 2019, at 4:47 PM, Jeffrey Kain wrote:
>
> Nobody else has responded... so I guess
Nobody else has responded... so I guess it was just us. Or maybe not that many
are running client/server in v17.1 yet. Aside from this weird glitch v17.1 has
been very solid.
--
Jeffrey Kain
jeffrey.k...@gmail.com
> On Mar 11, 2019, at 3:57 PM, Cannon Smith via 4D_Tech
This will not be fixed until Daylight Savings, or Standard Time is done
away with, and there is no more +/- 1 hour at random places around the
world :)
and just BECAUSE. (they can i guess???)
https://www.timeanddate.com/time/time-zones-interesting.html
there are 30 minute, and 45 minute
Hi Jeff,
We had to relaunch all our servers for them to get the time update, but they
are still on v16r6. I thought the daylight saving bug had been fixed in v17.1
so I’m curious to know what you find if you get more information.
Good luck.
--
Cannon.Smith
Synergy Farm Solutions Inc.
Aetna,
Did anyone else have any weirdness with their 4D Server v17.1 and the change to
Daylight Savings Time this morning?
Most, but not all, of our users got disconnected around the time of the change,
the SQL server and the 4D Server UDP port that broadcasts the server name
stopped responding (we
7 matches
Mail list logo
