[aelorah]

I installed a fresh copy of DM 6 and when I go to setup the organizer sync, the memo, tasks, and calendar setup without incident.........all are being synced to MS Outlook

Seems as though the Address Book sync continues to say (not installed) even after setting it up numerous times.

My first inclination was that it may be my laptop at work, but after installing DM 6 on my home computer and having the same thing happen I'm guessing its something on my phone?

Can anyone help me with this............. running the latest BB Tour OS, build 983 i think

[trucky]

It's possible you have your Address Book set to: Wireless Sync=On in your Options. That would keep DM from being able to sync it.

[aelorah]

When I go into my contacts and then options, the "wireless synchronization" dialog box does not give me any options............it only says "not available"

[trucky]

Well, scratch that one. I was just trying to eliminate a gotcha that got me once. I'm not sure what's going on then. Did you install your DM direct from RIM?

[ColoradoCrack]

I have the same issue.

[trucky]

Others have had success by rolling back to a previous version of DM. Not an elegant solution, but it may get up and running again.

[hmbixler]

Same problem as the above. gmail syncs wirelessly. I do not like this setup but I see no other choice.

[MobileMadness002]

Your not going to like hearing this. Have it happened to me after software update.

Backup your device completely
security wipe
reset sync options
reconfigure sync for 1 way from outlook to device
sync
reset configuration for 2 way sync

To Test, add a test contact or cal entry on the device and add 1 in Outlook. Named according to the source.
Sync again to make sure both entries go in the other respective application
delete the original from device and outlook
Sync again to make sure updates are going in both directions

Let me know if that works.

A long process I know, but darn thankful I spoke with em for my issue.

I should also mention that BlackBerry, RIM, would be very interested in gathering device logs before you do any work rounds to try and figure out exactly what is the "root cause" of the issue being experienced.

As you can see, you are not alone in this.