Forum Discussion

AlexanderH90's avatar
AlexanderH90
Copper Contributor
Sep 18, 2024

Unable to open PDF attachments from shared mailbox with OWA

Hi, we are using Exchange 2019 (Build 15.02.1544.011) and are experiencing an issue with Outlook Web Access (OWA) where PDF files cannot be previewed or downloaded. This problem only occurs when opening a shared mailbox in OWA and trying to open a PDF file from an attachment. In the personal mailbox, the files can be previewed and downloaded without any issues. When opening the PDF in a shared mailbox, the following error message appears:

 

{"Body":{"ErrorCode":500,"ExceptionName":"ThreadAbortException","FaultMessage":"Thread was being aborted.","IsTransient":false,"ResponseCode":"ErrorInternalServerError"}}

 

This error occurs in Edge as well as in other browsers. Is this problem already known?

 

Thanks,

Alex

Exchange Server
  • iwalsh's avatar
    iwalsh
    Copper Contributor
    Feb 27, 2025

    Workaround: For anyone with access to the Outlook desktop app, the classic version is working fine.

  • AdamWillett1's avatar
    AdamWillett1
    Copper Contributor
    Feb 25, 2025

    I'm experiencing this issue as well (unable to open/review PDF files in a shared inbox) but it opens if you move the email into the user inbox. Is there a fix for this?

  • Ilya's avatar
    Ilya
    Copper Contributor
    Feb 24, 2025

    We are encountering the same issue. The exact same email was sent to both a regular mailbox and a shared mailbox. The attached PDF can be opened and previewed from the regular mailbox without any issues, but it appears blank when previewed from the shared mailbox. This behaviour is consistent in both OWA and the Desktop Outlook App. It affects any PDF files that are being sent both within the organization and from external sources.

     

    • bnostrand's avatar
      bnostrand
      Copper Contributor
      Feb 25, 2025

      It looks like there’s an ongoing issue with opening attachments in OWA Shared Mailboxes. Microsoft is aware of the problem and is working on a code fix. They expect to start deploying the fix by the end of Wednesday, February 26, 2025, and hope to resolve the issue by the end of Thursday, February 27, 2025

Resources