Numerous users claim they cannot setup their “Corporate” email account

Nov 24, 2013 09:31 GMT  ·  By

There's been lots of excitement around Google's recent Android 4.4 KitKat release, but not all is well with the new platform. It looks like some users are experiencing issues with the Microsoft Exchange servers when trying to set up their “Corporate” email accounts.

AndroidPolice reports numerous Android 4.4 KitKat users are simply unable to set up a connection to their Exchange account, even though they had no troubles with previous versions of Google's operating system.

Sadly, this means the problem lies within KitKat programming, thus putting those who already acquired their Nexus 5 device is the position of not being able to use them at their full potential.

Apparently the symptoms may vary from user to user, as some are getting an error message that says their phone “Can't connect to server.”

Some of them manage to get passed this error by entering the domainusername syntax instead of filling in their email address, but this won't get you further on.

Those who have been successful in setting up their Microsoft Exchange accounts even after getting this error report they do not receive new messages, but their phones' batteries are now draining faster than before.

Some tech-savvy Android enthusiasts claim these problems are related to the way KitKat's Exchange apk creates and stores certificates and credentials.

Users who upgraded to Android 4.4 from a previous version claim existing certificates continue to work without experiencing any issues, while the newly produced connections can't be used.

The bad news is, for the time being there's no workaround that might fix this Microsoft Exchange issue. Some temporary solutions like switching from Push to Pull emails doesn't really solves the problem, as some users report this method still didn't do the trick for them.

Fortunately, Google acknowledged the issues and already has a fix in the works. In fact the search giant tagged the problem with the “FutureRelease” status on AOSP Issue Tracker, which means the bug fix is likely to be completed and will soon hit general public. Stay tuned for more info on the matter.