none
Exchange 2010 unable to open another mailbox via OWA RRS feed

  • Question

  • 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.

    Thursday, August 16, 2012 12:50 AM

Answers

  • 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.

    Wednesday, September 5, 2012 2:16 PM
  • Hi,

    Can you open the other user’s 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

    Thursday, August 16, 2012 10:03 AM
    Moderator

All replies

  • Whats the url you're using? https://mail.company.com/owa/otheruser@company.com

    James Chong MCITP | EA | EMA; MCSE | M+, S+ Security+, Project+, ITIL msexchangetips.blogspot.com

    Thursday, August 16, 2012 1:18 AM
  • 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.
    • Edited by IT Jericho Thursday, August 16, 2012 1:34 AM
    Thursday, August 16, 2012 1:31 AM
  • 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

    Thursday, August 16, 2012 2:21 AM
  • It's happening with any user. Not only with specific one.
    Thursday, August 16, 2012 2:41 AM
  • Same problem after RU4


    • Edited by Técé Thursday, August 16, 2012 7:40 AM
    Thursday, August 16, 2012 7:40 AM
  • Hi,

    Can you open the other user’s 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

    Thursday, August 16, 2012 10:03 AM
    Moderator
  • Always the problem with this method.
    With new users created after RU4 and give full access control to the new mailbox, it's working....

    Thursday, August 16, 2012 12:04 PM
  • Try running set-mailbox user -applymandatoryproperties again.

    James Chong MCITP | EA | EMA; MCSE | M+, S+ Security+, Project+, ITIL msexchangetips.blogspot.com

    Thursday, August 16, 2012 6:40 PM
  • 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

    Tuesday, August 21, 2012 2:23 AM
  • Hi Qwertz,

    Sorry, I'm unable to confirm that, because all my users have been created before RU4

    Tuesday, August 21, 2012 2:25 AM
  • 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

    Tuesday, August 21, 2012 3:10 AM
  • 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.

    Wednesday, September 5, 2012 2:16 PM
  • 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.


    • Edited by MattH077909 Tuesday, September 11, 2012 9:20 AM
    Tuesday, September 11, 2012 9:05 AM