Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 13418
  • Last Modified:

OWA 2010 error. Your mailbox appears to be unavailable.

Got a weird issue. When attempting to log in to another user's mailbox via OWA, I receive the following error:

Your mailbox appears to be unavailable. Try to access it again in 10 seconds. If you see this error again, contact your helpdesk.

I have tried this two different way.

1. https://customerurl.com/owa/user@domain.com. I get the log in page, but after entering the credentials, I get the error.

2. Log in to OWA as myself, choose my name in the top right, type in the mailbox I want to open, then get the error.

I have verified that the permissions are correct for the mailbox I am trying to access, and this used to work. I have also verified via Test-ServiceHealth that required services are running. Application logs don't show anything that relates to this error.
0
Chuck Cobern
Asked:
Chuck Cobern
  • 7
  • 6
1 Solution
 
Benjamin MOREAUProject ManagerCommented:
Try to add "Full Access" Rights via Exchange Management Console for the owner of the mailbox on his own mailbox.
0
 
Chuck CobernAuthor Commented:
Gave the user full access permission to his own mailbox, but still getting the same error.
0
 
Benjamin MOREAUProject ManagerCommented:
Could you post the result of :

Test-ServiceHealth | Select ServicesNotRunning | foreach { Start-Service $_.ServicesNotRunning }
0
Simplify Active Directory Administration

Administration of Active Directory does not have to be hard.  Too often what should be a simple task is made more difficult than it needs to be.The solution?  Hyena from SystemTools Software.  With ease-of-use as well as powerful importing and bulk updating capabilities.

 
Chuck CobernAuthor Commented:
ForEach-Object : Cannot bind argument to parameter 'Name' because it is an empty array.
0
 
Benjamin MOREAUProject ManagerCommented:
OK, just post the result of Test-ServiceHealth
0
 
Chuck CobernAuthor Commented:
[PS] C:\Windows\system32>Test-ServiceHealth


Role                    : Mailbox Server Role
RequiredServicesRunning : True
ServicesRunning         : {IISAdmin, MSExchangeADTopology, MSExchangeIS, MSExchangeMailboxAssistants, MSExchangeMailSub
                          mission, MSExchangeRepl, MSExchangeRPC, MSExchangeSA, MSExchangeSearch, MSExchangeServiceHost
                          , MSExchangeThrottling, MSExchangeTransportLogSearch, W3Svc, WinRM}
ServicesNotRunning      : {}

Role                    : Client Access Server Role
RequiredServicesRunning : True
ServicesRunning         : {IISAdmin, MSExchangeAB, MSExchangeADTopology, MSExchangeFBA, MSExchangeFDS, MSExchangeMailbo
                          xReplication, MSExchangePOP3, MSExchangeProtectedServiceHost, MSExchangeRPC, MSExchangeServic
                          eHost, W3Svc, WinRM}
ServicesNotRunning      : {}

Role                    : Hub Transport Server Role
RequiredServicesRunning : True
ServicesRunning         : {IISAdmin, MSExchangeADTopology, MSExchangeEdgeSync, MSExchangeServiceHost, MSExchangeTranspo
                          rt, MSExchangeTransportLogSearch, W3Svc, WinRM}
ServicesNotRunning      : {}
0
 
Benjamin MOREAUProject ManagerCommented:
Have you try (if you can) to restart the Information Store service ?
0
 
Chuck CobernAuthor Commented:
I would probably have to wait till after hours. I would assume user impact if I restart it now.
0
 
Benjamin MOREAUProject ManagerCommented:
Ok.

Do you try to access your user mailbox with an administrator mailbox... When you are loggin on OWA, do you use an admin account ? If YES, could you try tu use a user account with access right "full access" on your second user ?
0
 
Chuck CobernAuthor Commented:
The user that I was using does have full access permissions to the mailbox in question. I need to verify, but I think I resolved this issue by removing the permissions.

Remove-Mailbox -identity <alias> -User <alias> -AccessRights FullAccess

Then I add it back:

Add-Mailbox -identity <alias> -User <alias> -AccessRights FullAccess

When I go back to OWA, I can now access that one users mailbox. I was having this problem with several mailboxes so I will go and verify on the other mailboxes.
0
 
Benjamin MOREAUProject ManagerCommented:
Ok, Check & post your result :)
0
 
Chuck CobernAuthor Commented:
It was an issue with the permissions. Removing and readding the full access permissions cleared the problem. Thank you for your help. :)
0
 
Chuck CobernAuthor Commented:
Through troubleshooting the issue, I was able to come upon the answer myself.
0

Featured Post

Industry Leaders: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

  • 7
  • 6
Tackle projects and never again get stuck behind a technical roadblock.
Join Now