Hi, I'm having problem with reconciliation with my emails.. once I delete on my BB, I have to delete it also from my Outlook XP. Mailbox & handheld selected under email reconciliation.

device: 7290 v3.6
I'm not sure what is the version of our BES (v3.x).. :(

Is there a list of bugs that has been fixed from BB desktop manager v3.6 to v4.0? and from BES 3.x to v4.0?

I'm not the only one experiencing this problem and sometimes some of the users cannot receive mails for hours.. when I checked with the admin they always ask me to reset the device.. ;(

What if an urgent email wes sent to me and I wasnt able to receive it because I forgot to reset the device?

Cxxxkies -
What device do you have?
Do you know if you guys are running Blackberry Enterprise Server or are you running POP3 with a relay to your blackberry carrier?

Hi dgman,

my device is 7290 v3.6 (most of the users) and using Enterprise server. some of us having the reconciliation problem but the admin always saying to restart the device.. wtf! kin of a solution is that.. sorry about that.. I want to return my device already.. hehehe

HOWDY!
Sounds like your admin is clueless and is not taking you seriously! Can you fire him? LOL... this would stop the pain he is causing you, LOL. Seriously, 3.6 all-in-all should be pretty seamless and stable with wireless reconciliation. So let's start with the basics...

1. Is it a MS Exchange environment or an IBM Lotus environment?
2. Is the wireless calendar functioning?
3. Has the email have ever reconciled for you?

Do you use/have a Blackberry Desktop installed on your desktop or laptop?

I don't want to jump the gun but if it’s an Exchange environment, it sounds like your admin might have two different cdo.dll’s installed and causing a conflict. The CDO.DLL on the Exchange server and the BES Server must match! This is a common admin mistake!

1. Is it a MS Exchange environment or an IBM Lotus environment? Yup
2. Is the wireless calendar functioning? When stop receiving emails the calendr also stop working.
3. Has the email have ever reconciled for you? Yup

Do you use/have a Blackberry Desktop installed on your desktop or laptop? yup.

I don't want to jump the gun but if it’s an Exchange environment, it sounds like your admin might have two different cdo.dll’s installed and causing a conflict. The CDO.DLL on the Exchange server and the BES Server must match! This is a common admin mistake!
For this one I have to check with him but of course he will tell me the file is the same hehehe..
thanks for your help..

hopefully this wil fix the problem..

To be honest, I think this was an 'A or B' question not a 'Yes or No'...

To be a bit easier of a question, do you use Microsoft Outlook or Lotus Notes?

ei sorry about that.. Im using MS Outlook..

Sorry, I'm on a hurry when I say your reply and a bit confused.. :(

I'm using MS Exchange..

Exchange 2000 e-mail
Outlook 2003 client
T-Mobile 7290 with their 4.0
DM 4.0
BES 3.6 SP4 (latest SP whatever that is)

Wireless calendar works fine
Wireless e-mail recon stopped working ; if I delete/read on the BB, it gets handled on properly on Outlook. If it gets deleted on Outlook it does not get deleted on the BB.

Wireless e-mail reconciliation appears to be set up properly on the handheld. Desktop Manager says Wireless reconciliation is set up.

Working for other people - none of whom have this particular BB with this OS. I may try to change the OS from T-Mobiles 4.0 to Cingular's 4.0.

I have a few users here with the same problem(7290 running v4.00.219). I decided to go all out - removed the user from the server and cleared all BB information from their mailbox, wiped the handheld, set them back up and Activated wirelessly.

The user's BlackBerry only syncs read/unread information and only moves an item off the handheld if it's moved to the "Deleted Items" folder in Outlook. Hide Files Messages is set to yes as is wireless reconciliation.

This is a problem that RIM needs to acknowledge and fix. I have a few users who had no problems with the wireless reconciliation in 3.6 and now 4.0 sucks for them.

BTW, I am running BES 4.0 w/ Hotfix 2 in a native Exchange 2003 SP1 environment and the CDO.DLL file versions are the same.

CDO.dll is for wireless calendar. It's the only function of the BES that uses it.

Really stupid question, but I have come across this situation (I know NJ is not in this situation) are people waiting 20 minutes before complaining that it's not reconciling? Reconciliation can take up to 20 minutes.

Does it work if you go into messages, click the thumb wheel, and select reconcile now?

When deleting items in outlook, do they go into the deleted folders, or do you do a perma delete on them? They need to be in the deleted items folder when the BES scans for reconcile changes.

If you go into the messages -> options -> reconciliation, turn off wireless reconcile, save, then go back in and turn it on, does it work after that?

I have had ONE person who had this problem, and turning wireless reconcile off on the handheld actually turned it on. But he wasn't able to do ANY wireless reconcile at all...not even read/unread.

Zro

Hi Zro, Where did you find this information? I have some people complaining that it takes up to 19 minutes for changes to be reflected on the other side.

It woud be helpfull to have a more official statement (eg RIM KB) than your post (sorry for that) to prove that this is normal. I did find an article explaining that reconciliation is done in batches etc to save on the amount of wireless data to send, but it didn't contain any actual figures.

tia

The rule of thumb used to be 20 minutes or 20 clicks/operations. I'll see if I can dig up where I read that.

I take no offense from not wanting to believe something that one person said on the internet...i am actually happy about it...too many people just take some random comment as law

Zro

Ok, have one here....but it only gives definate times for C++ devices....

KB Article about wireless reconcile

Here's one about Lotus Domino...but I think the timing is off on it....I'm going to have to check into this one and find an official word for you.

Domino wireless reconcile KB article

I'm actually wondering if that "at random intervals when the handheld is idle" could be up to 20 minute random intervals...

Zro

State Reconcile - Outlook to Handheld - BES 4.0 for Exchange

not sure if that helps, since it was BES 4.0. however, my situation turned out to be the Display Name. this did not affect our BES 3.6 server, however (i moved myself to it and reconcile worked fine).

anyhow, if you want to test this out, do the following command from a domain controller or exchange server (or if you have domain privaledges, you can do it from your own machine, although it may take a little longer):

ldifde -f filename.txt -r "(objectclass=user)"

once you have this, open it up and search for you name and check the displayName attribute. if the value appears to be encrypted, then that may be the issue. here's an example (note the value, as well as the double semi-colon):

displayName:: V2Vha2xhbmQsIE1pY2hlbGUg

and this is what the line looks like on my now changed account (obviously, I didn't use my real name ):

displayName: LastName, FirstName

Anyhow, perhaps my research can help you all out... I'm still trying to figure out the root cause of our issue, as it only affected users up to a certain point (all new accounts being created now appear correct in the LDIFDE export). I have removed our Exchange migration (using Aelita's software) from the picture and I believe I can just about pinpoint it to having to do with the ADModify tool used to implement a global change to the formatting of Display Names from 'FirstName LastName' to 'LastName, FirstName'.

Its worth checking out, atleast. Trust me, we worked on this for about 2 weeks (sometimes playing phone tag) and this was one of the last things we were going to check. If anyone has any questions, let me know... I believe I tried to document as much as possible, but I possibly left out some of mine and RIM's troubleshooting steps. The major things that tipped us off were the fact that one new user was working (the only new person on that server) and the LDIFDE export...