[buu511]

Found another problem with the microsoft exchange account sync. All birthdates are exactly 1 day too early on the Q10 .My laptop and iPhone are also connected to the exchange server and display the birhtdates correctly.

Can anyone confirm this behavior?

[robsteve]

Do you have Facebook setup as well. I haven't looked lately, but The birthdays fed by FaceBook were off by a day, actually showing the day it is going to notify you. In other words if notification is set to notify you the day before the birthday, the notification date is shown, not the birthday.


Posted via CB10

[buu511]

The facebook birthdays have the correct date for me.

Sent from my Q10

[just_luc]

If you go to Facebook in the accounts menu, there is a drop down for birthdays, and the defaults is one day BEFORE at 9am. You can change it to the day of. There's no such option for exchange though.. can't explain that one. If you check the reminder it's colour coded to the exchange calendar? Its not maybe someone you happen to have in your exchange address book AND Facebook, and the notification is coming from facebook?

Posted via CB10

[buu511]

I turned off fb contacts completely to test this. And just displayed my normal exchange contacts without any fb link. All birthdays are one day off.

All fb contact birthdays show the correct dates.

Sent from my Q10

[just_luc]

I turned off fb contacts completely to test this. And just displayed my normal exchange contacts without any fb link. All birthdays are one day off.

All fb contact birthdays show the correct dates.

Sent from my Q10

Hrmmm.. can't explain that. have you talked to anyone else who's using the same exchange server? Maybe it's a server side setting...

Posted via CB10

[buu511]

If it was server side my iPhone, iPad, MacAir and Windows PC would also be affected. But all exchange contact birthdays show correctly there. Only the Q10 is 1 day off.

[buu511]

I did another test with iclouds carddav. Those work fine on the BlackBerry and all birthdays are correct. So it seems to be an exchange only problem.

Sent from my Q10

[buu511]

Further investigation shows that this issue has been around for a long time on a lot of different platforms.

This post from early 2012 shows that the problem existed in iOS at that time too.

I just want to inform you that Microsoft identified the reason for shifted birthdays using Exchange Active Sync. According to Microsoft the mentioned problem is not caused by a server-related problem, but due to an error in a Microsoft sample code which was used in Windows Mobile 6.5, Windows Phone 7, Hotmail Outlook Connector and even in iOS. That means that the client side connection was developed incorrectly. Microsoft and Apple copied the incorrect code from time to time using the mentioned Exchange code in their software (iOS, etc).

However, Microsoft already fixed the birthday bug within the latest update of the Outlook Hotmail Connector (please check changelog) as well as in the current update of Windows Phone 7.5 (Mango).

So the conclusion is that BB still has the bugged code implemented which results in the birthday shift. Guess I will have to wait for BB to fix this.

[ppeters914]

Any way to confirm there's an existing bug report so BBRY knows to fix it?

[buu511]

I don't know. I posted the issue on their support twitter and their support forum. Let's see if that helps.

Sent from my Q10

[buu511]

The twitter support told me to contact my provider which I didn't even buy the phone of. In the BlackBerry support forum my post got ignored. This bug is really annoying. I can't believe I am the only one noticing it? It should affect all exchange users.

Sent from my Q10

[Bruno Santa]

Hi, I am experiencing the same problem with all BlackBerry Z10 we have here, this has been the first post I find on the internet about this issue. the users are really annoyed with that. Please someone post ideas or a KB that will enlight us.

[buu511]

I don't understand why so few people complain about this. As far as I understand this bug it should be an issue for all exchange accounts. Maybe people haven't noticed yet.

Sent from my Q10

[buu511]

This still is not fixed in the latest leak ..

[akavbb]

It has something to do with time zones.
Mine was off by a day but the reminders were set on the correct day but at 00:00. Probably they set time to Pacific or something similar and now it will stay there. I fixed it manually. Never reappeared since.

Posted via CB10 | STL100-2 | Waiting for the mighty Squircle to return.

[buu511]

We'll I don't know how to fix this really.

Sent from my Q10

[woodywoodford]

Hah, this got me busted wishing a friend haappy birthday one day too soon. Embarassing.

Posted via CB10

[buu511]

Can't believe so few people care about this issue. It is hugely annoying and would be easy to fix... .I tried contactic BB support as well ..... dead end.

[buu511]

Bump in the hope that someone can help me....

Sent from my Q10

[Taurec]

We also see this on a Z30 with 10.2.1.x... that is odd!

[cvdburgh]

We also see this on a Z30 with 10.2.1.x... that is odd!

Same here. Z30, 10.2.1.2102 / 10.2.1.2141 connected to Exchange (Office 365).
Other way around works as well: I just added my mother's birthday to the contact on my phone and now it shows as one day later in Outlook on my PC!

[buu511]

Finally someone else acknowledging this bug. It's been driving me mad for almost a year now. Wish there was a way to let BlackBerry know about this.

Sent from my Q10

[niss63]

I haven't checked them all, but I have seen this problem, time to time. Right now I have at least one contact that has the incorrect birthday in contacts, but is one day off in BBM. The bad news is that I can't edit the date in BBM.

Posted via CB10

[freakinvibe]

We have exactly the same problem here:

Timezone Outlook: Berlin (+1)
Timezone Q10: Berlin (+1)
OS Q10: 10.2.1
Exchange 2010 via ActiveSync

Contact Birthday date is one day off on Q10. Example: Outlook: 2-Jan-1960 (correct), Q10: 1-Jan-1960 (wrong, one day off).

We have this problem since the Q10 exists (10.0). Blackberry never addressed this.