Re: OMA will not work, argh!!! Please HELP
From: Tim Hackbart [MSFT] (Timhack_at_online.microsoft.com)
Date: 05/13/04
- Next message: Rand Williams [MSFT]: "Exchange 5.5 Migration Process"
- Previous message: Paul Notredame: "Re: Message transfer fails between 5.5 and 2003"
- In reply to: Kevin: "Re: OMA will not work, argh!!! Please HELP"
- Messages sorted by: [ date ] [ thread ]
Date: Thu, 13 May 2004 16:45:24 -0500
Good points Kevin.
I am glad that you did get the answer, even if msexchange.org beat me to it
<g>
-- 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@elsoliz.com> wrote in message news:cbed01c43929$e12afdf0$a101280a@phx.gbl... > Tim, > > Thanks so much for responding. Turns out all it was was > the host header issue for the exchange website in IIS. I > posted this issue in two places and the good folks over at > msexchange.org answered it first. > > What I was puzzled at was the fact I was getting a 400 > HTTP bad request. I knew it had to be related to the way I > was connecting to OMA, just would have never thought the > host header and assigning an IP address under properties > would have messed that up. I assumed I needed the host > header if I ran multiple websites under IIS, which I do. > > The host header stuff was the only thing I hadnt tried > from everything you posted below. MS should really include > a reference to it in one of the currect KB articles > regarding OMA and SSL. > > Anyways thanks again for the response, > Kevin > > >-----Original Message----- > >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@elsoliz.com> wrote in message > >news:717401c42fac$e4419480$a001280a@phx.gbl... > >> 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@XXX.com 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 > > > > > >. > >
- Next message: Rand Williams [MSFT]: "Exchange 5.5 Migration Process"
- Previous message: Paul Notredame: "Re: Message transfer fails between 5.5 and 2003"
- In reply to: Kevin: "Re: OMA will not work, argh!!! Please HELP"
- Messages sorted by: [ date ] [ thread ]
Relevant Pages
|
Loading
