Alright so here's the beef that neither I, nor Blackberry Support have been able to figure out. My company uses a BES to set up our 130 or so users that have blackberries up and get them emailing and all that jazz. After a recent restart to our Global Catalog server, all email functionality on the phones and the BES has stopped. I have tried to use MFCMapi to open a profile but I don't even get an error it just locks up immediately after using the program. I've pinged both our Exchange Server and our Catalog server, as well as made sure that tracert and all other variables to test were successful and they were. I've reinstalled the MAPI 1.2.1 on the server and still to no avail and have tried restarting the BES, the Global Catalog server, and our Exchange server with no results. At the moment I have a mirror set up until the original BES is fixed but this has happened to one of our previous servers before for much the same reason and we were never able to resolve the issue. I have a BES set up on VMWare, currently running the 64-bit Windows 2008 Server OS. Our Exchange server is running 2003 and the BES is 5.0.2. Blackberry Support insisted this problem was out of their expertise and suggested I try to get help from Microsoft so here I am and I do certainly need help. If history repeats itself, it's only a matter of time before we have to reset our GC server and the other server has problems with email as well and hopping from one server to the next isn't exactly an ideal way to fix the problem. If anyone has any ideas at all or if you need more info that I haven't provided I'd be glad to give it. Thanks

Have you checked the application and system logs on the Exchange server for errors? Have you checked the DC's for replication or directory service errors? Try running the Exchange Best Practices Analyzer against the Exchange server. For 03 its a free download from MSFT. Let us know what you find.Chris Morgan

To answer the first two questions, yes I have and unfortunately, nothing in them really points to a problem connecting to the BES or anything like that. As for the Analyzer, I just used it and the error I got when scanning health was this, "The Exchange schema extensions are from an unknown version. Schema version detected is 14622" Not sure how relevant that might be but that was the only one it picked up when I ran the scan. Also, a detail I forgot to mention, whenever I use Edit MAPI on the BES server config application, I am able to find my exchange server (only by typing the name of the GC though oddly enough) and it underlines the name of both the server and the name being used for the email. The only difference aside from having to type the GC server as opposed to the Exchange server's name is that it doesn't put as exchangeserver.domain.com but only puts the ES's name. Not sure if that helps but in the mean time I'm working to find any other relevant information and trying to fix it myself as well. Thanks for the input.

Did you check all the tabs in the report? That schema thing is usually something you can ignore but I would click on the link for tell me more about it to verify you have the right schema version for your Exchange version.Chris Morgan

Well apparently anything above 10637 means I have Exchange 2007 installed somewhere and granted I'd love to fix it with the rather easy solution it gives, very weary of doing so since we only have one Exchange server and if that went down after said fix we'd have some trouble here. That aside, is it possible that because Exchange 2007 was somehow installed on our 2003 Exchange server that it's messing up with the BES' exchangemapicdo or something? Thanks

Anything is possible. :-) Doubtful it's causing the issue. Someone could have just extended the schema but not installed it. You can look in adsiedit to to see if there is an 07 server in there. Careful if you are in there as you can cause serious damage by making changes in there if they are done wrong. Try running DCdiag /s:<DomainControllerName> from the Exchange server and see if you get any errors. If dcdiag isnt on the box you can download the support tools to get it.Chris Morgan