Announcement

Collapse
No announcement yet.

OMA not working after configuring OWA SSL and FBA

Collapse
X
  • Filter
  • Time
  • Show
Clear All
new posts

  • OMA not working after configuring OWA SSL and FBA

    I hope someone can help me here,

    I recently configured my exchange 2003 SP2 server to use SSL and Form Based Login. This works perfectly. Because I'm also using a PDA and wants to synchronise everywhere, i had to make a now Virtual Directory exchange-oma as described in MS article 817379. For activesync and OWA everything works fine, except for OMA. When trying to log on to OMA, every client receives the following message:

    If you have recently changed your password, the system may not yet have completed the change. Please wait a short time and try again. If this is not the case, your Exchange server mailbox has not been created. Please access your account via Microsoft Outlook or Microsoft Outlook Web Access to create your user mailbox. Please contact your system administrator for additional assistance.

    Both (password change and mailbox creation) are not the problem.

    In the System Log the following records are shown:

    Event Type: Error
    Event Source: MSExchangeOMA
    Event Category: (1000)
    Event ID: 1803
    Date: 08-04-07
    Time: 13:29:57
    User: N/A
    Computer: SERVER
    Description:
    User [email protected] has either changed the password recently or not yet created a mailbox using an advanced client such as Microsoft(R) Outlook or Outlook Web Access. The back-end server returned a 401 Access Denied error.

    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.


    and

    Event Type: Error
    Event Source: MSExchangeOMA
    Event Category: (1000)
    Event ID: 1503
    Date: 08-04-07
    Time: 13:31:06
    User: N/A
    Computer: SERVER
    Description:
    An unknown error occurred while processing the current request:
    Message: The handle specified is invalid
    Source: System
    Stack trace:
    at System.Net.NTAuthentication.GetOutgoingBlob(Byte[] incomingBlob, Boolean& handshakeComplete)
    at System.Net.NTAuthentication.GetOutgoingBlob(String incomingBlob, Boolean& handshakeComplete)
    at System.Net.NegotiateClient.DoAuthenticate(String challenge, WebRequest webRequest, ICredentials credentials, Boolean preAuthenticate)
    at System.Net.NegotiateClient.DoAuthenticate(String challenge, WebRequest webRequest, ICredentials credentials, Boolean preAuthenticate)
    at System.Net.NegotiateClient.Authenticate(String challenge, WebRequest webRequest, ICredentials credentials)
    at System.Net.AuthenticationManager.Authenticate(Stri ng challenge, WebRequest request, ICredentials credentials)
    at System.Net.AuthenticationState.AttemptAuthenticate (HttpWebRequest httpWebRequest, ICredentials authInfo)

    Message: The remote server returned an error: (401) Unauthorized.
    Source: Microsoft.Exchange.OMA.ExchangeDataProvider
    Stack trace:
    at Microsoft.Exchange.OMA.ExchangeDataProvider.OmaWeb Request.GetRequestStream()
    at Microsoft.Exchange.OMA.ExchangeDataProvider.Exchan geServices.GetSpecialFolders()
    at Microsoft.Exchange.OMA.ExchangeDataProvider.Exchan geServices..ctor(UserInfo user)

    Message: Exception has been thrown by the target of an invocation.
    Source: mscorlib
    Stack trace:
    at System.Reflection.RuntimeConstructorInfo.InternalI nvoke(BindingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture, Boolean isBinderDefault)
    at System.Reflection.RuntimeConstructorInfo.Invoke(Bi ndingFlags invokeAttr, Binder binder, Object[] parameters, CultureInfo culture)
    at System.RuntimeType.CreateInstanceImpl(BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes)
    at System.Activator.CreateInstance(Type type, BindingFlags bindingAttr, Binder binder, Object[] args, CultureInfo culture, Object[] activationAttributes)
    at Microsoft.Exchange.OMA.UserInterface.Global.Sessio n_Start(Object sender, EventArgs e)

    Message: Exception of type Microsoft.Exchange.OMA.DataProviderInterface.Provi derException was thrown.
    EventMessage:
    UserMessage: A System error has occurred while processing your request. Please try again. If the problem persists, contact your administrator.
    Source: Microsoft.Exchange.OMA.UserInterface
    Stack trace:
    at Microsoft.Exchange.OMA.UserInterface.Global.Sessio n_Start(Object sender, EventArgs e)
    at System.Web.SessionState.SessionStateModule.RaiseOn Start(EventArgs e)
    at System.Web.SessionState.SessionStateModule.Complet eAcquireState()
    at System.Web.SessionState.SessionStateModule.BeginAc quireState(Object source, EventArgs e, AsyncCallback cb, Object extraData)
    at System.Web.AsyncEventExecutionStep.System.Web.Http Application+IExecutionStep.Execute()
    at System.Web.HttpApplication.ExecuteStep(IExecutionS tep step, Boolean& completedSynchronously)


    For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.


    I have really no idea what is going on and why OMA is not working anymore.

    When running the ExBPA no warnings are shown in the permissions test.

    I did find MS article 817310 which gives the great solution restarting the Exchange 2003 server, which doesn't help at all. None of the named reasons can be applied to my situation, my server is not heavy loaded and not installed on Windows 2000 Server.

    Anyone who can help me solving this problem, I would prefer using OMA over SSL but if a better solution is available for just HTTP traffic, I would like to hear!
    Last edited by SierdW; 8th April 2007, 13:02.

  • #2
    Re: OMA not working after configuring OWA SSL and FBA

    http://forums.petri.com/showthread.php?t=14032

    http://forums.petri.com/showthread.php?t=12923

    http://forums.petri.com/showthread.php?t=12684

    http://forums.petri.com/showthread.php?t=8261

    Searched manually. For some reason OMA doesn't register in the search tool. There are others (these go back to January 2007) if the above don't help.
    1 1 was a racehorse.
    2 2 was 1 2.
    1 1 1 1 race 1 day,
    2 2 1 1 2

    Comment


    • #3
      Re: OMA not working after configuring OWA SSL and FBA

      Thanks for the links, I'll give it a try and keep you informed

      Comment


      • #4
        Re: OMA not working after configuring OWA SSL and FBA

        Originally posted by biggles77 View Post

        Searched manually. For some reason OMA doesn't register in the search tool. There are others (these go back to January 2007) if the above don't help.
        Maybe an admin can fix this in the search. I've tried searching for many 3 letter words (like EAS, OWA, OMA etc.) and apparantly 3 letters is too short for the search tool.

        Comment

        Working...
        X