Originally Posted by Kathryn

Please excuse me if this has been posted before. Did a search and could not find an answer.

Here goes: 1st time installation of BES, running exch 2k3 sp2, msde2000 and have the besadmin account setup with the appropriate permissions as requested. When attempting to run the BES installation and we get to the point where we need to test the mapi, it appears that the mapi is unable to talk to the exchange server and therefore giving us a "name cannot be resolved".

Has anyone encountered this issue and can offer some possible solutions?

Originally Posted by bertiebassett

have you tried pinging the exchange server from the BES server and checking that your DNS is working correctly.

Did you install the BES using the besadmin account rather that general admin?

Oh and for BESadmin questions post in the besadmin forum - much quicker response with better SNR ration to general

Originally Posted by Kathryn

Thanks Bertie for the response, will go check out the BESAdmin section. Yes, did the usual ping, dns settings and yes, installed with BESAdmin account.

We think we know what the problem is and in the process of rebuilding the server AGAIN. When we first built the server, we loaded o/s with slipstream SP2. We managed to get BES to work on a VMachine that had SP1 & SP2 layered on top of each other and think that even though SP2 Slipstream is suppose to be full, that there are some .dll files that are missing and that is causing the problem. We should know for sure by Tuesday when we get back from Easter Break. I'll respond back with the solution.

Cheers K

Originally Posted by gibson_hg

Is the BESAdmin mailbox hidden? The name won't resolve if it's hidden. Can you resolve any other mailbox from the server? If not then there is an issue either with DNS or MAPI on this machine.