Heres the scenario:

I have a client that has about 200 users on their bes 4.0 exchange 2003 sp1 is the backend, they are patched up to sp3 hf3. I seem to have 2 scenarios:

1) Any changes/deletes made to an appointment in outlook does not reflect on the bb 100% of the time.

2) Any changes/deletes made to an appointment in outlook does not reflect on the bb about 20% of the time.

All additions work fine and any changes made on the bb get reflected into outlook. The cdo.dll and mapi32.dll are the same versions. The settings are all correct, and this is only affecting a few users.. possibly about 10 out of 200. BUT these users are all directors/decision makers who would decide if they will get another 500-1000 bb's so while it doesnt affect alot of users it affects the right ones.

Any insight would be appreciated as to what I should look for on the BES. I will be trying to call into the helpdesk in the next few days but trying to schedule everyone for a conference call is a *****. Thanks in advance.

What does the logs say for the users with problems?

Regards,
Bob

Hey MobileRC,

When did you first notice this happening? We're running the same setup with Outlook 2K clients and are seeing something similar with contact records. We weren't following things that closely, but went from SP2 to SP3 and the three hotfixes and that's when we first noticed the issue.

Trying to sync 10 test records and only a subset come over to the device. I've looked at the sync logs and am seeing a message that indicates the updated records have already been deleted, so it appears that BES is not sending the data, even though the records haven't been deleted. You may want to look for something similar in your logs.

I've spent about 5 hours with tech support and so far the only thing we've figured out is that a wired sync works. If you find out why this is happening with your appointments please post back to this thread and I'll do the same if I get a definitive answer with my contacts. Maybe things are failing the same with both types of records.

Ciao

I will get into the logs and see what it says