Exchange 2016: after installation of CU 18 attachments from shared mailbox can't be opened in OWA

Christoph 46 Reputation points
2020-09-30T10:31:23.44+00:00

Hi,

we installed last Thursday CU 18 on a single Exchange 2016. After that we recognized that attachment from shared mailboxes can't be opened anymore. This affects all attachments, download and preview. The problem seems to be that the URL for the attachment ist wrong. When we try to download an attchment a new windows is opened and we're redircted to a url in this format (original domain name is replaced):

"https://outlook.office365.com/owa/temp-test@domain-name.de/service.svc/s/GetAttachmentDownloadToken?redirect=%2fowa%2ftemp-test%40domain-name.de%2fservice.svc%2fs%2fGetFileAttachment%3fid%3dAAMkADVjYTJlNmVhLWU5YWUtNDExNC04YmI5LTNkNDI1NzU0YTRhZQBGAAAAAACFeKz%252b7LiwTJTGaiFKmoEUBwDgWBbEnQXzT5ipyGwAVbfZAAAAAAEMAADgWBbEnQXzT5ipyGwAVbfZAAAAAAk3AAABEgAQAHTIfMMNYkBEk%252bb%252f1UJcNZo%253d%26X-OWA-CANARY%3dji4zp9VACUGzxzvHkAjNH0AOjQZUZNgIt7lknLLRBv1JieCvW96de5oLgPWmV6rJSNOZafAG8fU.%26isDocumentPreview%3dFalse

I do not understand why this request is getting redirected to office365.com. We do not have an hybrid enviroment or anything like that. "Normal" user accounts does not have any problems. if we forward the affected e-mail from the shared mailbox to a real person, attachment can be opened. Event logs or similar do not show any related anomalies. Any ideas whats going on or how to fix this?

btw, problem exists only in OWA, the same attachment can be opened in Outlook without any problems. The problem also exists with a new shared mailbox.

kind regards Christoph

Exchange Server Management
Exchange Server Management
Exchange Server: A family of Microsoft client/server messaging and collaboration software.Management: The act or process of organizing, handling, directing or controlling something.
7,411 questions
{count} votes

Accepted answer
  1. David 91 Reputation points
    2020-10-14T09:57:17.057+00:00

    Hi everyone,

    Guess no one found a solution so far and we need a fix from MS?
    We have update to CU 18, same problem. But we do not have the recent updates installed from yesterday patch day.

    One workaround we discovered so far.
    Instead of "Open another mailbox..." you can access the shared mailbox with "Add shared folder..." instead.
    We run a DAG Exchange 2016 cluster on windows server 2012 R2 server.

    3 people found this answer helpful.

19 additional answers

Sort by: Most helpful
  1. Christoph 46 Reputation points
    2020-10-06T20:02:21.707+00:00

    Hi,

    possible workaround could be the move of the shared mailboxes to a new database.

    • affected mailbox1 moved from active DB1 to newDB1 - error was fixed
    • same mailbox1 moved back to DB1 - fix persistent

    • affected mailbox2 from existing DB1 to existing DB2 (no DAG) - error ???

    we're waiting for a reply from tech support regarding this


  2. Christoph 46 Reputation points
    2020-10-08T08:17:00.25+00:00

    ok guys,

    my colleague who performed the test unfortunately made a mistake. The described workaround does not work! Please excuse the circumstances. We are updating our case at Microsoft

    0 comments No comments

  3. Matthew Koeman 1 Reputation point
    2020-10-08T12:25:38.81+00:00

    we have the same issue after upgrading exchange 2016 cu16 > cu18

    0 comments No comments

  4. Stefan Schipper 1 Reputation point
    2020-10-09T06:46:46.947+00:00

    Same issue here on Exchange 2016. No hybrid.
    Did anyone receive any feedback/workaround from Microsoft already?

    0 comments No comments