But admittedly, I've never tried to setup ActiveSync over that connection. Even in cases of highly latent connections on mobile devices, like when traveling overseas on 2G and 3G, I haven't had any users complain about ActiveSync not working. I have maybe 30-40 Android devices (Samsung, HTC, Motorola) all running on Exchange 2010 (v14.1 Build 123.4). Your 449 error seems to be the server telling the client to re-provision. I don't think it is a lack of ActiveSync persmissions for the mailbox, that would prevent the connection wizard from moving forward. No idea what to do about that either.ĭoes this give you a clean bill of health? Īre you using a self signed cert? (though I think you are passed that being an issue)ĭo the users have too many mobile device partnerships? The IIS logs accuse HTTP error 449, that according to Microsoft means that 'insufficient information was provided by the client'. Any ideas?Īnother problem happens with a Samsung Galaxy Tab where I cannot install the ActiveSync account at all. The latency with the server is quite high, but iPhone and iPad have none of those problems, I don't know what to do. After a while it says the connection with the server failed, and later it works. Opening a message will often display no body. It will eventually sync the folder after several minutes. Telling the device to sync manually aparently has no effect, it does not say it failed either.

Once the account is added, I go to the Inbox and there is no mail. I just keep trying without changing the parameters and it eventually works. It takes too long to set up the account, and it will often fail saying the connection with the server failed. Right now it works wonders with iPad and iPhone, but something is happening with Android devices that is driving me crazy.įirst problem happens during the account setup. I have a Windows 2008 R2 Server with Exchange 2010 installed, and I'm having trouble to set up the Microsoft ActiveSync properly.

Microsoft activesync account