I also have an issue since PR1.2
I am used to read my emails offline after having sync my work mails

For some reason, since PR1.2, some emails cannot be shown offline. It is requesting a connection.

I have another issue as well with was already the case before PR1.2 and I wonder if anybody understand why.
For some reasons, to sync with my work mails, I have to open parameters, save them (without changing anything) before sync otherwise it will just not work!?

@Juhnu

Maybe it's a time-out issue. Vitaly told me to try the following at least for testing purposes.

If MfE account is not configured yet, when MfE wizard is started, somewhere between entering credentials and first sync page, switch to x-terminal application
and execute the following commands:
gconftool-2 -s --type=int /apps/activesync/ActiveSyncAccount1Temp/timeout1 600
gconftool-2 -s --type=int /apps/activesync/ActiveSyncAccount1Temp/timeout2 -- -1
gconftool-2 -s --type=int /apps/activesync/ActiveSyncAccount1Temp/timeout3 -- -1

Or for already configured account, execute the following commands from x-terminal:

gconftool-2 -s --type=int /apps/activesync/ActiveSyncAccount1/timeout1 600
gconftool-2 -s --type=int /apps/activesync/ActiveSyncAccount1/timeout2 -- -1
gconftool-2 -s --type=int /apps/activesync/ActiveSyncAccount1/timeout3 -- -1

"-1" means "wait forever".

After having those changes made open properties tab of MfE and click "save" so that those change will take effect on next sync.

Thanks tomster. I changed the time-outs as instructed, but still the problem remains. I have attached a full syslog where:

• Existing MfE setup in N900 used
• N900 calendar cleared of any entries
• Only calendar sync is active
• Run "Full resynchronisation"
• When Mfe sync hangs, wait a bit and then cancel sync

I can't find any clear errors from the log that would point to a sync problem.

I did a test with another "clean" Exchange account (it has had no calendar activity ever). I had only calendar sync enabled. With this account the sync goes through.

I had the very same problem when upgrading to PR1.2. Only difference is that I am on a Scalix Server instead of Exchange. In technical terms this means I have to use the sync protocol (EAS) pre-set to version 2.5 as described in the Heartbeat Wiki. Not sure whetther Exchange 2003 would require this as well...

I set up a new account after upgrading to PR 1.2 and could only manage to sync 1 time. From there sync failed any time I had the calendar check box activated. The logs also showed a time-out on calendar sync. I'd guess (though can't read the logs in detail) that there was some sort of mis-communication between server and device on sync flags. Either server or device couldn't determine what content already has been synced and what hasn't.

After talking to Vitaly he suggested to try the above mentioned fix (on a existing account). In my case it didn't help either. At least not instantly.

I then deleted/cleared the calendar on my device and tried again. From there everything worked fine and sync is back up again.

As of my experience I'd suggest the following (if applicable in your scenario):

Be careful with deletion of contacts or calendar on device. Though sync fails, chances are that deleting the data from your device also deletes data on your server! I ran into that...

Backup
Delete MfE account
Delete contacts and calendar on device
Set up a new account (might wanna try time-out fix or EAS 2.5)
Run initial full sync (email, calendar and contatcs)
On 2nd sync calendar should give you the same troubles again
uncheck calendar in MfE properties
delete calendar on device again
Do a normal sync without calendar -> sync should work fine now
Now activate calendar sync again in MfE properties
Do NOT do a full resync
Sync manually

In my case it worked from there.

--edit--
After reading your logs more carefully I am no longer that sure that your issues are the same as mine. I don't see a time-out or http 500 error...

MfE on the N900 works with Exchange 2010
If initial sync still fails (even if all settings are ok), please check the solution here. It's a server side permission problem that your admin can easily resolve.

I think synching Email causes a problem. If you just synch contacts and calendar it should work (although i did not synch contacts)

tomster, thanks for your detailed post. I tried the same but it did NOT work for me on my
N900 PR1.2 Exchange Server 2003 with 'Enable Unsupported Devices' checked.

You're welcome. Just trying to help...

As I wrote above I do not have experience with MS Exchange servers at all. But I do remember that MfE didn't work on Exchange 2003 with factory-new firmware. This has been fixed in one of the subsequent releases.

In my case sync even then didn't work out of the box because there were problems with auto-negotitation on initial contact. Seemed like my device and Scalix server couldn't agree which EAS protocol version to use. Vitaly came up with a work-around pre-setting EAS to v 2.5 permanently as described in the Heartbeat Wiki. Since then everything worked like a charm on PR 1.1.1 - until PR 1.2 came out.

Though trying to set up the MfE-account on both a OTA-updated device as well as a flashed-from-scratch one I didn't succeed. Also the fix to enlonging time-outs didn't work. Finally I got it up and running by following the above mentioned steps. More or less trial'n'error ;-)

But be patient. Vitaly will read through this thread from time to time and as soon he comes up with a fix/ has time to brwose through your log files he'll post it here. He just seems to be really busy at the moment.

Thanks tomster, I apprecaite that gesture of helping nature.

As a temporary relief I am using POP3 settings for my work mails, synching calendar manually. Hopefully my N900 wll work with MfE / Exchange Server 2003 in the coming days. I will wait for Vitaly to see this message and help people like me.

To speed things up a bit I suggest you post your device's Activesync logs here. A short Howto you'll find in the MfE Heartbeat here on the wiki. Don't forget to blank-out your personal credentials like server, login and password.