OMA - unable to connect to your mail server - Application log error eventid:1805 error: 400


Searching forums and web, there are a number of references to this error,

but most are for the 403 whereas the error we receive in the application log is 400.

 

As mentioned its a tricky one. So far I have verified according to kb docs and others sources.

-OMA vdir is set to basic authentication, domain is set to "our domain". (In fact all of the

relevant vdirs: OMA, exchange-oma, microsoft-server-activesync, Exchange, Exchweb, have been

double checked against an SBS server that does work for authentification and SSL.  


-.net framework 1.1.4322.573. Reinstalled: "aspnet_regiis.exe -i". Although one curiousity is that the ASP.NET

tab does not appear on this server.


-ExchangeVDir key is set to the proper exchange-oma vdir

-no host headers on default web site and using the standard ports.

-have re-run the CEICW

-Mobile access IS enabled globally and individually

 
Error message in log is as follows:  Source: MSExchangeOMA, Category:(1000), EventId:1805

Request from user test@BCN.local resulted in the Microsoft(R) Exchange back-end server SERVER1 returning an HTTP error with status code 400

Response:
Cache-Control: private
Content-Length: 0
Server: Microsoft-IIS/6.0
MicrosoftSharePointTeamServices: 6.0.2.5530
X-Powered-By: ASP.NET
Public-Extension: http://schemas.microsoft.com/repl-2
Date: Mon, 10 Jul 2006 09:57:10 GMT


Original Request:
Content-Type: text/xml
Depth: 0
Content-Length: 389
vehastingsAsked:
Who is Participating?
 
ee_ai_constructConnect With a Mentor Commented:
PAQ / Refund
ee ai construct, community support moderator
0
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
If you look in IIS, Servername > Application Pools.  Do you have an ExchangeMobileBrowseApplicationPool?  With a directory below for /LM/W3SVC/1/root/OMA?

Jeff
TechSoEasy
0
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
Also, if that's there, can you access OMA via http://localhost/oma ?

Jeff
TechSoEasy
0
Free Tool: SSL Checker

Scans your site and returns information about your SSL implementation and certificate. Helpful for debugging and validating your SSL configuration.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
Ah... in testing this on my machine I just noticed that my .Net Framework is version 1.1.4322.2300 which is SP1.  You need to install that.

Jeff
TechSoEasy
0
 
vehastingsAuthor Commented:
Hi Thanks for your suggestions but I have just managed to fix it.  We had changed the host header on the company web to server1.  When we changed it back to companyweb it worked fine.

0
 
Jeffrey Kane - TechSoEasyPrincipal ConsultantCommented:
oh... that would probably be a problem... but you still should patch .Net Framework when you get a chance.

Jeff
TechSoEasy
0
 
vehastingsAuthor Commented:
thanks for your help will do patch.
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.