locked
exchange 2010 can not open exchange 2007 owa mailbox RRS feed

  • Question

  • exchange 2010 can not open exchange 2007 owa mailbox
        Our exchange co-existing environment is exchange 2007 and exchange 2010. Everything works well. But now exchange 2010 can not open exchange 2007 owa mailbox.
        I find the log. It is very long. But I need your help.

     

    Request

    Url: https://legacy.gki.tryue.com:443/owa/default.aspx

    User host address: XX

     

    Exception

    Exception type: Microsoft.Exchange.Data.Storage.StoragePermanentException

    Exception message: Cannot open mailbox /O=GKI/OU=staff/cn=Recipients/cn=geell.

     

    Call stack

     

    Microsoft.Exchange.Data.Storage.ConnectionCachePool.OpenMailbox(String serverDn, String userDn, String mailboxDn, Guid mailboxGuid, Guid mdbGuid, Object identity, ConnectFlag connectFlag, OpenStoreFlag openStoreFlag, CultureInfo cultureInfo, String clientInfoString, Boolean secondTry)

    Microsoft.Exchange.Data.Storage.ConnectionCachePool.OpenMailbox(String serverDn, String userDn, String mailboxDn, Guid mailboxGuid, Guid mdbGuid, Object identity, ConnectFlag connectFlag, OpenStoreFlag openStoreFlag, CultureInfo cultureInfo, String clientInfoString, Boolean secondTry)

    Microsoft.Exchange.Data.Storage.ConnectionCachePool.OpenMailbox(String serverDn, String userDn, String mailboxDn, Guid mailboxGuid, Guid mdbGuid, Object identity, ConnectFlag connectFlag, OpenStoreFlag openStoreFlag, CultureInfo cultureInfo, String clientInfoString)

    Microsoft.Exchange.Data.Storage.MailboxSession.Initialize(LogonType logonType, ExchangePrincipal owner, DelegateLogonUser delegateUser, Object identity, OpenMailboxSessionFlags flags)

    Microsoft.Exchange.Data.Storage.MailboxSession.CreateMailboxSession(LogonType logonType, ExchangePrincipal owner, DelegateLogonUser delegateUser, Object identity, OpenMailboxSessionFlags flags, CultureInfo cultureInfo, String clientInfoString)

    Microsoft.Exchange.Data.Storage.MailboxSession.Open(ExchangePrincipal mailboxOwner, WindowsPrincipal authenticatedUser, CultureInfo cultureInfo, String clientInfoString)

    Microsoft.Exchange.Clients.Owa.Core.OwaWindowsIdentity.CreateMailboxSession(ExchangePrincipal exchangePrincipal, CultureInfo cultureInfo)

    Microsoft.Exchange.Clients.Owa.Core.UserOptions.LoadSharedCalendarTimezoneSetting(TimezoneSetting& setting)

    Microsoft.Exchange.Clients.Owa.Core.UserOptions.Load(IList`1 properties)

    Microsoft.Exchange.Clients.Owa.Core.UserOptions.LoadAll()

    Microsoft.Exchange.Clients.Owa.Core.UserContext.Load(OwaContext owaContext)

    Microsoft.Exchange.Clients.Owa.Core.RequestDispatcher.CreateUserContext(OwaContext owaContext, UserContextKey userContextKey, UserContext& userContext)

    Microsoft.Exchange.Clients.Owa.Core.RequestDispatcher.PrepareRequestWithoutSession(OwaContext owaContext, UserContextCookie userContextCookie)

    Microsoft.Exchange.Clients.Owa.Core.RequestDispatcher.InternalDispatchRequest(OwaContext owaContext)

    Microsoft.Exchange.Clients.Owa.Core.RequestDispatcher.DispatchRequest(OwaContext owaContext)

    System.Web.HttpApplication.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()

    System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)

     

    Inner Exception

    Exception type: Microsoft.Mapi.MapiExceptionCallFailed

    Exception message: MapiExceptionCallFailed: Unable to make connection to the server. (hr=0x80004005, ec=2084) Diagnostic context: Lid: 23065 EcDoConnectEx called [length=76] Lid: 17913 EcDoConnectEx returned [ec=0x824][length=56][latency=0] Lid: 19778 Lid: 27970 StoreEc: 0x824 Lid: 17730 Lid: 25922 StoreEc: 0x824

     

    Call stack

     

    Microsoft.Mapi.MapiExceptionHelper.ThrowIfError(String message, Int32 hresult, Int32 ec, DiagnosticContext diagCtx)

    Microsoft.Mapi.ExRpcConnection.Create(ConnectionCache connectionCache, ExRpcConnectionCreateFlag createFlags, ConnectFlag connectFlags, String serverDn, String userDn, String user, String domain, String password, String httpProxyServerName, Int32 ulConMod, Int32 lcidString, Int32 lcidSort, Int32 cpid, Int32 cReconnectIntervalInMins, Int32 cbRpcBufferSize, Int32 cbAuxBufferSize)

    Microsoft.Mapi.ConnectionCache.OpenMapiStore(String mailboxDn, Guid mailboxGuid, Guid mdbGuid, ClientIdentityInfo clientIdentity, String userDnAs, OpenStoreFlag openStoreFlags, CultureInfo cultureInfo, String applicationId)

    Microsoft.Mapi.ConnectionCache.OpenMailbox(String mailboxDn, Guid mailboxGuid, Guid mdbGuid, WindowsIdentity windowsIdentityAs, String userDnAs, OpenStoreFlag openStoreFlags, CultureInfo cultureInfo, String applicationId)

    Microsoft.Exchange.Data.Storage.ConnectionCachePool.OpenMailbox(String serverDn, String userDn, String mailboxDn, Guid mailboxGuid, Guid mdbGuid, Object identity, ConnectFlag connectFlag, OpenStoreFlag openStoreFlag, CultureInfo cultureInfo, String clientInfoString, Boolean secondTry)

     

    Tuesday, August 16, 2011 2:08 PM

Answers

  • According to your error code, I find one similar case.
     
    On the Exchange 2007 server, run this command in the Shell
     
    Set-OrganizationConfig -SharedCalendarTimezoneSetting Principal      

      
    After you run this command, Exchange 2007 will not check the time zone settings of the delegate (in our case, the Exchange 2010 mailbox).
      Since Update Rollup 1 for E2K7 SP3, a new functionality has been introduced. This new functionality forces Exchange 2007 to check the delegate user's SharedCalendarTimeZone parameter.

    • Marked as answer by cbier Wednesday, August 17, 2011 11:53 AM
    Wednesday, August 17, 2011 6:49 AM
  • Terence, You're amazing.. This fixed my problem too!

    Hi Everyone.. here's an article that's worth reading:

    Understanding Proxying and Redirection: Exchange 2010 SP1 Help 

    http://technet.microsoft.com/en-us/library/bb310763.aspx

     

    If an Exchange 2010 (works similarly for 2007) CAS server is configured only with an internal URL the following will occurr:

    If a user connects to a CAS server that is in a different AD site then their exchange server it will proxy the request to another site in many cases (such as mine where I have users who travel alot) this is ideal as the local CAS saver will cache content from the remote exchange server providing a fast experience for the user when travelling. In our environment this has resulted in reduced support costs as there is no client redirection/confusion due to redirects,etc..

    Now here's where it gets interesting (this is mentioned in the above link and supported by MS) if you copy all of your Exchange 2007 versioned owa directories from your Exchange 2007 CAS servers to Exchange 2010 Exchange 2010 will proxy (and cache) to Exchange 2007!

    By versioned directories I mean copy all of the with names like:

    8.0.685.24

    8.0.730.1

    8.0.752.0

    8.1.240.5

    8.1.278.2

    8.1.340.0

    8.1.359.2

    8.2.176.2

    8.2.217.2

    8.2.254.0

    8.3.106.1

    8.3.83.4

    from the Program Files\Microsoft\Exchange Server\ClientAccess\Owa directory to the same directory on an Exchange 2010 cas server. 

    IMPORTANT NOTE make sure that you copy ALL of the directories not just the current versions for ideal compatibility. If you patch 2007 which creates new OWA version directories you will need to copy them to your 2010 cas servers to maintain compatibility.

     

    In my case we've decided NOT to set any external URLs and rely on proxying for OWA/MAPI RPC access. This way we can do without the overly complex/annoying legacy URL process. In our case out webmail is integrated into an internal portal so we've just created a new Global namespace (via F5 GTM) called mail.domain.com and we've told our portal developers to use this namespace for all webmail access. GTM will automatically route the user to the local (i.e. geographically ) Hardware load balancer (F5 LTM) and the the users gets access to the fasted possible webmail. So far all is working well in our lab enviornment and in prod testing and barring any issues we'll be going with this solution for prod.

     

    Hope this helps

    • Marked as answer by Terence Yu Saturday, August 20, 2011 1:16 AM
    Friday, August 19, 2011 2:08 PM

All replies

  • I think the behaviour you are seeing is to be expected.

    OWA on Exchange 2010 only supports Exchange 2010 mailboxes. If you want to open a mailbox on Exchange 2007 then you need to connect to Exchange 2007 OWA. If you want to access both mailboxes through Exchange 2010 OWA then you will need to move the mailbox to Exchange 2010. The version of OWA is driven by the version of the mailbox server that the mailbox is on.

    Simon.


    Simon Butler, Exchange MVP
    Blog | Exchange Resources | In the UK? Hire Me.
    • Proposed as answer by Abhinav Aneja Tuesday, August 16, 2011 3:33 PM
    Tuesday, August 16, 2011 2:36 PM
  • You have 2010 and 2007 coexisitence. Are you unable to getthe legacy url working?

    Please post the deatils about your config - this error accessing owa from external\internal and how did you setup the legacy URL, are you using reverse proxy?

    • Proposed as answer by Abhinav Aneja Tuesday, August 16, 2011 3:33 PM
    • Unproposed as answer by Abhinav Aneja Tuesday, August 16, 2011 3:33 PM
    Tuesday, August 16, 2011 2:59 PM
  • I think the behaviour you are seeing is to be expected.

    OWA on Exchange 2010 only supports Exchange 2010 mailboxes. If you want to open a mailbox on Exchange 2007 then you need to connect to Exchange 2007 OWA. If you want to access both mailboxes through Exchange 2010 OWA then you will need to move the mailbox to Exchange 2010. The version of OWA is driven by the version of the mailbox server that the mailbox is on.

    Simon.


    Simon Butler, Exchange MVP
    Blog | Exchange Resources | In the UK? Hire Me.
    Agreed. 2010 will open there mailbox and 2007 will open there mailbox.
    "Abhi" "Exchange Specialist" ------------- Please remember to click “Mark as Answer” on the post that helps you, and to click “Unmark as Answer” if a marked post does not actually answer your question. This can be beneficial to other community members reading the thread.
    • Proposed as answer by Abhinav Aneja Tuesday, August 16, 2011 3:33 PM
    Tuesday, August 16, 2011 3:02 PM
  • Agreed with Simon, Exchange 2010 does not support Exchange 2007 OWA.

    You need to use separate url for 2007 and 2010.

     

    Thanks


    Mihir Nayak
    Tuesday, August 16, 2011 3:29 PM
  • According to your error code, I find one similar case.
     
    On the Exchange 2007 server, run this command in the Shell
     
    Set-OrganizationConfig -SharedCalendarTimezoneSetting Principal      

      
    After you run this command, Exchange 2007 will not check the time zone settings of the delegate (in our case, the Exchange 2010 mailbox).
      Since Update Rollup 1 for E2K7 SP3, a new functionality has been introduced. This new functionality forces Exchange 2007 to check the delegate user's SharedCalendarTimeZone parameter.

    • Marked as answer by cbier Wednesday, August 17, 2011 11:53 AM
    Wednesday, August 17, 2011 6:49 AM
  • I think the behaviour you are seeing is to be expected.

    OWA on Exchange 2010 only supports Exchange 2010 mailboxes. If you want to open a mailbox on Exchange 2007 then you need to connect to Exchange 2007 OWA. If you want to access both mailboxes through Exchange 2010 OWA then you will need to move the mailbox to Exchange 2010. The version of OWA is driven by the version of the mailbox server that the mailbox is on.

    Simon.


    Simon Butler, Exchange MVP
    Blog | Exchange Resources | In the UK? Hire Me.
    Sorry I don't explain it clearly. I set proxy for it. If exchange 2010 will redirect url to exchange 2007 if it finds mailbox not on 2010 server. 
    Wednesday, August 17, 2011 11:53 AM

  •  
    Set-OrganizationConfig -SharedCalendarTimezoneSetting Principal      

       

    It seems work for my scenario. 
    • Proposed as answer by MSKWIK Wednesday, May 23, 2012 8:19 PM
    Wednesday, August 17, 2011 11:54 AM
  • Terence, You're amazing.. This fixed my problem too!

    Hi Everyone.. here's an article that's worth reading:

    Understanding Proxying and Redirection: Exchange 2010 SP1 Help 

    http://technet.microsoft.com/en-us/library/bb310763.aspx

     

    If an Exchange 2010 (works similarly for 2007) CAS server is configured only with an internal URL the following will occurr:

    If a user connects to a CAS server that is in a different AD site then their exchange server it will proxy the request to another site in many cases (such as mine where I have users who travel alot) this is ideal as the local CAS saver will cache content from the remote exchange server providing a fast experience for the user when travelling. In our environment this has resulted in reduced support costs as there is no client redirection/confusion due to redirects,etc..

    Now here's where it gets interesting (this is mentioned in the above link and supported by MS) if you copy all of your Exchange 2007 versioned owa directories from your Exchange 2007 CAS servers to Exchange 2010 Exchange 2010 will proxy (and cache) to Exchange 2007!

    By versioned directories I mean copy all of the with names like:

    8.0.685.24

    8.0.730.1

    8.0.752.0

    8.1.240.5

    8.1.278.2

    8.1.340.0

    8.1.359.2

    8.2.176.2

    8.2.217.2

    8.2.254.0

    8.3.106.1

    8.3.83.4

    from the Program Files\Microsoft\Exchange Server\ClientAccess\Owa directory to the same directory on an Exchange 2010 cas server. 

    IMPORTANT NOTE make sure that you copy ALL of the directories not just the current versions for ideal compatibility. If you patch 2007 which creates new OWA version directories you will need to copy them to your 2010 cas servers to maintain compatibility.

     

    In my case we've decided NOT to set any external URLs and rely on proxying for OWA/MAPI RPC access. This way we can do without the overly complex/annoying legacy URL process. In our case out webmail is integrated into an internal portal so we've just created a new Global namespace (via F5 GTM) called mail.domain.com and we've told our portal developers to use this namespace for all webmail access. GTM will automatically route the user to the local (i.e. geographically ) Hardware load balancer (F5 LTM) and the the users gets access to the fasted possible webmail. So far all is working well in our lab enviornment and in prod testing and barring any issues we'll be going with this solution for prod.

     

    Hope this helps

    • Marked as answer by Terence Yu Saturday, August 20, 2011 1:16 AM
    Friday, August 19, 2011 2:08 PM
  • thanks for sharing your experience and offer detail document.
    Saturday, August 20, 2011 1:17 AM