No announcement yet.

Corrupt Office Docs as Attachments to Shared Review

  • Filter
  • Time
  • Show
Clear All
new posts

  • Corrupt Office Docs as Attachments to Shared Review

    It seems that a Microsoft Office document can become corrupt when added as an attachment to a FoxitPhantom shared review.

    By "corrupt" I mean this. We start with a Visio file.The Visio file is fine. People can open it and send it as an email attachment with no issues. The Visio file is attached and published to a shared review.

    A reviewer, either using Foxit Reader or Foxit Phantom, double-clicks the attachment icon to download the file. The "Open File Attachment" dialog box appears. The reviewer selects "Open this file attachment," and then clicks OK. The Office application starts (Visio in this case). The error message appears: "An error (275) occurred during the action Open File. Visio cannot open the file or a component in the file because it is corrupt." The Visio file is not opened.

    A similar issue occurs with PowerPoint. Given the same scenario as above, only with a PowerPoint file, PowerPoint responds with the following message: "PowerPoint found a problem with the content in C:\Users\{path}{filename}.pptx. PowerPoint can attempt to repair the presentation. If you trust the source of this presentation, click Repair." The reviewer clicks Repair. The next message is: "PowerPoint couldn't read some content in {filename}.pptx [Repaired] and removed it. Please check your presentation to see if the rest of it looks okay." The PowerPoint file is opened and seems fine. But the reviewer had to deal with those sketchy error messages first.

    Some details:
    Office Professional Plus 2013.
    The shared review file was posted to an internal SharePoint library, and then sent as a link to reviewers. My test version is saved locally, and I open my local file to conduct these tests.
    The shared review file extension is .ppdf (protected PDF).
    Comments are collected on an internal server. This is NOT a Foxit ConnectedPDF review.
    Files used to test this included a simple Visio drawing and a simple PowerPoint presentation, each with one empty page based on the default Blank Drawing/Blank Presentation template. Alternatively, a simple text file (.txt) and a simple PDF file (.pdf) did not suffer corruption.

    As a workaround, we will ask reviewers to .zip Office documents before attaching them to a shared review (right-click the file in Windows Explorer > Send To > Compressed (zipped) folder). Zipping the attachment first seems to protect the file from corruption.

    Could this be due to an encoding issue between Foxit Phantom and Office documents?


    Last edited by JasonLS1015; 06-26-2019, 10:30 PM.

  • #2

    Could you please help provide following info so we could test the problem and further look into it accordingly on our side?
    1) Version number of your Foxit PhantomPDF; (You may check it by going to "Help"->"About Foxit PhantomPDF') If not the most current version 9.5.0, may I encourage you to give it a try?
    2) Did you attach the Office document to the .ppdf document as attachment then go to "Share"->'Send for Shared Review'->"Collect comments on an internal server"?
    3) If possible, could you please use the LiceCap tool to generate an animated gif that shows how to reproduce the problem for our referencing?
    Here's the download link:
    (Unzip it, then double-click on licecap file, you can then specify the recording area then hit "Record", it requires naming the file first then start recording.)
    4) Your OS info. (You may right-click on "This PC/Computer" then open Properties to check the detailed OS version number.)

    Thank you.


    • #3

      1. Phantom version
      2. First, sent as shared review (Share > Send for Shared Review > Collect comments on an internal server). Then attached document to the shared review (Comment > Attach File) and published comments.
      3. See attached GIF.

      4. Windows 10 Enterprise 10.0.16299 (Build 16299)
      Last edited by JasonLS1015; 08-15-2019, 07:49 PM.


      • #4
        See attached .zip, which contains an MP4 file showing how to reproduce the problem.
        Attached Files


        • #5

          I've forwarded your comments as suggestion to Foxit internal bug tracking system for taking a closer look at. The report ID#: QCPHANTOM-20211. Any further update, we'll post here. Or you may email us to [email protected] with this ID# to track the processing status. Thank you.


          • #6
            While using Phantom PDF, I am not able to create filliable for. It comes with an error message whenever I try to do it. What can I do now?


            • #7
              monicachortle13 ,I apologize for any difficulty using Foxit Software.Do you mean that you failed to create filliable form? If so,please let us know which tool under the "Form"tab in Foxit PhantomPDF did you use and what was the error message you received? Please take a screenshot of the error message you referred. To make a screenshot, please press 'PrScrn SysrRq' on the keyboard, then go to 'Start'->'All Programs'->'Accessories'->'Paint'->press Ctrl V to paste and save.
              And please go to "Help"tab in Foxit PhantomPDF,click on "About Foxit PhantomPDF" to check its version information.