O365 client stopped opening shared mailboxes

Hello all,
I had users that have been accessing shared mailboxes from their outlook clients for weeks with no issues. All of a sudden, whenever they try to access the shared mailboxes, the cursor spinds until it times out and then brings up a dialog box saying:
The set of folders cannot be opened. Microsoft Exchange is not available. Either there are network problems or the Exchange server is down for maintenance.
Our Exchange server is E365, so it is definately up. The permissions on the shared mailbox are correct, because you can open the shared mailbox using OWA.
Any ideas why the long term function of "open these additional mailboxes" under the main account would no longer function?
Thank you!
-Karl

Hi Karl,
As you mentioned, you can open the shared mailbox using OWA. Thus, the permissin on the shared mailbox should be correct. The issue may be related to Outlook client.
Please remove the shared mailbox from "Open these additional mailboxes", apply it. Then re-add it back to check if the shared mailbox can be opened now. If the issue persists, please uncheck User Exchange Cached mode in Account Settings and
verify whether the shared mailbox can be opened in Outlook Online mode.
If the issue doesn't continues in Online mode, it may be caused by corrupted profile. We can
create a new Outlook profile to have a try.
Regards,
Winnie Liang
TechNet Community Support

Similar Messages

"Set of folders can not be opened. you must connect to microsoft exchange with current profile" geeting error while opening shared mailbox in outlook 2007

Hello Folks,
I am having exchange sever 2007 SP3. currently facing issue with one shared mailbox. One of the user is not able to open that mailbox from outlook 2010.
I can able to add that mailbox in the outlook but while opening the outlook it is asking for password. Outlook is not accepting user password for that mailbox. I have removed that user from full access and added that user again.
Other shared mailbox is working fine with same outlook profile and other user can also able to access that problematic shared mailbox.
Can anyone tell how to troubleshoot..?
Thanks, Chinmay.

Hi,
How do you open the shared mailbox in Outlook?
Please remove the shared mailbox from your Outlook totally and follow the following steps to open it:
1. Open Outlook, click File > Account Settings
> Account Settings.
2. Click Change and make sure Use Cached Exchange Mode is checked.
3. Click More Settings > Advanced tab.
4. Click Add next to Open these additional mailboxes and type the shared mailbox.
5. Click Ok > OK. Then the shared mailbox would be listed under the Navigation Pane.
Alternatively, we can create a new Outlook profile in Outlook and setup the shared mailbox. If it is asking for credentials, we can use the user account who have full access permission to the shared mailbox for authentication.
Regards,
Winnie Liang
TechNet Community Support

Outlook 2010 Problem opening shared mailbox "the set of folders cannot be opened. Microsoft Exchange is not available"

Hi, I have a number of mailboxes configured for sharing.
For those users who have full access rights (given via EMC) the mailboxes automatically appear in Outlook 2010.
However for one of those mailboxes the users recieve the following error when they try to access it:
"The Set of Folders cannot be opened. Microsoft Exchange is not available. Either there are network problems or the Exchange server is down for maintenance."
Meanwhile the users' primary mailboxes continue to work as normal, as do the other mailboxes that have been shared with them.
The output of get-mailboxpermissions for the problematic mailbox is the same as the output for a full working one.
If I add the mailbox to my account (as though I was using Outlook 2003) it allows me access, however I then have the situation of having the mailbox listed twice, one working the other not.
How do I get this mailbox to behave as expected?
Many thanks
Nick

So the problem returns. I'm not sure what we did to work around it, the users who were having the problem have left and the new batch are now encountering it.
I have issued the following command on the Exchange Server (one site, one server, all roles, only a default throttling policy exists):
$a = Get-ThrottlingPolicy | where-object {$_.IsDefault -eq $true}
$a | Set-ThrottlingPolicy -RCAMaxConcurrency 40
The result of Get-ThrottleingPolicy is:
RunspaceId                                : 8bc47cdf-a695-47f0-b31e-e6ffba6aed66
IsDefault                                 : True
AnonymousMaxConcurrency                   : 1
AnonymousPercentTimeInAD                  :
AnonymousPercentTimeInCAS                 :
AnonymousPercentTimeInMailboxRPC          :
EASMaxConcurrency                         : 10
EASPercentTimeInAD                        :
EASPercentTimeInCAS                       :
EASPercentTimeInMailboxRPC                :
EASMaxDevices                             : 10
EASMaxDeviceDeletesPerMonth               :
EWSMaxConcurrency                         : 10
EWSPercentTimeInAD                        : 50
EWSPercentTimeInCAS                       : 90
EWSPercentTimeInMailboxRPC                : 60
EWSMaxSubscriptions                       : 5000
EWSFastSearchTimeoutInSeconds             : 60
EWSFindCountLimit                         : 1000
IMAPMaxConcurrency                        :
IMAPPercentTimeInAD                       :
IMAPPercentTimeInCAS                      :
IMAPPercentTimeInMailboxRPC               :
OWAMaxConcurrency                         : 5
OWAPercentTimeInAD                        : 30
OWAPercentTimeInCAS                       : 150
OWAPercentTimeInMailboxRPC                : 150
POPMaxConcurrency                         : 20
POPPercentTimeInAD                        :
POPPercentTimeInCAS                       :
POPPercentTimeInMailboxRPC                :
PowerShellMaxConcurrency                  : 18
PowerShellMaxTenantConcurrency            :
PowerShellMaxCmdlets                      :
PowerShellMaxCmdletsTimePeriod            :
ExchangeMaxCmdlets                        :
PowerShellMaxCmdletQueueDepth             :
PowerShellMaxDestructiveCmdlets           :
PowerShellMaxDestructiveCmdletsTimePeriod :
RCAMaxConcurrency                         : 40
RCAPercentTimeInAD                        : 5
RCAPercentTimeInCAS                       : 205
RCAPercentTimeInMailboxRPC                : 200
CPAMaxConcurrency                         : 20
CPAPercentTimeInCAS                       : 205
CPAPercentTimeInMailboxRPC                : 200
MessageRateLimit                          :
RecipientRateLimit                        :
ForwardeeLimit                            :
CPUStartPercent                           : 75
AdminDisplayName                          :
ExchangeVersion                           : 0.10 (14.0.100.0)
Name                                      : DefaultThrottlingPolicy_eccf5379-4fb6-4e97-8b47-37b1dc58a9
DistinguishedName                         : CN=DefaultThrottlingPolicy_eccf5379-4fb6-4e97-8b47-37b1dc5
ettings,CN=Our Org Name,CN=Microsoft Exchange
onfiguration,DC=domain,DC=internal
Identity                                  : DefaultThrottlingPolicy_eccf5379-4fb6-4e97-8b47-37b1dc58a9
Guid                                      : a274d3ec-f2f8-43c3-ad26-6b960924ef0e
ObjectCategory                            : domain.internal/Configuration/Schema/ms-Exch-Throttling-Polic
ObjectClass                               : {top, msExchGenericPolicy, msExchThrottlingPolicy}
WhenChanged                               : 07/06/2011 10:24:47
WhenCreated                               : 07/06/2011 10:24:41
WhenChangedUTC                            : 07/06/2011 09:24:47
WhenCreatedUTC                            : 07/06/2011 09:24:41
OrganizationId                            :
OriginatingServer                         : OneOfTheDCs.domain.internal
IsValid                                   : True
But the problem remains. Do I need to adjust anything else for this value (40) to become active? The documentation implies that the above is required on a CAS, however there is mention of registry settings but no guidance on whether these are required if
the above is used.
When I create a second profile via Mail (in control panel) for the shared mailbox and then start outlook using this profile I am able to access the mailbox as expected. This is running in the context of the user who cannot access it from her
default Outlook profile.
Many thanks

Exchange 2010 users cannot open Exchange 2013 shared mailbox

Title says it all.
We're in the process of migrating 1000+ mailboxes to Exchange 2013. A number of shared mailboxes have been migrated, but those users still on 2010 cannot open them.
Is this just how it is, or is there a way around it?

Hi,
I tested in my lab, if the shared mailbox is on Exchange 2010, I could open this shared mailbox successfully. Then I moved this shared mailbox to Exchange 2013, after that, I couldn’t open it anymore, I got the following error:
Besides, I tried to open a shared mailbox on Exchange 2013 which was not moved from Exchange 2010, it is the same error message.
Based on the test, it seems that Exchange 2010 users can’t open shared mailbox on Exchange 2013. So I recommend you move those users to Exchange 2013.
Best regards,
Belinda Ma
TechNet Community Support

Outlook 2013 (Only) - Shared Mailbox - Not Syncing

Hi
After searching this forum and many other forums online, I have decided to ask my question here as I cannot find a solution.
We are migrating from Exchange 2003 to Exchange 2010 at the moment. All of a sudden our Outlook 2013 users (All of them) cannot update Shared Mailboxes. When you select that folder it says "Updating this Folder" but nothing is happening. Only happens
with their open Shared Mailbox not with their own Mailbox. I have done the following tests:
Users can open the Shared Mailbox and sync properly using OWA.
Users can open the Shared Mailbox but cannot sync via Outlook 2013.
Users can open and sync the Shared Mailbox via Outlook 2010.
Ran OST repair tool, no luck.
Completely deleted the profile and wiped all the files in the outlook folder and recreated the profile, no luck. (Not syncing straight away.)
Users can sync the Shared Mailbox when they are running outlook in Online mode. (I dont wanna do this coz they want to save their sent emails from a Shared Mailbox into the respective "Sent Item" folder which only works in Cached Mode.
Everything used to work fine and suddenly stopped for everyone. Can you please guide me on how to fix this?
Thanks in advance.
With regards
M
PS
I just realized that my Build Version is "Version 14.1 (Build 218.15)"
I am downloading the Service Pack 3, and it might help?

Hi,
It seems that the issue only happens in Outlook 2013 Cached mode. If you add secondary mailboxes to your profile through the Advanced
tab in the Microsoft Exchange dialog box, please check whether the “Download Shared Folders” is enabled in the Advanced tab.
If it is, the Sync issue occurs may because Outlook 2013 locally caches (in your Outlook data file [.ost]) all folders to which you have access in the secondary mailbox. To resolve it, we can refer to the detailed solution in the following KB:
http://support.microsoft.com/kb/2297543/en-us
Thanks,
Winnie Liang
TechNet Community Support
Hi,
I found this little tick yesterday and did clear it. So now people can still have their own mailbox cached and the rest online. But thank you for the link coz I couldnt find it before and it is good to know that it is a known issue rather than being a misconfiguration
at server level :) I have marked your post as the answer. Thanks again.

User mailboxes have more server-side rule options then shared mailboxes?

I was hoping to set up some server-side rules to keep a shared mailbox clean. The goal was to have some rules to move incoming messages to specific folders based off words in the subject. I opened the shared mailbox in OWA and found the action
of moving the message to a folder was not available. At first I figured that's an action that's only available in a client-side rule. However, I then found that in my user mailbox that action is available server-side. It would appear there
are a number of other action that are available server side to user but not shared mailboxes.
Anybody else notice this? Is this a bug?
Single Exchange 2013 SP1 server - nothing fancy.

Hi,
I have a test in my environment using Exchange 2013. We can use two methods to create rules in OWA. When I open shared mailbox via OWA to create rules, only one way is possible. I recommend you use this way to create rules in OWA and check the result. Here
is the detailed steps for your reference.
Click Setting icon (on the right corner) -> Options -> organize email -> New
Hope it helps.
Best regards,
Amy Wang
TechNet Community Support

Shared Mailbox migrating from Lotus Notes to Exchange

We currently have Lotus Notes and in the process of migrating to Exchange Server 2010. We are using the Quest Notes Migrator for Exchange and the Quest Coexistence Manager for Notes tools.
One of the issues we’re coming across is Shared Mailboxes..
Currently in Notes we have:
Signatures as part of the NSF file so they are included with every email – how will Outlook clients behave for Shared Mailboxes? Because we want the same Signature to be part of every email sent from a shared mailbox regardless of which user sent the email.
We are aware that if we use OWA we won’t have this problem, but how do we configure Signatures for Shared Mailboxes using Outlook clients?
Stationary: We have Stationery linked to our Shared Mailbox accounts, so for example, in our helpdesk mailbox, we have stationary documents/templates we send to end users who email our helpdesk asking a FAQ. Opposed to pointing users to SharePoint, how
do we tackle this in Outlook? Is there options?
Thanks
Ray

Hi,
1. you can use transport rule to have same signature when from field contains shared mailbox email address.
2. Sorry, I don't understand your second question.
Kottees : My Blog : Please mark it as an answer if it really helps you.

Shared mailbox not working on 2007

Hello,
i'm having a problem generating a shared mailbox and making it work, here's the BG info:
Created a universal security group called "info access" with two users which need MB access
we have domain.local internal and domain.com external
i created the mailbox with the cmdlets:
New-Mailbox -Name:'Info customer' -OrganizationalUnit:'domain.local/main' -Database:'Mailbox Database' -UserPrincipalName:'[email protected]' -Shared
Add-MailboxPermission info -User:'info access' -AccessRights:FullAccess
Add-ADPermission info -User:'info access' -ExtendedRights:Send-As -AccessRights:ReadProperty, WriteProperty -Properties:'Personal Information'
Set-Mailbox -Identity info -GrantSendOnBehalfTo:'info access'
Everything completed ok, i see the hsared mailbox in the EMC, i see it can receive mails, but when i go to add the mailbox to one of those users outlook it gives error "outlook cannot open mailbox, the user cannot access the location", OWa also
fails but with a hard crash message with mapiexceptionlogonfailed
what is going on?, i double checked on the EMC and i see the permissions granted to the group, do i need to apply permissions to each user?

Hi Eliminateur,
Thank you for your question.
The name of shared mailbox is “info customer”, so we could run the following command to grant full access to “info customer” :
Add-MailboxPermission –Identity 'Info customer' -User:'info access' -AccessRights:FullAccess
Add-ADPermission –Identity 'Info customer' -User:'info access' -ExtendedRights:Send-As -AccessRights:ReadProperty, WriteProperty -Properties:'Personal Information'
Set-Mailbox –Identity 'Info customer' -GrantSendOnBehalfTo:'info access'
Then we could check if we could open shared mailbox which name is “Info customer”.
If there are any questions regarding this issue, please be free to let me know.
Best Regard,
Jim
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Jim Xu
TechNet Community Support

Exchange 2010 Mailbox Users Cannot Access 2013 Shared Mailboxes

Hi Guys & Girls,
I've a painful issue with my environment which is made up of 1 x 2010 CAS server with 1x 2010 Mailbox server and 1x 2013 CAS server with 1 x 2013 mailbox server.
The users who've yet to be migrated to 2013 and are still on the 2010 server are unable to open shared mailboxes which have already been migrated to 2013.
When trying to access shared mailboxes on the 2013 servers they received the following error:
The configuration of OutlookAnywhere on my two CAS servers is as follows:
RunspaceId : aed28f13-cdd2-4dcf-a0a8-96b8e2518171
ServerName : THCAS1
SSLOffloading : True
ExternalHostname : mail.resourcegroup.co.uk
InternalHostname : mail.resourcegroup.co.uk
ExternalClientAuthenticationMethod : Ntlm
InternalClientAuthenticationMethod : Ntlm
IISAuthenticationMethods : {Ntlm}
XropUrl :
ExternalClientsRequireSsl : True
InternalClientsRequireSsl : False
MetabasePath : IIS://THCAS1.ResourceGroup.co.uk/W3SVC/1/ROOT/Rpc
Path : C:\Windows\System32\RpcProxy
ExtendedProtectionTokenChecking : None
ExtendedProtectionFlags : {}
ExtendedProtectionSPNList : {}
AdminDisplayVersion : Version 14.3 (Build 123.4)
Server : THCAS1
AdminDisplayName :
ExchangeVersion : 0.10 (14.0.100.0)
Name : Rpc (Default Web Site)
DistinguishedName : CN=Rpc (Default Web Site),CN=HTTP,CN=Protocols,CN=THCAS1,CN=Servers,CN=Exchange
Administrative Group (FYDIBOHF23SPDLT),CN=Administrative
Groups,CN=ResourceGroup,CN=Microsoft
Exchange,CN=Services,CN=Configuration,DC=ResourceGroup,DC=co,DC=uk
Identity : THCAS1\Rpc (Default Web Site)
Guid : 71f76f2a-4ee1-4a9a-b2da-06d79e975403
ObjectCategory : ResourceGroup.co.uk/Configuration/Schema/ms-Exch-Rpc-Http-Virtual-Directory
ObjectClass : {top, msExchVirtualDirectory, msExchRpcHttpVirtualDirectory}
WhenChanged : 26/11/2013 16:23:13
WhenCreated : 25/11/2013 16:33:45
WhenChangedUTC : 26/11/2013 16:23:13
WhenCreatedUTC : 25/11/2013 16:33:45
OrganizationId :
OriginatingServer : thdc1.ResourceGroup.co.uk
IsValid : True
ObjectState : Changed
RunspaceId : aed28f13-cdd2-4dcf-a0a8-96b8e2518171
ServerName : THCAS2
SSLOffloading : True
ExternalHostname : thcas2.resourcegroup.co.uk
InternalHostname : thcas2.resourcegroup.co.uk
ExternalClientAuthenticationMethod : Ntlm
InternalClientAuthenticationMethod : Ntlm
IISAuthenticationMethods : {Basic, Ntlm, Negotiate}
XropUrl :
ExternalClientsRequireSsl : True
InternalClientsRequireSsl : False
MetabasePath : IIS://THCAS2.ResourceGroup.co.uk/W3SVC/1/ROOT/Rpc
Path : C:\Program Files\Microsoft\Exchange Server\V15\FrontEnd\HttpProxy\rpc
ExtendedProtectionTokenChecking : None
ExtendedProtectionFlags : {}
ExtendedProtectionSPNList : {}
AdminDisplayVersion : Version 15.0 (Build 712.24)
Server : THCAS2
AdminDisplayName :
ExchangeVersion : 0.20 (15.0.0.0)
Name : Rpc (Default Web Site)
DistinguishedName : CN=Rpc (Default Web Site),CN=HTTP,CN=Protocols,CN=THCAS2,CN=Servers,CN=Exchange
Administrative Group (FYDIBOHF23SPDLT),CN=Administrative
Groups,CN=ResourceGroup,CN=Microsoft
Exchange,CN=Services,CN=Configuration,DC=ResourceGroup,DC=co,DC=uk
Identity : THCAS2\Rpc (Default Web Site)
Guid : 39c5133f-14cb-4d44-ae9c-69f7fb0fc432
ObjectCategory : ResourceGroup.co.uk/Configuration/Schema/ms-Exch-Rpc-Http-Virtual-Directory
ObjectClass : {top, msExchVirtualDirectory, msExchRpcHttpVirtualDirectory}
WhenChanged : 26/11/2013 16:23:05
WhenCreated : 26/11/2013 12:49:17
WhenChangedUTC : 26/11/2013 16:23:05
WhenCreatedUTC : 26/11/2013 12:49:17
OrganizationId :
OriginatingServer : thdc1.ResourceGroup.co.uk
IsValid : True
ObjectState : Changed
If anyone could offer any help it'd be much appreciated, it's going to take several days to migrate my remaining 2010 users to 2013 which is causing a lot of use complaints.

Hi Seb,
Try the following please.
1- Remove the existing assigned mailbox permission from the mailbox.
2- Assign the permission (Add-MailboxPermission) with -AutoMapping value set to $false.
3- Launch Outlook. Then add the mailbox manually as an additional mailbox from the Account Settings. (Access to the mailbox by only following this step would also work but your user's then will have the same mailbox displayed twice hence
step 1 & 2)
ecsword

Send As from a shared mailbox stopped working

I have created a Shared Mailbox a few months ago and gave one use full access rights and send as permissions. This worked perfectly since it was created. On Friday, the user started getting:
Delivery has failed to these recipients or groups:
You can't send a message on behalf of this user unless you have permission to do so. Please make sure you're sending on behalf of the correct sender, or request the necessary permission.
If the problem continues, please contact your helpdesk.
There have been no changes made to any of the rights or permissions anywhere. The shared mailbox properties still show this user in the full access and send as list. The shared accounts address is available in the GAL so that is not an issue.
Any ideas would be appreciated. I could probably recreate this mailbox, but would rather fix the issue or at least know what happened in case it does it again.
Nick Laurino

Hi,
Have you tried removing and then re-adding the permission for the user? Worth a try when such issue occurs.
As the administrator, you may want to verify that the user actually does have "Send-As" permission on the shared mailbox. To do that,
Open the Exchange Management Console on the Server
Navigate to Recipient Configuration > Mailbox and right click the Shared Malibox
Select "Manage Send As Permission"
Check that the user is listed in the permissions
To solve the issue on the client side, delete the offline address book and allow Outlook to recreate it.
Close Outlook
Delete the Offline Address Book folder
It can be found under "C:\users\{username}\AppData\Local\Microsoft\Outlook\Offline Address Books"
Open Outlook and it will download a fresh copy of the Offline Address Book
I hope this can be helpful.
Thanks,
Melon Chen
Forum Support
Come back and mark the replies as answers if they help and unmark them if they provide no help.
If you have any feedback on our support, please click
here

Opening a shared mailbox in Outlook 2013 (office 365) returns "Cannot Expand Folder" error.

Hi!
We've just upgraded from our old Domino email server to Office 365 E1 and running an on-premise Exchange 2013 hybrid server.
In Outlook 2013, when trying to expand a shared mailbox, It asks me to enter my outlook credentials. Trying so doesn't work and it continues to ask repeatedly. If I click cancel, I get the following error:
"Cannot expand the folder. The set of folders cannot be opened. Microsoft Exchange is not available.
Either there are network problems or the Exchange server is down for maintenance."
The error only occurs in Outlook 2013 and it happens to all staff who are using Outlook 2013. Shared mailboxes are accessible in Outlook 2010 and OWA with no issues.
I have tried recreating profiles, removing and re-adding permissions, disabling auto-mapping. I've tested with creating shared mailbox in Exchange Online and on our hybrid server.

Hi,
Check if the kb below matches your scenario:
https://support.microsoft.com/kb/2992644
This problem occurs only when the following conditions are true:
You are using Microsoft Outlook 2013 client version 15.0.4641.1001.
The client is connected by using Outlook Anywhere (RPC over HTTP).
To resolve this issue, apply the update that is described in the following article in the Microsoft Knowledge Base:
2889859
If you are using the Click-to-Run version of Office 2013, the Outlook application is kept up to date automatically. For more information about Office 2013 Click-to-Run updates, see
Microsoft Office 2013 Click-to-Run virtualization
I hope the information is helpful.
Regards,
Melon Chen
TechNet Community Support
It's recommended to download and install
Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
programs.

Sent items not saved in personal sent items when shared mailbox is open in outlook

hi,
user is using exchange 2010 and the shared mailboxes are in exchange 2003. when user send an email as send as to the shared mailbox the sent items is not saved in her personal sent items. she can look up the sent items on her shared mailboxes sent items.
I tried recreating her profile when the shared mailboxes are not added in the outlook, personal sent items is okay but when the shared mailboxes is added , sent items doesn't go to her personal sent items. Please help. Is it by design?

Hi,
Since Exchange 2003 server is out of support, I still suggest migrating to Exchange 2010 server.
How about this behavior on OWA, if everything going well as expected, it should be an issue on the Outlook client side.
Please try to run Outlook under safe mode to avoid some AVs and add-ins.
Thanks
Mavis
Mavis Huang
TechNet Community Support

Ex2010 shared mailbox folder won't open in OWA2013

Hi,
I've got simple lab environment:
2x Widnows 2008R2 + Exchange 2010sp3
Widnows 2008R2 + Exchange 2013cu3
1 x test mailbox13 on 2013
1 x test mailbox10 on 2010
I added full access permission on mailbox10 to mailbo13 and want to open it with OWA.
I can do that by "open another mailbox..." option in another browser window but
when I want to "add shared folder..." to folder structure on the left panel:
In Outlook 2010 everything is ok and I can view two mailbox trees on the left.
CalendarFolderConfiguration looks fine and clean.
Any ideas?

Hi,
Firstly, I’d like to explain, OWA 2013 can open all folders while OWA 2010 can open only inbox and calendar.
Open another mailbox makes all folders open in another window. Add shared folder make two mailbox open in the same tab.
And I have a test on my lab: if I add shared folder with an account which I haven’t granted full access permission to , the same error message appears. if the permission is well, I don’t get any error message.
According to your description, Outlook works well. Maybe the issue is related to OWA configuration. Thus,we can use MFCMAPI to remove the IPM.Configuration.Owa.OtherMailbox message hidden in the mailbox and then try again.
Additionally, we can also check if there is any error in the event log to narrow down the cause and try to re-add the full access permission.
Best regards,
Angela Shi
TechNet Community Support

HTTP 500 error when opening a legacy shared mailbox in OWA 2013 (Exchange 2007/2013 coexistence environment)

Hi,
Our Exchange 2013/2007 coexistence environment is set up and all is working apart from this:
Mailbox A has full permissions to Mailbox B. Mailbox A is migrated to Exchange 2013, but Mailbox B remains on Exchange 2007. If I login to Outlook Web App 2013 as Mailbox A and then "Open another mailbox..." and select Mailbox B, a new window opens
up saying "HTTP 500 Internal Server Error". The URL it is trying is :
https://webmail.ourdomain.com/owa/[email protected]/?offline=disabled
( I can open Mailbox A in Outlook 2010 and do "Open Other users's folder.." and Mailbox B opens up just fine. )
Our legacy CAS server's External and Internal URLs are set to :
https://legacy.ourdomain.com/owa
and the Exchange 2013 CAS server's External and Internal URLs are set to :
https://webmail.ourdomain.com/owa
We have FBA enabled on both the E2K7 and E2K13 OWA
In the IIS logs:
2015-03-02 16:36:50 <E2K13_IP> POST /owa/service.svc action=SubscribeToNotification&UA=0&ID=-25&AC=1&CorrelationID=c2899211-568d-4da4-a163-351a8621c9fd_142531419466924;&cafeReqId=7ffae082-a96f-42fd-85f8-bf23775ed5de; 443 ourdomain.com\MailboxA
<LoadBalancer_IP> Mozilla/4.0+(compatible;+MSIE+8.0;+Windows+NT+6.1;+WOW64;+Trident/4.0;+SLCC2;+.NET+CLR+2.0.50727;+.NET+CLR+3.5.30729;+.NET+CLR+3.0.30729;+Media+Center+PC+6.0)
https://webmail.ourdomain.com/owa/#path=/mail 200 0 0 109
2015-03-02 16:36:50 <E2K13_IP> GET /owa/ offline=disabled&CorrelationID=<empty>;&cafeReqId=7c8e137f-cdb7-4449-9cb8-f36f94539244; 443 ourdomain.com\MailboxA <LoadBalancer_IP> Mozilla/4.0+(compatible;+MSIE+8.0;+Windows+NT+6.1;+WOW64;+Trident/4.0;+SLCC2;+.NET+CLR+2.0.50727;+.NET+CLR+3.5.30729;+.NET+CLR+3.0.30729;+Media+Center+PC+6.0)
- 500 0 0 265
In the OWA HTTP Proxy logs:
2015-03-02T16:36:50.096Z,7c8e137f-cdb7-4449-9cb8-f36f94539244,15,0,913,7,,Owa,webmail.ourdomain.com,/owa/,,FBA,True,ourdomain.com\MailboxA,ourdomain.com,[email protected],Mozilla/4.0 (compatible; MSIE 8.0; Windows NT 6.1; WOW64; Trident/4.0; SLCC2;
.NET CLR 2.0.50727; .NET CLR 3.5.30729; .NET CLR 3.0.30729; Media Center PC 6.0),<LoadBalancer_IP>,<Exchange2013ServerName>,500,,ServerNotFound,GET,,,,,ExplicitLogon-SMTP-Header,,,,0,,,,40,9,,0,7;,7,,0,7,,0,46.8643,0,,,,,,,,,1,10,0,,10,,50,50,?offline=disabled,,BeginRequest=2015-03-02T16:36:50.049Z;CorrelationID=<empty>;ProxyState-Run=None;ServerLocatorRefresh=beebf732-0f99-47a0-9f36-d266573f1510;RefreshingCacheEntry=CacheEntry(BackEndServer
<Exchange2007ServerName>.ourdomain.com~1912832083|ResourceForest |LastRefreshTime 2015-03-02T16:01:29.3265514Z|IsSourceCachedData False);ProxyState-Complete=CalculateBackEnd;EndRequest=2015-03-02T16:36:50.096Z;I32:ADS.C[<DC_Name>]=1;F:ADS.AL[<DC_Name>]=6.6401;I32:ATE.C[<DC_Name>.ourdomain.com]=1;F:ATE.AL[<DC_Name>.ourdomain.com]=0,HttpProxyException=Microsoft.Exchange.HttpProxy.HttpProxyException:
The server <Exchange2013ServerName>.ourdomain.com was not found in the topology. ---> Microsoft.Exchange.Data.Storage.ServerNotFoundException: The server <Exchange2013ServerName>.ourdomain.com was not found in the topology.
at Microsoft.Exchange.Data.Storage.ServiceTopology.GetSite(String serverFullyQualifiedDomainName)    at Microsoft.Exchange.Data.ApplicationLogic.Cafe.HttpProxyBackEndHelper.GetServiceTopologyWithSites(String serverFqdn ServiceTopology
topology)    at Microsoft.Exchange.Data.ApplicationLogic.Cafe.HttpProxyBackEndHelper.GetE12ExternalUrl[ServiceType](BackEndServer mailboxServer)    at Microsoft.Exchange.HttpProxy.OwaProxyRequestHandler.GetE12TargetServer(BackEndServer
mailboxServer)    at Microsoft.Exchange.HttpProxy.BEServerCookieProxyRequestHandler`1.GetDownLevelClientAccessServer(AnchorMailbox anchorMailbox BackEndServer mailboxServer)    at Microsoft.Exchange.HttpProxy.LatencyTracker.GetLatency[T](Func`1
operationToTrack Int64& latency)    at Microsoft.Exchange.HttpProxy.ProxyRequestHandler.InternalOnCalculateTargetBackEndCompleted(TargetCalculationCallbackBeacon beacon)    at Microsoft.Exchange.HttpProxy.ProxyRequestHandler.<>c__DisplayClass3b.<OnCalculateTargetBackEndCompleted>b__3a()
--- End of inner exception stack trace ---;
Hoping that somebody can help ?
Thanks

Hi Ansev,
Thank you for your question.
By my testing, user who was migrated to Exchange 2013 cannot access mailbox on Exchange 2007 with 500 error, although user account have “Full Access Permission” to mailbox on Exchange 2007.
I suggest we migrate account which has “Full Access Permission” for other user to Exchange 2013.
If there are any questions regarding this issue, please be free to let me know.
Best Regard,
Jim
Please remember to mark the replies as answers if they help, and unmark the answers if they provide no help. If you have feedback for TechNet Support, contact [email protected]
Jim Xu
TechNet Community Support

Exchange 2013 (Office 365) shared mailbox not staying up to date.

We have created a new shared folder for multiple users to access in Office 365 and were having some issues. There are a few users where this mailbox works great, but others users aren't able to see any changes that are made in the shared mailbox.
Opening the mailbox in O365 shows all folders, emails, etc... but for some reason syncing stops working randomly after a bit of time. Removing and re-adding permissions to the mailbox does fix this issue, but that's not a feasable fix for us.
Users can add folders to the shared mailbox, and those added folders do show up in the mailbox when opened in O365, but the changes do not push down to multiple other clients.
Anyone else seen this or have any info? Thanks!

Hi,
Are the users using Cached Exchange Mode or Online Mode? When the issue comes next time, have the user switch to the other mode and test if this helps.
We can disable Cached Mode for Shared folders, check if this helps resolve the sync issue:
Go to FILE -> Account Settings -> Account Settings -> Double click on the Exchange account -> More Settings -> Advanced tab -> Uncheck "Use Cached Exchange Mode", and click Apply then OK.
In Cached Mode, it doesn't connect to Exchange Server all the time but keeps a cache of the mailbox locally to sync the local cache and mailbox according to a period, this may cause some items not sync immediately. By switching to Online Mode, it should
be immediate.
Regards,
Melon Chen
TechNet Community Support
It's recommended to download and install
Configuration Analyzer Tool (OffCAT), which is developed by Microsoft Support teams. Once the tool is installed, you can run it at any time to scan for hundreds of known issues in Office
programs.

O365 client stopped opening shared mailboxes

Similar Messages

Maybe you are looking for