Improve company productivity with a Business Account.Sign Up

  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 1298
  • Last Modified:

BES problem after changing domain controller on Exchange 2010

Hello, I've been having problems with my BES server (5.03) since I changed the Domain Controller on the exchange EMC.

I changed the selection from Use default Domain Controller to Specifty a Domain Controller and since then the BlackBerry devices activated in the BES can't connect to the server.

Could this change in domain controller be the cause of the BES not working?

If so, any possible fix for this problem?

Thanks in advance for your time.
1 Solution
Simon Butler (Sembee)ConsultantCommented:
Why did you specify the domain controller? That isn't a recommended solution.
However it shouldn't affect the BES operation. Did you restart the BES services after making the change?

ScreenFoxAuthor Commented:
Yeah, I did and it still not working. I changed because I didn't know what was the "Default Domain Controller" and I wanted to be sure that it was not a specific DC that will be demoted  soon.

I changed back to use default DC but still nothing.
Haresh NikumbhSr. Tech leadCommented:
Have you rebooted BSE server after making changes in Domain controller?
Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

ScreenFoxAuthor Commented:
Yes I did.
Manpreet SIngh KhatraSolutions Architect, Project LeadCommented:
Firstly why are you making Exchange look to a specific DC ?
Hope no issue between the BES server and this DC ?

- Rancy
Simon Butler (Sembee)ConsultantCommented:
Recreate the BES profile to begin with.

ScreenFoxAuthor Commented:
Firstly why are you making Exchange look to a specific DC ?
Hope no issue between the BES server and this DC ?

Because I wanted to make sure that Exchange was not using a DC that will be demoted soon.

Recreate the BES profile to begin with.

I recreated the BES profile, but its still not working.

I exceuted IEMSTest.exe and this is the result:

BlackBerry Enterprise Server Utility - IEMSTest.exe (IExchangeManageStore), Vers
ion 1.0
Copyright (c) Research In Motion, Ltd. 1999. All rights reserved.
Opening Default Message Store Mailbox - BESAdmin

BESAdmin: Opening message store using
        /o=ExchangeEurosigma/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/
        /o=ExchangeEurosigma/ou=Exchange Administrative Group (FYDIBOHF23SPDLT)/
cn=Configuration/cn=Servers/cn=MEXHUB/cn=Microsoft Private MDB
BESAdmin: Mailbox opened successfully
BESAdmin: Root Folder opened successfully
BESAdmin: Folder created successfully
BESAdmin: Test folder deleted successfully
BESAdmin: MAPI test completed successfully
BESAdmin: CDO Server Name: MEXHUB
BESAdmin: CDO Mailbox DN: /o=ExchangeEurosigma/ou=Exchange Administrative Group
BESAdmin: CDO logon successful
BESAdmin: CDO COM exception: Code = 80040705, WCode = 0505, Code meaning = IDisp
atch error #1285
    Description = El servidor de Microsoft Exchange no estß disponible. Puede qu
e haya problemas de red o que el servidor de Microsoft Exchange estÚ fuera de se
rvicio por mantenimiento. [AlmacÚn de informaci¾n de Microsoft Exchange Server -
BESAdmin: CDO test failed
BESAdmin: No Send As permission for the {SIGMARED\BESAdmin} account operator.
BESAdmin: Initializing EWS Proxy... successful
BESAdmin: Configuring User... successful
BESAdmin: EWS calendar find request... failed

Open in new window

ScreenFoxAuthor Commented:
Found the problem, I had to change the homeMTA setting of the BESAdmin user on ADSIedit.
ScreenFoxAuthor Commented:
Found the problem myself.
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

Join & Write a Comment

Featured Post

Free Tool: Site Down Detector

Helpful to verify reports of your own downtime, or to double check a downed website you are trying to access.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now