After further testing, I discovered the issue is actually just moving the file. NTFS permissions, by default, apply differently when copying a file over versus moving it.

Does the user who causes the problem maybe have a different mapping than other users, to get to the main folder? That could be the cause of the problem.

Then of course, you could try running this powershell script ("\\R9N2WRN\Share" is the main folder in this example). Personally I'm not a fan of that, since not everyone allows you to run powershell and it could be locked out on certain machines for certain users:

$Acl = Get-Acl "\\R9N2WRN\Share"

$Ar = New-Object System.Security.AccessControl.FileSystemAccessRule("user", "FullControl", "ContainerInherit,ObjectInherit", "None", "Allow")

$Acl.SetAccessRule($Ar)
Set-Acl "\\R9N2WRN\Share" $Acl

See https://stackoverflow.com/questions/25779423/powershell-to-set-folder-permissions

To execute powershell code from powerbuilder, see: https://stackoverflow.com/questions/54866589/run-powershell-commands-from-powerbuilder One user suggests using OLE instead of running a batch file with the Run() function (my preferred way too):

string ls_cmd
oleobject wsh
wsh=create oleobject

wsh.connecttonewobject("WScript.Shell")

ls_cmd='cmd /C powershell ......'

wsh.run(ls_cmd,0,false)
destroy wsh

There's also a link to one of Bruce Armstrong's posts. He also uses "Run(...)", but suggests you can avoid that by using "ShellExec", "ShellExecEx" and "CreateProcess". 

regards

MiguelL

Hi Matt;

  If all you do is just restart your PB App, do the PDF moves start working OK again?

Regards ... Chris

Hi Matt

Are you saying that it works some of the time but not always?