[liamdye]

So I had a working BES/Exchange setup, then after a few reboots the BES does not work anymore. I test the MAPI profile and here is the message I get:

---------------------------
Microsoft Outlook
---------------------------
The name could not be resolved. Network problems are preventing connection to the Microsoft Exchange Server computer. Contact your system administrator if this condition persists.
---------------------------
OK
---------------------------

Details:
BES Express 5
Exchange 2010
Server 2008 R2 x64 on both machines
Can ping my Exchange Server
DNS resolves
OWA works logging into BESAdmin
BESAdmin account details haven't changed

I just don't understand what happened. One thing that it could be is I set the permissions of all the BES Services to login as BESAdmin. (BESAdmin has local admin and log on as a service rights).

[knottyrope]

Did you reboot BES or exchange?

Reboot BES if you rebooted exchange.

[liamdye]

I have rebooted both many times. Currently I am updating Java on BES, and updating BES to 5.0.2MR1 and updating Windows. I also attempted to reinstall CDO 1.2.1.

[knottyrope]

you are going way to fast, need to get to the cause instead of upgrading everything like crazy

Java been updated? Dont update it, it is not needed but check the following

KB14697-Could not load the Java Virtual Machine. Load Library the specified module could not be found

Also modify this key, it seems to get the wrong value during an upgrade for some.

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Servic es\BAS-AS\Parameters\JVM Option Number 3

-Xmx1024m
by
-Xmx768m

[knottyrope]

What errors in MAGT BES logs do you have when you reboot BES?

[liamdye]

Hello,

So I did the registry change for the Java which you instructed (unfortunately everything had already been updated).

Regarding BES MAGT logs, there does not look to be any errors.

By the way, is it fine that all BES services are running as "DOMAIN\besadmin"? Or should they be something different?

[nobody7290]

have you decided to hide the besadmin user from the GAL ? This is not recommended.

[invisibl]

Originally Posted by nobody7290

have you decided to hide the besadmin user from the GAL ? This is not recommended.

Hi there

Not wanting to Hijack this thread
Can you explain this: I have been searching this point this morning and it seems to be a 50/50 opinion fest
Would be wondeful to have this cleared up from a KB article or similar

Many thank
s

[liamdye]

Originally Posted by nobody7290

have you decided to hide the besadmin user from the GAL ? This is not recommended.

Nope, haven't hid the besadmin user from the GAL. It worked perfectly fine before a few reboots, didn't change anything in the organization. Also, I can't resolve the Exchange address if I use another user (ie Administrator) either.

[nobody7290]

If you go to a some workstation, login as besadmin,
and, setup a new outlook profile for this user,
does autodiscover work, and will display the same server as you see in the mapi profile of the besadmin on the BES server ?

[liamdye]

So I went onto a workstation, and tried to configure BESAdmin in Outlook using my correct server settings and it didn't work! Got the same error as one the BES. Now, I don't use autodiscover because I never bothered to set that up correctly, but I have my account working fine on Outlook on my machine, so I don't know why the BESAdmin wouldn't work.

[liamdye]

Now some more error messages:

---------------------------
BESProfile
---------------------------
The (BlackBerryServer) profile is invalid due to missing or invalid property tags.
Ensure the specified profile information is valid and unique.
---------------------------
OK
---------------------------

and

---------------------------
BlackBerry Server Configuration
---------------------------
The MAPI subsystem cannot be correctly initialized and used. Please make sure MAPI is installed and configured properly.
---------------------------
OK
---------------------------

[nobody7290]

Accessing the besadmin mailbox from OWA - does that work ?
The besadmin must have a mailbox, as any other user, and outlook web-access should be set to enabled.

[liamdye]

Yes, I can log in through OWA.

[Kul]

is the besadmin account permissioned correctly ?,is the AD account disabled ? you should be able to resolve the besadmin account fine - its just as mentioned earlier, a simple mailbox account

[nobody7290]

Dont know if that helps, but, have you tried to restart all exchange services/restart the server exchange is running on ?

Have you checked in the Exchange management console, that mapi access is enabled for the besadmin user ?

[RadHaz75]

follow these instructions on updating mapi and cdo, specifically the part about recreating the mapi profile...

KB15779-How to install or upgrade the Microsoft Exchange Server MAPI Client and Collaboration Data Objects 1.2.1

also, are you sure the besadmin mailbox wasn't deleted or moved? pretty interesting that you can't access it in outlook either...