Hi there,
Not sure in your scenario whether you are also appending the files, but we were having a similar issue where 'save and append as pdf' to a network location was returning the same error. If one user had the error come up, another user could perform the same action and it work just fine - so the path was correct. I just found a possible answer on this forum from a member named VickyNesbit from Aug 2012, which reads:
"We all use networked accounts here - save and append PDFs to the network account and this error will pop up intermittently - I'm guessing because the server is busy backing up the newly created PDF at the same time that FileMaker is trying to append to it.... Or something like that anyway...
Amended script to save everything to the temporary folder (which is local) using Get ( TemporaryPath ) - it works sweet as a nut every time!"
I have very high hopes that this will resolve the issue in our environment, I hope it helps you too
