I have run into this too, although in my experience there was always some error during my scripting process.
Try saving the file with a different name (if you haven't already), otherwise try the Print command from the file menu and select a PDF printer and see if you can produce a PDF.
The scripting use to work the way it was. I have tried using File-Save/Send Record As - PDF, saving it to my desktop with a unique name, I receive the same error.
These databases are hosted on a server, I just opened up a backup directly in the client and than it will save correctly. I need these to work off the server.
Sounds like there may be some plugin issue, where the plugin you are using to produce PDFs is correctly installed in the server but not in the computer that is displaying this error.
Do you know if there are plugins involved in the script? Otherwise, it seems strange that the "Save records as PDF..." from the Menu does not work either.
No I do not use any plug in at all
Create a brand new layout using FMP16 in a new file and see if you can save it as a PDF.
If that works, try changing the layout theme In your original file.
I have seen this same error message from time to time. The problem was NEVER that the disk was full or that the disk was locked. It was (if memory serves) always due to a faulty path. The smallest things can invalidate the path: failure to append ".pdf" to the filename might do it; a misplaced "/" in the path; and of course, a path to a folder that doesn't exist.
I'd suggest adjusting your script as follows:
Set Variable [ $outputpath ; Get ( DesktopPath ) & "myreport.pdf" ]
Go to Layout [ ReportLayout ]
Save Records as PDF [ With dialog:on ; $outputpath ; Records being browsed ]
This should allow you to confirm that a pdf can be created on the user's desktop. Once you have confirmed that, you can modify as necessary.
With more testing it seems limited to just two machines that can not write the pdfs. They are set-up as workstations using the same generic logons. It must be the way the machines are set up somehow. I check all the folders I am trying to save into and they have read/write privileges to everyone. I will have to look more into the two machines setup that is blocking things
Thanks for all the ideas
Is it possible that the file is open in some app? That is one way to create that error message.
They are set-up as workstations using the same generic logons.
Is that a generic log on that controls access to your solution? If so, you might review the privilege set to be sure that it allows printing and exporting.