squimby
asked on
OWA 2016 Public Folder Shared Contacts - Error: The message can't be sent right now. Please try again later.
Outlook Web Access 2016 will not email to valid public folder shared contacts for one specific contact list. If you are in the full Outlook 2016 client, there are no issues emailing to anyone in this same shared contact list. All other shared contact lists work fine in both OWA 2016 and Outlook 2016. The Exchange 2016 server is fully patched.
I can see the shared contact in the shared contact list. I can select the shared contacts in the public folder shared contact list.
When I go to send to anyone in this shared contact list from OWA 2016, I get "Error: The message can't be sent right now. Please try again later". All other emails, addressed to anyone, are sent absolutely fine.
Repeating this with the same public folder shared contact list in real Outlook 2016 works fine.
Repeating this with any other public folder shared contact list in OWA 2016 works fine.
Patching the Exchange server to current patch levels including the most recent CU had absolutely no effect.
The users are highly transient and must use OWA 2016 vs. the full Outlook client.
See the attached screen shot.
VFES-Shared-Contact-Error.PNG
I can see the shared contact in the shared contact list. I can select the shared contacts in the public folder shared contact list.
When I go to send to anyone in this shared contact list from OWA 2016, I get "Error: The message can't be sent right now. Please try again later". All other emails, addressed to anyone, are sent absolutely fine.
Repeating this with the same public folder shared contact list in real Outlook 2016 works fine.
Repeating this with any other public folder shared contact list in OWA 2016 works fine.
Patching the Exchange server to current patch levels including the most recent CU had absolutely no effect.
The users are highly transient and must use OWA 2016 vs. the full Outlook client.
See the attached screen shot.
VFES-Shared-Contact-Error.PNG
ASKER
The hosts file entries made absolutely no difference.
I can OWA to addresses not in this public shared contacts directly. Creating a new shared contact has the same issues.
Adding me to as a second recipient to a shared contact fails the same way until I remove the shared contact.
It happens with OWA inside and out.
OWA virtual directory rights: Authenticated Users - Write, System Full (inherited), my ID inherited full (Exchange admin and domain admin), Administrators inherited full.
Looking at a random sampling of users I appear to have three Exchange Legacy DN variations. One is not set. one is First Administrative Group and one is First Administrative Group with a number. The three screenshots are attached showinng the variation.
This Exchange server was originally Exchange 2000 migrated to 2003 migrated to 2010 and recently migrated to 2016 over the years The server is working fine. All users are working fine. OWA is working fine outside of this specific shared contact issue. Other pre-existing shared contacts work fine in OWA. Other aspects of public folders are working fine (i.e. calendars). The full Outlook 2016 client works fine - even with these shared contact lists.
Thanks for your assistance!
Exchange-Legacy-DN3.PNG
Exchange-Legacy-DN1.PNG
Exchange-Legacy-DN2.PNG
I can OWA to addresses not in this public shared contacts directly. Creating a new shared contact has the same issues.
Adding me to as a second recipient to a shared contact fails the same way until I remove the shared contact.
It happens with OWA inside and out.
OWA virtual directory rights: Authenticated Users - Write, System Full (inherited), my ID inherited full (Exchange admin and domain admin), Administrators inherited full.
Looking at a random sampling of users I appear to have three Exchange Legacy DN variations. One is not set. one is First Administrative Group and one is First Administrative Group with a number. The three screenshots are attached showinng the variation.
This Exchange server was originally Exchange 2000 migrated to 2003 migrated to 2010 and recently migrated to 2016 over the years The server is working fine. All users are working fine. OWA is working fine outside of this specific shared contact issue. Other pre-existing shared contacts work fine in OWA. Other aspects of public folders are working fine (i.e. calendars). The full Outlook 2016 client works fine - even with these shared contact lists.
Thanks for your assistance!
Exchange-Legacy-DN3.PNG
Exchange-Legacy-DN1.PNG
Exchange-Legacy-DN2.PNG
This question needs an answer!
Become an EE member today
7 DAY FREE TRIALMembers can start a 7-Day Free trial then enjoy unlimited access to the platform.
View membership options
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
what is the permission set on the OWA virtual directory ?
Shared address automatically resolving to the right recipient address in OWA and still an issue ?
what if.. if you add your address on the to field in addition to that email?
Issue when access OWA internally or externally ?
when accessing internally.. can u put a host entry for each exchange server and check if you can send the emails ?
any chance a duplicate legacy exchange DN value available in your environment ?