Monday, February 23, 2009

Failed to retrieve the Server DN, shutting down



Problem:

We start receiving fallowing message on the BES servers and "Failed to retrieve the Server DN, shutting down"

Cause:

The BB service account is corrupted with un-known reason ( we are un-able to find the cause)

Event Type: Error

Event Source: BlackBerry Messaging Agent SMTP25WINBES01 Agent 200

Event Category: None

Event ID: 10275

Date: 2/23/2009

Time: 10:42:48 AM

User: N/A

Computer: SMTP25WINBES01

Description:

Failed to retrieve the Server DN, shutting down


Event Type: Warning

Event Source: BlackBerry Controller

Event Category: None

Event ID: 20406

Date: 2/23/2009

Time: 10:00:35 AM

User: N/A

Computer: SMTP25WINBES01

Description:

'SMTP25WINBES01' agent 1: will not restart - reached the maximum of 10 restarts per 24 hours


Solution:

This is one of the weird error and researching the cause did not much help to us. So we went ahead and basically performed fallowing steps

  1. Re-start the BES services ( Problems exist)

    If you remember this needs to be done in order, others fallows as you wish in any order.

  • R ( Router)
  • D (Dispatcher)
  • C (Controller)
  1. Reboot the BES server ( problem exist)
  2. Check BES account verified it is not locked
  3. Check server DNS setting TCP/IP made sure DNS IP addresses have not been changed
  4. WINS configured ( if there is one)
  5. Flushed TCP/IP configuration, Un-Registered and registered WINS server
  6. Open BES logs continue to look for errors
  7. Re-start BES services in order
  8. Re-configure the BES profile on the BES server ( Problem persist)
  9. Finally we create new BES service account , configure profile and give proper permission on the exchange 2007 server, made all worked out.

PS:

Granting BB Permissions Exc07

Change the domain SMTP25 to your own domain

Use the BB Service account you have

  • Domain: SMTP25
  • BB Service account name: svc-besadmin

Get-MailboxServer Add-ADPermission -User SMTP25\svc-besadmin -AccessRights GenericRead,

GenericWrite -ExtendedRights Send-As, Receive-As, ms-Exch-Store-Admin


Oz Ozugurlu
MVP (Exchange)
MCITP (EMA), MCITP (SA)
MCSE 2003, M+, S+, MCDST
Security+, Project +, Server +
Blog: http://www.smtp25.blogspot.com

1 comment:

Anonymous said...

For me, the error had to do with the besadmin mailbox missing the 'HomeMTA' attribute. I took the homeMTA from another mailbox on the same Exchange server and applied that to the besadmin account and that fixed the problem.