View Single Post
Posts: 334 | Thanked: 616 times | Joined on Sep 2010
#182
Originally Posted by ImSoQt View Post
N9 - Mail for Exchange fails after initial synchronization.

This issue may already have been described in this thread or elsewhere. Forgive me if this is the case. Hopefully someone can give me a pointer if this is the case.

A more detailed description.

Mail for Exchange synchronization only works when:
a) The account has just been created.
b) The account has been deactivated and activated again. (easier and my current work around)

The first synchronization works fine, all emails, contacts and calendar data is received and stored in the N9 device. Any subsequent synchronization, gives an error like "Can't connect to the server" (a bit uncertain of the english error message having swedish language in my device).

Only way around the issue is to delete and recreate the account (a) or to deactivate and activate the account (b).

Changing access point between different nets as gprs or wifi doesn't help.
I'm having this exact problem too: disable/enable to MfE account lets me sync once but fails next time, or in the very end stages of first sync. I took the logs, but can't transmit them yet. In short activesync.log says:

[error], Transfer 4343184 : failed with error 3
[error], AS_LIB : Received HTTP status 60003. Factory not created.

Couple of lines later it mentions that JobFolderSync(0x33c218) of job sequence of above errors "completed with bad code 60003, abort".
Then the job sequence is "done with code 60003".

I wouldn't be surprised if this is caused by pretty rotten Exchange 2007 we have, unfortunately maintained by me, but if there are lots of similar errors with other people, then I might be of the hook.
 

The Following 2 Users Say Thank You to Manatus For This Useful Post: