Hi Cannon,
> If we encounter a server with a process that has “hung”, can we install
> ProcDump at that moment and get a capture?
> Or does ProcDump need to be installed and running before the server is
> launched?
ProcDump does not need to be running before 4D Server is launched.
ProcDump cou
Hi Tim,
[Not sure if you missed this last week so I thought I’d ask again.]
If we encounter a server with a process that has “hung”, can we install
ProcDump at that moment and get a capture? Or does ProcDump need to be
installed and running before the server is launched?
--
Cannon.Smith
Synerg
You might but be aware if you use cross table reports in quick reports, they
are not as yet available in 64 bit client. If you compile 64 bit server and 32
bit client on macs you use the new network layer
Regards
Chuck
> On Sep 22, 2017, at 5:49 PM, 4d_tech-requ...@lists.4d.com wrote:
>
> I ask because we have been upgrading our customers to V15 R5 and are seeing
> the opposite, especially on all our VM systems.
I can confirm speed issues with v15 and VM machines — verified on multiple
servers, with differe
Hi Tim,
If we encounter a server with a process that has “hung”, can we install
ProcDump at that moment and get a capture? Or does ProcDump need to be
installed and running before the server is launched?
--
Cannon.Smith
Synergy Farm Solutions Inc.
Hill Spring, AB Canada
403-626-3236
> On Se
Tim -
> And since you are using the legacy network that means you are still running
> 32bit 4D Client. If you want to run 64bit client — macOS or Windows — you are
> required to use the new network layer. Is that your understand too?
Correct. I’m thinking 2Q of 2018 that we will start looking
> What is “procdump”? I’ve not heard of this before.
ProcDump is a command-line utility by Microsoft to create DMP files:
https://docs.microsoft.com/en-us/sysinternals/downloads/procdump
4D Support has a small interface to help configure ProcDump, referred to as
ProcDump_interface:
https://taow.
On Sep 22, 2017, at 4:49 PM, Jeff Kain wrote:
> 15.4, which seemed to be about the same as v13.
>
> At first I just discounted the early reports, but more and more came in that
> things were a lot snappier in v16.
And since you are using the legacy network that means you are still running
32bi
On Sep 22, 2017, at 4:49 PM, Jeffrey Kain wrote:
> We reported the stored procedure frozen issue... it's only happened once so
> far. We're going to get a procdump from the server the next time it happens.
What is “procdump”? I’ve not heard of this before.
Tim
*
-Original Message-
From: 4D_Tech [mailto:4d_tech-boun...@lists.4d.com] On Behalf Of Tony
Ringsmuth via 4D_Tech
Sent: Friday, September 22, 2017 3:19 PM
To: 4D Nug <4d_tech@lists.4d.com>
Cc: Tony Ringsmuth
Subject: Re: 4D v16 issues
Drew,
I’m h
> On Sep 22, 2017, at 3:19 PM, Tony Ringsmuth via 4D_Tech
> <4d_tech@lists.4d.com> wrote:
>
> Only thing I would shy-away from is the new network layer: I’m dealing with
> a case right now where if you have larger numbers of users (20+): things get
> slow.
Mac, Windows or mixed? Is the serve
, 2017 3:40 PM
To: 4d_tech@lists.4d.com
Cc: Jeffrey Kain
Subject: Re: 4D v16 issues
15.4, which seemed to be about the same as v13.
At first I just discounted the early reports, but more and more came in that
things were a lot snappier in v16.
> On Sep 22, 2017, at 4:17 PM, Stephen J. O
-boun...@lists.4d.com] On Behalf Of Tony Ringsmuth
via 4D_Tech
Sent: Friday, September 22, 2017 3:19 PM
To: 4D Nug <4d_tech@lists.4d.com>
Cc: Tony Ringsmuth
Subject: Re: 4D v16 issues
Drew,
I’m happy to report that my users are on 16.2, and things are going quite well.
I have users to the t
15.4, which seemed to be about the same as v13.
At first I just discounted the early reports, but more and more came in that
things were a lot snappier in v16.
> On Sep 22, 2017, at 4:17 PM, Stephen J. Orth
> wrote:
>
> Jeff,
>
> When you say V16 is noticeably faster, compared to what versio
Drew,
I’m happy to report that my users are on 16.2, and things are going quite well.
I have users to the tune of about 500,000 man-hour/month using instances of the
database that I work-on.
Only thing I would shy-away from is the new network layer: I’m dealing with a
case right now where if y
Technical <4d_tech@lists.4d.com>
Cc: Jeffrey Kain
Subject: Re: 4D v16 issues
Hey Drew -
We reported the stored procedure frozen issue... it's only happened once so
far. We're going to get a procdump from the server the next time it happens.
The record lock issue has only happ
I would only use legacy network for now... when users crash with the new
network, they never get logged out of the system and leave all of their records
locked. I haven't taken time to reproduce this in a small database and report
the issue to 4D.
Neil
--
Privacy Disclaimer: This mes
Hey Drew -
We reported the stored procedure frozen issue... it's only happened once so
far. We're going to get a procdump from the server the next time it happens.
The record lock issue has only happened twice. From what others have written
here, it sounds like it's been an issue for others fo
18 matches
Mail list logo