Originally Posted by fadmin
This is mostly due to miscommunication between BES and exchange. Maybe exchange was temporarily unaccessible due to any reason (network related or simple reboot). Simple bes service restart usually fixes it if failure cause was fixed.
I would have known if the exchange srv went down and would have appropriateley chalked it up to that. Support and I have been going round and round on this. I realize it's a communications problem, but where do I look to find the root cause?