This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(204.8, 98%, 29%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EC%3C/text%3E%3C/svg%3E)
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
Let me ping some people and see if I can get an answer.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(0, 97%, 10%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EEB%3C/text%3E%3C/svg%3E)
I have the same problem here.
4- Exchange Servers 2016 CU18;
2- Exchange Servers 2019 CU7;
In my case the problem is in full access to downloading the attachment of other mailbox by owa.
https://owa.hosterdomain.com/owa/login@customer.com/#path=/attachmentlightbox
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(268.8, 84%, 36%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ESU%3C/text%3E%3C/svg%3E)
I also discovered a problem when a user who is in a mailing group is sent letters with attached photos.
the preview does not work and open (download) - throws it to "https://outlook.office365.com/owa/t ...... Works only if you click" Download all "which is not convenient.
Has anyone found a solution? Or maybe Microsoft has released a separate patch?
CU wait a month, long time.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(112.00000000000001, 38%, 20%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EMM%3C/text%3E%3C/svg%3E)
CU19 is out. I've tested it and it solves this problem. However, I can no longer view PDFs in path=/attachmentlightbox. I have to open them in a new tab/window.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(307.2, 31%, 39%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3ED%3C/text%3E%3C/svg%3E)
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.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(233.6, 90%, 32%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EKH%3C/text%3E%3C/svg%3E)
This is an incredibly valuable workaround, and works for our affected environment. Thank you so much for sharing this.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(28.799999999999997, 82%, 12%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EEY%3C/text%3E%3C/svg%3E)
Hi everyone,
The engineering team is working on the issue and fix would be release in the coming updates.
Please wait for the next CU released then test if the issue persists.
If an Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.
btw, I got a nearly final anwser from the MS support that the real bugfix will be only available in the next CU.
Thank you for the update, even if it's not such good news.
Hi @Christoph ,
Microsoft support is aware of a similar issue and asks that you open a support ticket with them so they can track it down. So please do that to get some resolution. It's not something that can be solved here.
Thanks!
Hi,
thank you for your response. We opened already a ticket with Microsoft yesterday, but we have not received any feedback yet
kind regards
Christoph
If you can provide the Case Number, I can pass that on.
sure it's: 22106041
maybe it wasn't the best idea to open the ticket in german language ;-)
:) Well, at least they can check it out and maybe get some eyes on it quicker.
sounds promising :-)
It seems a bug with Exchange 2016 CU18, not heard such issues before and it's working well in my Lab(2013&2016).
Let's see how Microsoft would explain about this.
If an Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.