1 Reply Latest reply on Mar 7, 2014 2:08 PM by TSGal

    View PDF stored inside container not opening Filemaker GO

    JordanWilliams

      Summary

      View PDF stored inside container not opening Filemaker GO

      Product

      FileMaker Server

      Version

      13 Advanced

      Operating system version

      Windows Server 2008 R2

      Description of the issue

      After upgrading from Filemaker server 12 Advanced to 13 Advanced the container holding a PDF will not open on Filemaker GO 12 or 13. The same container functions fine on Filemaker Pro and Pro Advanced as well as on Web Direct. After clicking the "view" option from the export menu FMGO will attempt to open the PDF in a viewer but will fail with the error message "Failed to open .pdf". Also the container will not show a preview of the PDF file but will show an icon with the name.pdf.
      Again this is only happening with Filemaker GO 12 and 13 in conjunction with Filemaker server advanced 13. All functions work properly with Filemaker server advanced 12.

      Clearing all of the cache folders in the server directory tree seems to allow the PDF to be opened one time and then once the cache is filled again it will fail.

      Steps to reproduce the problem

      1) Create container on layout with Filemaker Pro 13 Advanced. Set the container to PDF content type.
      2) Upload the database to Filemaker Server Advanced and access it from Filemaker Go 13.
      3) Tap on the container field and select the "view" option
      4) The PDF will open the first time.
      5) Close out the app and try the same step again. This time the PDF will not open.
      6) Log on to the server and delete the contents in RC_cache and RC_stramingcache and it will open one more time.  The next time it will fail again.

      Expected result

      The PDF should open in the webviewer.

      Actual result

      Failed to open .pdf

      Nothing opens and error is thrown after the second attempt to open the PDF

      Exact text of any error message(s) that appear

      Failed to open .pdf

      Workaround

      Log on to the server and delete the contents in RC_cache and RC_stramingcache and it will open one more time.  The next time it will fail again.

        • 1. Re: View PDF stored inside container not opening Filemaker GO
          TSGal

               Jordan Williams:

               Thank you for your post, and I apologize for the late reply.

               I am unable to replicate the issue.  Here are the steps I took:

               1. Using FileMaker Pro 12 under Windows 7, I created a database file with two Container fields named "Container File" and "Container Interactive".

               2. In Layout Mode, I set the formatting for "Container Interactive" for Interactive content.

               3. In Browse Mode, I added one record.  With "Container File" active, I pulled down the Insert menu and selected "File...".   I inserted one of the FileMaker PDF files (Acknolwedgements).  It appears as a PDF icon.

               4. With "Container Interactive" active, I pulled down the Insert menu and selected "PDF...".  I inserted another FileMaker PDF files (Read Me).

               5. I turned on Network Sharing for All users.

               6. I closed the file and quit FileMaker Pro 12.

               7. I manually moved the FileMaker Pro 12 file to Windows Server 2008 R2 machine running FileMaker Server 13, and placed it in the Databases folder.  I launched Admin Console and opened the database file.

               8. On an iPhone, I launched FileMaker Go 13, accessed the server and opened the database file.

               9. I tapped first in the "Container File", tapped View, and the PDF file is displayed.

               10. I tapped the "Container Interactive" field, tapped View, and the PDF file is displayed.

               11. I closed the file, and exited the application.

               12. I launched FileMaker Go again, accessed the file, and I can tap and view both Container fields.

               Let me know what I'm doing differently than you so I can replicate the issue.

               TSGal
               FileMaker, Inc.