01-15-2008, 05:25 PM
Thumbs Must Hurt
Join Date: Jun 2007
Post Thanks: 0
Thanked 0 Times in 0 Posts
| | MAPI Call failed....
Please Login to Remove!
MAPI call failed. Error 'Network problems are preventing connection to the Microsoft Exchange Server computer.', LowLevelError 1722, Component 'Microsoft Exchange Server Information Store', Context 1300
Starting to get plenty of the above messages in my MAGT logs now and users are experiencing dropouts in mails being delivered and having troubles activating new devices.
BES is Exchange, latest version with latest service packs. Service account that the BES was originally installed under was based on a UK Exchange box whereas the BES is based in Sydney.
Went about creating the new service account on the Sydney Exchange and switched over for everything to use that. Have since applied the service packs as that service account.
Any ideas as to what could still be causing the dropouts?
The BES is running in a VM Server thats running Win2k3 SP2 32 bit, on a box thats running Win2k3 SP2 64bit.
The BES does seem to get packet loss from to the Exchange box. Running the same traces on the box the VM is running on gets no packet loss. Ping times between all boxes are sub 10ms.
Any ideas at all anyone?
Would it be worth a re-install of the BES under the new service account just to make sure that there aren't any underlaying issues from when that was swapped over?
Cheers all once again ;)