Sync problem Blackjack - WM6 and OCS

[cknight1001]

I'm using SYNCML 3.0.2.15 with Blackjack I and Oracle Collaboration Suite. Contacts and Tasks are working fine. I consistently get an error on events however.

The log is as follows:

- Slow Sync for Events
- Successfully Completed
- Device: +7, =7, -5 items
- Server: +0, =12, -0 items
- Failed: dev:2, srv:0
- Rec 169411 / Sent 57130 bytes

There are two calendar entries for the same day that do not load to the device. This happens consistently.

I guess since the problem is because of the Failed: dev but I don't know what that means or how to troubleshoot.

Thanks for any help. We are evaluating this product for use at our university.

[cknight1001]

More information:

It appears that the calendar events that are causing the device failure are those which have been scheduled within OCS using a facility resource. Those events that are not using a facility resource seem to sync ok.

[luz]

There are two calendar entries for the same day that do not load to the device. This happens consistently.

Is there anything special with those two events? Like a huge description, exotic recurrence, attendees with invalid email adresses?

The windows mobile calendar sometimes refuses to store events if it thinks they are malformed. We try to implement our software as fault tolerant as possible, but can't completely avoid that some entries are rejected.

I guess since the problem is because of the Failed: dev(ice)

Yes, this line shows the number of items that failed to be stored in the device. Unfortunately, the Win Mobile OS does not give any reason why it can't store, so the only way to find out is to look at the data and guess what might be special compared to those events that sync ok.

[cknight1001]

The facility resources do have invalid email addresses associated with them such as 00398.00001@email.invalid.

Does it do some type of check on the email address?

[luz]

We found a small problem related to WM6 which made storing events fail when there was a invalid email address for an attendee. This is now fixed in 3.0.2.16 and later versions of the software.