I'm having a MAPI issue on my BES 4.1SP6 server. We had to redo a few servers due to an SMS error and BES was one of them. Everything was going well until I installed Office 2007 for 2007 document viewing. I was expecting to be able to be able to do a custom install so that Outlook didn't load. I got called away and when I came back, Outlook was installed.

I uninstalled Office and also uninstalled the CDO 1.2.1, as we have some users on 2007 Exchange, others (including the BES service account) on 2003. I rebooted, reinstalled CDO 1.2.1 and rebooted again.

Most everything works, users can do GAL lookups etc. However there are some problems. If a user puts a calendar entry in their Blackberry, it doesn't go to Outlook. Going the other way works. Contacts do work from device to Outlook.

I'm also seeing errors launching the Blackberry Manager on the server:

Network problems are preventing connection to the Microsoft Exchange Server computer. (I can ping the Exchange server that has the BES service account.)

Then: The action could not be completed.

After that, the MAPI profile screen comes up, with the right Exchange server and mailbox, but if I click check name, it says the name cannot be resolved. I also notice that on the MAPI screen the title is Microsoft Exchange Server, but on the name cannot be resolved error, the title is Microsoft Outlook.

Clicking OK brings up the error: The name could not be resolved. The action could not be completed. I click OK and I get Failed to open the default message store using the MAPI Profile BlackberryManager. At that point the manager opens.

Sorry about the length of this post, but does anyone have any suggestions?

SMS Error?

Good move. While Outlook is supported on Exchange 2007; it isn't supported on a server with BES.

Check out this post on one-way calendar sync

Blow away your BlackBerryManager MAPI Profile ... KB10285 - How to re-create the BlackBerry Enterprise Server MAPI profile. You don't want to blow away BlackBerryServer as that is the one being used by the BES services.

__________________
http://blog.port3101.org/hdawg/

The views expressed by me on Port3101 and its affiliated sites are my own and do not necessarily reflect the views of my employer.

I've not seen this exact issue, but had some similar things pop up when updating the MAPI/CDO tools for Exchange 2007 on some of our BES. Make sure that you have the correct MAPI information in both places:
Start>Programs>BlackBerry Enterprise Server>Edit MAPI Profile
and
Start>Programs>BlackBerry Enterprise Server>BlackBerry Server Configuration, BlacKBerry Server tab, Edit MAPI Profile button.
(have seen where one is correct and the other is blank or points to wrong server and caused problems opening BB Manager).

As for the calendaring problem, my guess is that since you installed the Exchange 2007 MAPI/CDO tool but your service account mailbox is still on Exchange 2003, the CDO.dll is causing conflicts. Move your service account to an Exchange 2007 server and see if that takes care of it. (if you do move it, make sure to update the server name in both MAPI profile spots listed above).
RIM's KB on moving the account to E2K7:
KB14502 - Migrate the BlackBerry Enterprise Server from Exchange 2000/2003 to 2007

I ran into this problem at one point as well.. In my case it had to do with our Exchange 2007 implementation being full native mode. It relates to cached-mode vs. non cached-mode. You need to enable non cache-mode for the users in question. That will allow the BesAdmin account to logon to the users account using MAPI.

Huh?

That doesn't make any sense. cached/non-cached is a client side function and should have nothing with server access for another MAPI profile on another machine.

__________________
http://blog.port3101.org/hdawg/

The views expressed by me on Port3101 and its affiliated sites are my own and do not necessarily reflect the views of my employer.

From what I understand, an SMS package was created but not assigned. It somehow defaulted to everything. So it started deploying to all systems and servers. Fortunately it was caught before it touched most systems, but we still had some servers and clients go down.


Which I knew, just thought I'd be given the option to do a custom install. Next time I'll do it via CD rather than network store.




I'll check these out. Thanks!

Even though I'm just editing the mapi profile for Blackberrymanager, do I need to stop services? I tried it without stopping them and no luck. I backed up the reg key and deleted it. I went to the configuration and edit mapi profile, but it still couldn't resolve. I logged into another system and in Outlook was able to resolve it. On BES, I also tried to use the FQDN of the PO server. Still couldn't resolve.

One other thing. I remember this happened to me once before, in that case one of our domain controllers was shut down and it was trying to go to that for the global catalogue. How do I make sure the BES is pointing to the right server? I set DNS, and it's right in the dca key under MAPI. From the logs it mentions the right server for global catalogue.

On BES I can't resolve any mailbox name, not just besadmin.

No you do not need to stop the services. You're not touching the MAPI profile the BES users, but rather a different profile that you use to launch the BlackBerry Manager and have email access.

You don't want to touch this one; this is the BlackBerryServer MAPI profile. There are 2 different MAPI profiles.

Restart the BES so it picks up a fresh Global Catalog server ... check this out too: KB13157 - BlackBerry smartphone users are unable to send but can receive messages

__________________
http://blog.port3101.org/hdawg/

The views expressed by me on Port3101 and its affiliated sites are my own and do not necessarily reflect the views of my employer.

The global catalogue was put on the other AD server. Our AD manager said it wasn't recommended as that was the master, but the message said that it was OK if all others were GCs. Now the BESadmin name is resolving fine. I rebooted several times after this server didn't have a global catalogue.

Everything works now. Lesson learned: have all servers as a GC. Why everything else worked I don't know. I thought GAL lookups etc used the global catalogue as well.

from my understanding BES 5.0 in an purely native exchange account logs in to your account using its permissions. If the user account doesnt allow the MAPI protocol the that function fails. I may be way off base but that is what fixed the problem here. But then again we do everything far from the norm.

Where'd you hear that? MAPI's role / access hasn't changed from 4.x.

__________________
http://blog.port3101.org/hdawg/

The views expressed by me on Port3101 and its affiliated sites are my own and do not necessarily reflect the views of my employer.

Cause 3
The protocolSettings in Active Directory have been set to deny MAPI connections.
Resolution
Microsoft Exchange 2003 SP2 and Microsoft Exchange 2007 SP1
Complete the following steps:
1. Install the Windows 2003 Support Tools if they are not currently installed.
2. Open adsiedit.msc.
3. Expand Domain [servername.domain.com] then the respective container holding the user object that you want to check the protocolSettings of.
4. Right-click a user and select Properties on the context menu.
5. Select protocolSettings from the list of properties and click Edit.
6. If you see a value of MAPI§0§0§§§§§§ or MAPI§1§1§§§§§§ then MAPI access has been turned off for this user. Remove the value.
Note: It can take anywhere from 15 minutes to 2 hours for this change to take effect.
Note: By default the Multi-valued string is blank which means that no value is defined and MAPI access is allowed.

I will try to figure out what KB article I got that from and let you know.

Sure ... KB14075 ... but tell me one organization that disables MAPI access to a mailbox.

__________________
http://blog.port3101.org/hdawg/

The views expressed by me on Port3101 and its affiliated sites are my own and do not necessarily reflect the views of my employer.

We do! How else do you control client access to your Exchange environment.

So you give people Exchange accounts but limit who can access it via MAPI? The only time I've seen this implemented is with hosted Exchange. I've seen client versions limited, but not MAPI ever being blocked for standard users ... haven't heard an business justification for doing it.

Why do you do it? Do you let people POP / IMAP but not MAPI? or OWA only?

__________________
http://blog.port3101.org/hdawg/

The views expressed by me on Port3101 and its affiliated sites are my own and do not necessarily reflect the views of my employer.

No POP/IMAP/MAPI. Just OWA and Outlook 2007. According to MS, Outlook 2007 does not need it in order to be able to connect to Exchange. All of our clients used Cached Exchange Mode. We wanted to limit the clients to Outlook 2007 only and that is the only way we could do it.

Uhh, you definitely don't have your story right there. Outlook 2007 very much uses RPC/MAPI.

__________________
http://blog.port3101.org/hdawg/

The views expressed by me on Port3101 and its affiliated sites are my own and do not necessarily reflect the views of my employer.

I only know that overall our entire exchange was configured in Cached Mode Only. It could be that only Outlook 2007 can do that. I know non-cached mode had to be enabled for any user that was on the BES. I also know that any other client besides 2007 will not work with it. I dont know Exchange and to be honest I dont want to know it! I got the short stick and was stuck working on a new BES deployment which led me here. Typical govt decision. Throw out your perfectly good unix systems and go to windows and oh yeah, have it all done in a few months!