QGSmith
asked on
Exchange account on ipad not synchronizing after it was deleted and re-added
I am having difficulty re-adding an Exchange account to a user’s ipad.
The Exchange 2007 has a Godaddy SSl certificate. I was able to add the account once but had to perform a mailbox clean-up on the user mailbox, so I deleted the account from the ipad and then re-added the account after the clean-up (which was done on a desktop computer). The account gets added again but does not sync or download any email when opening the email application on the ipad.
In my attempts to get the account to synchronise I have added and deleted the exchange account a number of times with various settings to no avail.
For the record: The other pop accounts on the ipad still works as normal and no settings on the server has changed as other users can still sync using their ipads.
Please advise how to get the ipad to sync with MS Exchange again.
Thanks
The Exchange 2007 has a Godaddy SSl certificate. I was able to add the account once but had to perform a mailbox clean-up on the user mailbox, so I deleted the account from the ipad and then re-added the account after the clean-up (which was done on a desktop computer). The account gets added again but does not sync or download any email when opening the email application on the ipad.
In my attempts to get the account to synchronise I have added and deleted the exchange account a number of times with various settings to no avail.
For the record: The other pop accounts on the ipad still works as normal and no settings on the server has changed as other users can still sync using their ipads.
Please advise how to get the ipad to sync with MS Exchange again.
Thanks
ASKER CERTIFIED SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
SOLUTION
membership
Create a free account to see this answer
Signing up is free and takes 30 seconds. No credit card required.
ASKER
Not sure how this worked on this same ipad before and suddenly stopped. It turned out to be a server issue afterall.
ASKER