| | working now
And the good news is it is working now. This afternoon I accidentally rebooted my exchange server and noticed some different items in the logs on the BES server after exchange came back up. I tried to re-activate again and it came booming in! So - what I have determined is that after exchange permissions have been set for BESADMIN, the exchange server requires a reboot.