Monitoring the _error_log.txt found in the \BRO folder for any new happenings of this error may be useful in knowing whether your fixes are working or not..
Have all users exit Power Broker.
Check for orphaned sessions on the server.
Close open files from:
• Computer Management
• Shared Folders
• Open Files
Now track todays date and check the _error_log.txt for any new errors until they go away after trying these suggestions.
Antivirus Blocking DBF Operations
This has become more common recently.
Typical culprits:
• ESET
• SentinelOne
• CrowdStrike
• Sophos
• Defender Controlled Folder Access and more…
Disable Real Time Scanning on Network Drives
\BRO
\BUCKET
\BULK
\IMAGES (2,3,4,5) AND any other Power Broker related folders
Disconnect and reconnect mapped drive can be a fast way to see how long it takes before the error occurs again.
How to check to see if something in Windows is disconnecting your connection.
Google ‘turn off background refresh of group policy’
Google ‘Configure keep-alive connection intervall’
Check Utilities – ReSet User InUse Files.
<Reset All users> to clear any open files or users signed in more than once.
Orphaned FoxPro Lock Files
Look for lingering files:
*.TMP
FOXUSER.*
If these files are in the network ‘Share’ ,it’s safe to delete these as long as people are not in Power Broker or doing maintenance.
Insufficient Rights on Parent Folder
The data share directory containing the Power Broker software should have the setting ‘Full Control’
\BRO
\BUCKET
\BULK
\IMAGES (2,3,4,5) AND any other Power Broker related folders
Read-Only Attribute Still Present
Even after running this from the root of \BRO in a CMD prompt:
attrib -r *.* /s
the server may still have read-only permissions enforced through inheritance.
Check that:
• DBF
• CDX
• FPT
all show writable from Windows Explorer.
Offline Files Enabled
Has caused random 1705 errors.
Check:
Control Panel
Sync Center
Manage Offline Files
Disable Offline Files for VFP data shares.
User Doesn’t Have Rights to Create Temporary Files
VFP often creates temporary work files during REINDEX.
Test with everyone out of Power Broker and ensuring your have a recent backup just in case but only one a few users, not all:
The Idea: COPY Usercode.dbf test.dbf
If that fails, rights are likely the issue.
Example:
Q:\bro>copy kv.dbf Q:\bro\test.dbf
1 file(s) copied.