Re: Drop User NOT working (after client disconnected using Force Quit)

2020-04-15 Thread John J Foster via 4D_Tech
Hey Tim, Thanks for the very detailed response. I will cull through them and see what I can send to the client. Their IT is very sophisticated. At one time, I was told, they were Microsoft’s 10th largest client? Suffice to to say they are well equipped - a blessing and a curse since they know

Re: Drop User NOT working (after client disconnected using Force Quit)

2020-04-15 Thread Tim Nevels via 4D_Tech
On Apr 15, 2020, at 11:05 AM, Spencer Hinsdale wrote: > Dude, 17.4 is the bomb. The ultimate fix for our times is Sleep on SSL > (ACI0096906). This means you can run remote, encrypted, and shut your laptop > for lunch and when you open again 4D client is Instant ON! > > New Networking

Re: Drop User NOT working (after client disconnected using Force Quit)

2020-04-15 Thread John J Foster via 4D_Tech
Hey Randy, Yea that makes sense IU guess if 4D thinks the processes are still active. Spencer suggested that it might have been fixed in 17.4. Fingers crossed, John… > In some situations where the 'drop user’ was failing, I have been able to > switch over to the list of processes and abort

Re: Drop User NOT working (after client disconnected using Force Quit)

2020-04-15 Thread John J Foster via 4D_Tech
Hey Randy, Spencer has indicated that there was a bug fix which handled this. So fingers crossed… Thanks for sharing, John… > We have seen this numerous times on a client running a Mac server with people > logging in from a Windows terminal server. > > My understanding was that clients

Re: Drop User NOT working (after client disconnected using Force Quit)

2020-04-15 Thread John J Foster via 4D_Tech
Hey Spencer, I was hoping to hear something like that. The client site has about 40-50 clients plus a few remote and they don't like changing! So this might be the push needed. I’ll find and review the bug fixes. Appreciate, John… > Dude, 17.4 is the bomb. The ultimate fix for our times

Re: Drop User NOT working (after client disconnected using Force Quit)

2020-04-15 Thread Jeffrey Kain via 4D_Tech
This is what I do as well. Drop User doesn't work at all in v17R5, but killing off the processes does. The issue of ghost users sounds like our experience when we tried the not-so-new network layer. We don't see it very often at all with the legacy network. > On Apr 15, 2020, at 12:04 PM,

Re: Drop User NOT working (after client disconnected using Force Quit)

2020-04-15 Thread Spencer Hinsdale via 4D_Tech
Dude, 17.4 is the bomb. The ultimate fix for our times is Sleep on SSL (ACI0096906). This means you can run remote, encrypted, and shut your laptop for lunch and when you open again 4D client is Instant ON! New Networking (ServerNet) works awesome. 64-bit Remote, Encrypted is FAST. 32-bit

Re: Drop User NOT working (after client disconnected using Force Quit)

2020-04-15 Thread Randy Jaynes via 4D_Tech
In some situations where the 'drop user’ was failing, I have been able to switch over to the list of processes and abort each of the user’s processes. The user was dropped when the last process successfully aborted. I can say that this hasn’t succeeded every time, but it has worked for me.

Re: Drop User NOT working (after client disconnected using Force Quit)

2020-04-15 Thread Randy Kaempen via 4D_Tech
John, > On Apr 15, 2020, at 10:28 AM, John J Foster via 4D_Tech > <4d_tech@lists.4d.com> wrote: > > 4D v17.2 64bit Windows > Windows 10 Pro > > Another issue (last month actually) that I’m not sure if there is a fix. > Although client believes there is one! Here’s what happened: > > A User

Drop User NOT working (after client disconnected using Force Quit)

2020-04-15 Thread John J Foster via 4D_Tech
Hey All, 4D v17.2 64bit Windows Windows 10 Pro Another issue (last month actually) that I’m not sure if there is a fix. Although client believes there is one! Here’s what happened: A User (client) froze up in the application and so they excited improperly by quitting the 4D through the Task