Exchange 2010 unable to open another mailbox via OWA
Hi guys,
Recently I've tried to open another mailbox using OWA, but got an error:
Request
Url: https://exchangesrv2:443/owa/
User host address: 192.168.10.7
OWA version: 14.2.318.2
Exception
Exception type: System.ArgumentNullException
Exception message: Value cannot be null. Parameter name: organizationId
Call stack
Microsoft.Exchange.Data.Directory.ScopeSet.GetOrgWideDefaultScopeSet(OrganizationId organizationId, QueryFilter recipientReadFilter)
Microsoft.Exchange.Data.Directory.ADSessionSettings.FromOrganizationIdWithoutRbacScopesServiceOnly(OrganizationId scopingOrganizationId)
Microsoft.Exchange.Clients.Owa.Core.Utilities.CreateADRecipientSession(Boolean readOnly, ConsistencyMode consistencyMode, SmtpDomain smtpDomain)
Microsoft.Exchange.Clients.Owa.Core.OwaMiniRecipientIdentity.UpgradePartialIdentity()
Microsoft.Exchange.Clients.Owa.Core.RequestDispatcher.PrepareRequestWithoutSession(OwaContext owaContext, UserContextCookie userContextCookie)
Microsoft.Exchange.Clients.Owa.Core.RequestDispatcher.AcquireAndPreprocessUserContext(OwaContext owaContext, HttpRequest request)
Microsoft.Exchange.Clients.Owa.Core.RequestDispatcher.InternalDispatchRequest(OwaContext owaContext)
Microsoft.Exchange.Clients.Owa.Core.RequestDispatcher.DispatchRequest(OwaContext owaContext)
Microsoft.Exchange.Clients.Owa.Core.OwaRequestEventInspector.OnPostAuthorizeRequest(Object sender, EventArgs e)
System.Web.HttpApplication.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
I have full access permissions to selected mailbox.
Please help me to sort it out.
August 15th, 2012 8:55pm
Whats the url you're using?
https://mail.company.com/owa/otheruser@company.comJames Chong MCITP | EA | EMA; MCSE | M+, S+ Security+, Project+, ITIL msexchangetips.blogspot.com
Free Windows Admin Tool Kit Click here and download it now
August 15th, 2012 9:23pm
Thanks James for reply.
My URL is: https://exchangesrv2/owa/user@domain.com
Then I put MY login and pass and got that error.
Same error even for user's mailbox which is already attached to my Outlook 2010.
August 15th, 2012 9:36pm
Can you confirm if this is happening with just this user or it's occuring with any user you shared out?James Chong MCITP | EA | EMA; MCSE | M+, S+ Security+, Project+, ITIL msexchangetips.blogspot.com
Free Windows Admin Tool Kit Click here and download it now
August 15th, 2012 10:26pm
It's happening with any user. Not only with specific one.
August 15th, 2012 10:46pm
Same problem after RU4
Free Windows Admin Tool Kit Click here and download it now
August 16th, 2012 3:44am
Hi,
Can you open the other users mailbox via the following method:
http://hosting.intermedia.net/support/kb/default.asp?id=1831
Thanks,
Simon Wu
Exchange Forum Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
tnmff@microsoft.com
August 16th, 2012 6:03am
Hi,
Can you open the other users mailbox via the following method:
http://hosting.intermedia.net/support/kb/default.asp?id=1831
Thanks,
Simon Wu
Exchange Forum Support
Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
tnmff@microsoft.com
Free Windows Admin Tool Kit Click here and download it now
August 16th, 2012 6:08am
Always the problem with this method.
With new users created after
RU4 and give full access control to the new mailbox, it's working....
August 16th, 2012 8:09am
Try running set-mailbox user -applymandatoryproperties again.James Chong MCITP | EA | EMA; MCSE | M+, S+ Security+, Project+, ITIL msexchangetips.blogspot.com
Free Windows Admin Tool Kit Click here and download it now
August 16th, 2012 2:45pm
Hi Simon,
As I know using this method other user's mailbox will be added to the Outlook and then download whole user's mailbox - it's not convenient with huge size mailboxes.
Thanks for advise
August 20th, 2012 10:28pm
Hi Qwertz,
Sorry, I'm unable to confirm that, because all my users have been created before RU4
Free Windows Admin Tool Kit Click here and download it now
August 20th, 2012 10:30pm
I didn't try -ApplyMandatoryProperties, but found the source of problem. I'm getting that error if using: https://exchangesrv2/owa/user@domain.com, where user@domain.com is
external address, but there are no problems if use https://exchangesrv2/owa/user@domain.local -
local address.
With local address I can open other mailbox without any issues.
Also I've found that after successful mailbox open, user's mailbox appeared within my Outlook. Is there any chance do not download user's mailbox to PC and use only OWA?
Thanks
August 20th, 2012 11:15pm
We had the same problem over here. All servers patched to Exchange 2010 SP2 RU4 last week (before this we were running on Exchange 2010 SP2 RU1). Before this rollup, users were able to switch in OWA to other users with an "external" primary mailadres.
After the update, they started receiving this error. I added this "external" address on our Hub servers as an Accepted (authoritative) domain and the problem was gone.
Free Windows Admin Tool Kit Click here and download it now
September 5th, 2012 10:16am
We had the same problem over here. All servers patched to Exchange 2010 SP2 RU4 last week (before this we were running on Exchange 2010 SP2 RU1). Before this rollup, users were able to switch in OWA to other users with an "external" primary mailadres.
After the update, they started receiving this error. I added this "external" address on our Hub servers as an Accepted (authoritative) domain and the problem was gone.
September 5th, 2012 10:20am
Thanks B.Peeters think you nailed it.
Just as a note though, I implemented your suggestion and it resolved the issue but I had to remove it as we have an EXIM gateway system that is responsible for our distribution list and email alias management and this change means that any addresses hosted
on our gateway system are returned non deliverable by Exchange (understandably) before getting to our gateway system. So I went back and added the domain as an "internal relay" which works for both.
Free Windows Admin Tool Kit Click here and download it now
September 11th, 2012 5:10am