AnsweredAssumed Answered

Corrupted container issue

Question asked by darrenburgess on Feb 11, 2013
Latest reply on Feb 15, 2013 by ArchitectureConceptsLighting

I am working with a solution that using secure external storage.

 

It appears that some of the container data has been corrupted. I am observing the following:

  1. Attempting to export the field contents give an 824 error. (File is damaged or not a FileMaker file)
  2. The file can be viewed using the interactive container field display for PDF files
  3. Just an JPG icon is displayed if container interaction is set to JPG
  4. Files that are not corrupt will display the JPG preview.
  5. I can use the Save to Disk icon in the PDF interaction controls to save the corrupted file, even if the JPG preview is not viewable.
  6. Saving the file using PDF interaction controls saves the file, but with the encrypted filename (as in: FM-18F28C01-9F12-C04C-B469-83472F03120E.pdf)
  7. There are 72 document files in this solution. Corrupt files were not added on any particular day or by any particular user.

 

I would suspect that the issue is corrupt or missing JPG previews for the PDF files.

 

Questions:

  1. Do you believe that issue is corrupt JPG previews?
  2. What could cause this issue?
  3. Is there a way to fix the corrupted container data? (I could use PDF interaction to save each file individually and then import it back in.)

 

Thanks for your help!

 

Darren Burgess

http://www.mightydata.com

Outcomes