Updated: Sept 6/23

Summary:
1. Installing the latest build of PFW on server resolved problem with deleting
LCK files when exiting Paradox

2. Performance reading/writing files across the network was never resolved
so we did the following:
   - deleted old network drive P: mapping via Group Policy 
   - created new local drive on Remote Desktop server
   - shared new drive with read/write access to relevant user
  group
   - copied all data & network control files from old network drive to new
local drive
   - re-lettered new local drive to the same letter used previously for the
network drive (i.e. changed D: to P:)
   - ensured that network backup is configured to include new local drive
   - tested data read/writes and all works as before.  Actually, it's about
25% faster.

If anyone out there every finds out why performance would take such a hit
after upgrading to Server 2019 I'd certainly appreciate any information as
I expect to run into this again with other legacy Paradox applications.

Bradley Wood

"Bradley Wood" <inukshukat@hotmail.com> wrote:
>
>Liz,
>
>I tried running it as an Administrator without any luck.
>
>I've requested that the hosted services provider disable security scanning
>on the executable and the directories where the database files live but
they
>have to pass it by their SysOps team for approval.  I'll post a response
>if/when they make that change.
>
>Thanks for your suggestions!
>
>BW
>
>Liz McGuire <liz@paradoxcommunity.com> wrote:
>>What happens if you run as administrator?  Just for testing purposes. 
That
>would help
>>determine if it's a rights issue.  (Just because the users can do it does
>not mean
>>that an app, even if run as that user, has the rights.)  Also, have you
>tried running
>>Paradox in some compatibility mode - working backward - to see if that
works?
>>
>>Oh, finally, make sure all antivirus software is set to ignore the Paradox
>executable
>>and all directories where it and the database files live.
>>
>>Liz
>>
>>
>>On 25 Aug 2023 09:10, Bradley Wood wrote:
>>> Steve,
>>> 
>>> Thanks for your responses!
>>> 
>>> 1. Local Share in the BDE was set to true.
>>> 
>>> 2. I was able to configure the startup and associated cleanup into a
bat
>>> file as a temporary work around but I was hoping to identify some setting
>>> (likely related to network security) that would prevent the AppCrash
event
>>> on exit when it attempts to delete the .lck files.  It's interesting
that
>>> it does cleanup all the temporary files in the :PRIV: dir that start
with
>>> the "__.." prefix but stumbles over the .lck files.
>>> 
>>> Again, thanks for your help.
>>> 
>>> Bradley Wood
>>> 
>>> Steve Green <steve@oasistradingpost.com> wrote:
>>>>> As a final configuration point, SMB2/3 has been disabled on the RD
&
>>>>> App servers, SMB1 has been enabled, and OpLocks has been disabled.
>>>>
>>>> and Local Share in the BDE must be TRUE.. could be the solution needed,
>>> too
>>>>
>>>>
>>>>> Since the Remote Desktop server from which the application is run was
>>> upgraded > from
>>>> Server 2012 to 2019 the .LCK files in the user's private
>>>> directory are> no longer being deleted when exiting PFW.
>>>> you should be able to easily wrap the startup in a bat file and kill
>the
>>> 
>>>> lock files first, if necessary
>>>>
>>>>
>>>> -- 
>>>> Steven Green
>>>> Myrtle Beach, South Carolina USA
>>>>
>>>> http://www.OasisTradingPost.com
>>>>
>>>> Collectibles and Memorabilia
>>>> Vintage Lego Sets and Parts
>>>> - and Paradox support, too
>>>>
>>> 
>