Re: OMA not implemented issue

Hi
you can configure different web sites per application.
So you would have one for OWA with FBA and
one for OMA. Both are secured with SSL.

But you have to have two different names (and certs).

Henry


"Andoni" wrote:

Hi Leif,

Thanks for your advice. I removed the registry entry when setting up the
Exchange-OMA website identifier, changed the SSL settings to secure only the
/Exchange virtual directory and I can log in to the OMA now.

I guess the initial problem was that I had the entire web site on the
exchange server set to use SSL. The only problem now is telling everyone that
they can't use forms-based access to log into OWA any more ;)

Many thanks for your help

Andoni

"Leif Pedersen [MVP]" wrote:

Hi,

Why did you create another 'Web site identifier'? This should not be
necessary when using front-end servers.

This might help:
http://support.microsoft.com/default.aspx?scid=kb;en-us;817379

Leif

"Andoni" <Andoni@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:CD809231-47F2-4FB5-B36D-1E0120636750@xxxxxxxxxxxxxxxx
Hi all,

We are using Win2k3 / Exch2k3sp2.

I have our webmail successfully secured using SSL and this works fine from
the internet and internally.

However, I am now trying to implement OMA and this does not work. I
receive
the following error message in the event log of the front end servers:

----------------------------------------------

Event ID 1503
Source: MSExchangeOMA

An unknown error occurred while processing the current request:
Message: The remote server returned an error: (501) Not Implemented.
Source: Microsoft.Exchange.OMA.ExchangeDataProvider
Stack trace:
at
Microsoft.Exchange.OMA.ExchangeDataProvider.OmaWebRequest.GetRequestStream()
at
Microsoft.Exchange.OMA.ExchangeDataProvider.ExchangeServices.GetSpecialFolders()
at
Microsoft.Exchange.OMA.ExchangeDataProvider.ExchangeServices..ctor(UserInfo
user)

Message: Exception has been thrown by the target of an invocation.
Source: mscorlib
Stack trace:
at System.Reflection.RuntimeConstructorInfo.InternalInvoke(BindingFlags
invokeAttr, Binder binder, Object[] parameters, CultureInfo culture,
Boolean
isBinderDefault)
at System.Reflection.RuntimeConstructorInfo.Invoke(BindingFlags
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.Session_Start(Object
sender, EventArgs e)

Message: Exception of type
Microsoft.Exchange.OMA.DataProviderInterface.ProviderException 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.Session_Start(Object
sender, EventArgs e)
at System.Web.SessionState.SessionStateModule.RaiseOnStart(EventArgs e)
at System.Web.SessionState.SessionStateModule.CompleteAcquireState()
at System.Web.SessionState.SessionStateModule.BeginAcquireState(Object
source, EventArgs e, AsyncCallback cb, Object extraData)
at
System.Web.AsyncEventExecutionStep.System.Web.HttpApplication+IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean&
completedSynchronously)


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

-------------------------

We have 2 front end servers configured in the DMZ as webmail servers, and
are also our mail relay servers.

In IIS, on the default website I have added another 'Web site identifier'
entry similar to the existing one except this one has the host header
value
equal to the FQDN of the server.

On the default web site I have enabled SSL, however I have disabled this
on
the OMA virtual directories. Should it be configured this way, or should I
be
disabling SSL on the default web site and enabling it on the /exchange
virtual directory only?

In the ESM I have disabled forms-based authentication on both servers.

Any help anyone could provide I would be most grateful.

Thanks

Andoni



.

Relevant Pages

  • RE: OMA not implemented issue
    ... I have our webmail successfully secured using SSL and this works fine from ... I am now trying to implement OMA and this does not work. ... the following error message in the event log of the front end servers: ... invokeAttr, Binder binder, Objectparameters, CultureInfo culture, Boolean ...
    (microsoft.public.exchange.setup)
  • Re: OMA not implemented issue
    ... changed the SSL settings to secure only the ... Why did you create another 'Web site identifier'? ... necessary when using front-end servers. ... invokeAttr, Binder binder, Objectparameters, CultureInfo culture, ...
    (microsoft.public.exchange.setup)
  • IIS + Network Load Balancing + Multiple SSL sites
    ... We have a 2 servers that are network load balanced ... Each web site we ... One of which uses the standard SSL port of ... for SSL. ...
    (microsoft.public.inetserver.iis.security)
  • Re: ActiveSync, Exchange 2003, Sprint Audivox pp6600
    ... I have a single server solution, default web site is ... I have SSL set on OWA and OMA but not on the ...
    (microsoft.public.exchange.setup)
  • Re: ActiveSync, Exchange 2003, Sprint Audivox pp6600
    ... I have a single server solution, default web site is ... I have SSL set on OWA and OMA but not on the ...
    (microsoft.public.pocketpc)