Re: OMA will not work, argh!!! Please HELP



I'm having the same problem. I'm going to impliment Method 2 on KB 817379.
But I have a couple of questions. Should the procedures in KB 898131 and
817379 both be performed? Also, the "URL that OMA builds"? On my phone I
will type http://mail/exchange-oma/admin? Where is name resolved at to know
that mail is my server and not mail.mycompany.com? Something seems like it
is missing here. Thanks, Mike Lawson
"Tim Hackbart [MSFT]" <Timhack@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:el6BMEVMEHA.1192@xxxxxxxxxxxxxxxxxxxxxxx
> Sorry this has been so frustrating.
>
> Let me make sure I understand your current setup. You have a single
server
> with SSL enabled and REQUIRED on the Exchange virtual directory, correct?
> This of course will break OMA as OMA builds a URL to
> HTTP://Backend/Exchange/Alias, so if /exchange requires SSL, OMA will
fail.
> To get around that you need to create a new virtual directory in the ESM,
> then set the registry key to tell OMA to use this VDir instead of
\Exchange
> as described in those 2 KB's
> This way the URL built will be Http://Backend/AlternateVdir/Alias
>
> Note, you must not require SSL on this alternate Vdir and you must not
have
> Host headers that interfere.
>
> 400 bad request is usually when IIS can not find the Web Site you are
> requesting. OMA builds a URL with the Netbios name of the Exchange server
> that hosts your mailbox.
> So lets say your Single server is named Mail.company.com and your user is
> Admin and your Alternate Vdir from above is "Exchange-oma"
> The URL that OMA builds will be
> Http://Mail/exchange-oma/admin
> IF you have modified the HTTP identities of your Default Web Site that
does
> not include "Mail" as a Host header, you will get a 400.
> If you have modified the HTTP identities then make sure you either go back
> to the default, "All Unassigned" "80" and NO host headers, OR add a HTTP
> identity with the Netbios name of the Server, in my example "all
unassigned"
> "80" "Mail"
>
> Let me know if this helps or confuses the issue.
>
> --
> Tim Hackbart M.C.S.E.
> This posting is provided "AS IS" with no warranties, and confers no
rights.
>
> Please do not send email directly to this alias. This alias is for
newsgroup
> purposes only.
>
> "Kevin" <kevin@xxxxxxxxxxx> wrote in message
> news:717401c42fac$e4419480$a001280a@xxxxxxxxxx
> > I have been trying to get OMA to work for weeks now and
> > everything I have tried hasnt helped, I'm soooo
> > frustrated with this... I really hope you guys can help.
> >
> > Here is my setup...
> >
> > Single server with Exch '03 and Win 2003 Server standard.
> > I'm using a 3rd party SSL cert for OWA. The server is
> > setup with everything working except OMA. I get the 1507
> > Event ID in event viewer and sometimes 1805 both relating
> > to 400 Bad Requests. Here is the 1805 error
> >
> > Request from user XXX@xxxxxxx resulted in the Microsoft
> > (R) Exchange back-end server XXXXX returning an HTTP
> > error with status code 400:Bad Request
> >
> > * FYI this is not a FE/BK setup, its a single server*
> >
> > Response:
> > Content-Type: text/html
> > Date: Sat, 01 May 2004 18:00:32 GMT
> > Connection: close
> > Content-Length: 39
> >
> > <h1>Bad Request (Invalid Hostname)</h1>
> >
> > Orignal Request:
> > Content-Type: text/xml
> > Depth: 0
> > Content-Length: 389
> > Expect: 100-continue
> > Host: XXXXX
> >
> > All the server name and address details have been
> > removed. Anyways, when I go to IE to try log into
> > http://servername/oma I get a login prompt and then after
> > I log in I get this...
> >
> > Unable to connect to your mailbox on server XXXXXX.
> > Please try again later. If the problem persists contact
> > your administrator.
> >
> > What is strange about this is the HTTP title on the IE
> > toolbar says (Server off-line) which I know its not but
> > for some reason OMA things it is...At this point Im stuck
> > I have messed with this for sooo long my head is
> > spinning. I have tried just about every KB article on
> > these issues...See Q817379 and Q822177
> >
> > If anyone has any other suggestion I would really
> > appreciate it. Let me know if you need anymore info about
> > my setup
> >
> > -Kevin
>
>


.



Relevant Pages

  • Re: OMA will not work, argh!!! Please HELP
    ... > the host header issue for the exchange website in IIS. ... > regarding OMA and SSL. ... > have a single server ... >>400 bad request is usually when IIS can not find the Web ...
    (microsoft.public.exchange.setup)
  • Re: Activesync by Air not working after adding second Sharepoint Site!
    ... a bad request to the server. ... Double Verify the Exchange server default Web site listener. ... Check if you are able to visit the OMA site from a client with IE. ... A suggestion would be to contact Microsoft Product Support Services via ...
    (microsoft.public.windows.server.sbs)
  • RE: OMA not accessible
    ... If this is not the case, your Exchange ... Microsoft Outlook or Microsoft Outlook Web Access to create your user ... This problem may occur if the Exchange Server 2003 computer is heavily ... the OMA virtual directory may corrupted on SBS. ...
    (microsoft.public.windows.server.sbs)
  • Re: OMA/ActiveSync debugging
    ... Here is what I associated with an OMA connect attempt in the HTTPERR log: ... Can I conclude that the inability to locate PropFind is causing my problem ... "Was the server a DC and you demoted it to a member server?" ... "Does OWA work?" ...
    (microsoft.public.exchange.admin)
  • Re: Exchange-oma
    ... Is this why I cannot run OWA and OMA? ... CEICW and told the server to open access to everything (OWA, OMA). ... I would like to kindly let you know that in SBS ...
    (microsoft.public.windows.server.sbs)