Nothing to do with Active Directory. The path you specified is probably incorrect or you do not have enough privileges to create file in that location.
Try to save pdf to your desktop first.
Sometimes Windows Network Administrators lock local Temp folders, somewhere where FileMaker developers often export PDFs, e.g. prior to emailing.
It could also be something so simple as another user (or indeed you yourself) already have the file that FileMaker is trying to create open.
Several solutions we have built creates a pdf on a shared network drive prior to attaching to an email (although with Windows 10 and Outlook the 32bit/64bit issues have arisen but that is a different story). If one person runs the script and then leaves the pdf open on the pc, another user will get the error message you experienced when they try to run the script.
I get this all the time.
Just set the path using the "Add Files" button initially so you see what path makes FM happy.
I also just save to the desktop as a test, first.
ditto the previous replies. Can you post your PATH to the file?
I've seen this, as well. The majority of the time this message comes up for me, it's because there's already a file with that name at that path, and the file is open so it can't be replaced. I sure wish we could get a more specific error (i.e. "c:\filename.pdf is open, and cannot be replaced") or at least a different error code. It'd save me a lot of confused support calls.
Thanks everybody. The initial problem was the file pathname. I spoke with our systems administrator and we needed to add in the server name to the path filename in order for it to work.
"filewin://Server Name/.../Invoice Notice/testing.pdf"
However, now I can't add in the field name. I understand that I should be able to replace testing.pdf with & "table:fieldA" and "table:fieldB" & ".pdf" however, I am receiving the same error message again. I'll double check the syntax, but I think it is correct.
P.S. The file name doesn't already exist.
Check your calculation (with the file name replacement) in Data Viewer. There might be some characters in filename that break your path or missing/extra "/".
When I getting those errorsI
I make a temporary dialogue and show my path variable and last error. Then I can see what really is written in the path and file name.
I finally worked it out. It didn't like me putting quotes around the field names. It works fine now.
Thanks for all your suggestions. I am continually learning new things.