Home > Computers > BES 5.0 SP2 Part 2

BES 5.0 SP2 Part 2

So part 2 of my BlackBerry Enterprise Server 5.0 Service Pack 2 adventure…

After installing BES 5.0 SP2 I was not able to get to the BlackBerry Administrative Service (BAS) website. Looking in the Event Log I had several errors that said, “Event ID: 7031. Source: Service Control Manager. Description: The BlackBerry Administration Service – Application Server service terminated unexpectedly. It has done this 1 time(s). The following corrective action will be taken in 60000 milliseconds: Restart the service.” I fired up Process Explorer & sure enough the BAS-AS.exe process would end after a minute or two then start back up.

Looking at the logs in C:\Program Files\Research In Motion\BlackBerry Enterprise Server\Logs\<DATE> I saw several log files for the BAS-AS service. One for each time that the service terminated then started back up. I opened the last one & started by searching for the string [warn]. There will always be some entries that will look something like:

[org.hibernate.impl.SessionFactoryObjectFactory] [WARN] InitialContext did not implement EventContext

However there was one strange one followed by what looks like a Java dump log:

[com.rim.bes.bas.util.EJBUtilities] [WARN] [BBAS-2041] {unknown} registerClusterMembershipListener Failed to register cluster membership listener, javax.naming.NameNotFoundException: null not bound

Searching around for that error pointed to KB22249 article on RIM’s site. Problem is it’s not there anymore (Thanks again RIM). Luckily I ran across several other sites that summarized the fix. Using those sites I did the following.

  • Open SQL Server Management Studio Express.
  • Expand Databases & select BESMgmt.
  • Click New Query & run the following query:



WHERE TraitId =35 AND PluginId = 0

  • Copy the value. It will be something like RIM_BES_BAS_HA_53748561_SERVERNAME.
  • Open regedit & browse to HKLM\SYSTEM\CurrentControlSet\Servic es\BAS-AS\Parameters. Notice that the value JVM Option Number 8 is blank.
  • Modify the JVM Option Number 8 value as follows:


Note– Don’t forget to change SERVERNAME to the name of your BES server.

  • Close the registry.
  • Start the BAS-AS service.

I watched the process for a few minutes until the usage calmed down. Launched the browser to bring up BAS & it came right up. After that everything looked OK.

  1. July 22, 2011 at 4:42 pm

    Hello Patrick!

    Man, this BES 5.0 is some annoying stuff 😦

    I am running into a problem, pretty closer to yours, but not exactly the same, since I’ve verified and the registry that you mention still exists.

    On BAS-AS err.log I find the following message:
    [Fatal Error] service-port-bindings.xml:52:31: Element type “binding” must be followed by either attribute specifications, “>” or “/>”.

    On the service logs, I can find this:
    (07/22 19:18:07:053):{main} [com.rim.bes.bas.authenticationmanager.AuthenticationManagerUtilities] [FATAL] [BBAS-4013] {unknown} getAuthenticationManagerLocal caught exception while getting manager – something seriously wrong with the JNDI lookup, com.rim.bes.bas.util.BASCouldNotCompleteRequestRollbackException: getRemoteServerObject could not do JNDI lookup on ‘ejb/bas/authenticationmanager/AuthenticationManagerLocal’ javax.naming.CommunicationException: Could not obtain connection to any of these urls: SERVERNAME.INTERNAL.DOMAIN:11099 and discovery failed with error: javax.naming.CommunicationException: Receive timed out [Root exception is java.net.SocketTimeoutException: Receive timed out] [Root exception is javax.naming.CommunicationException: Failed to connect to server SERVERNAME.INTERNAL.DOMAIN:11099 [Root exception is javax.naming.ServiceUnavailableException: Failed to connect to server SERVERNAME.INTERNAL.DOMAIN:11099 [Root exception is java.net.ConnectException: Connection refused: connect]]]

    Any chance on this errors have happened to you before?

    I would be very thankfull if you could help me or guide me to some way…

    Obs: Yes, I have spent many hours on looking at logs, querying BES database and running procmon… But not find anything…


  2. Carsten
    May 23, 2013 at 2:00 am

    Hi Patrick,
    many thanks for your helpful post, it was very helpfull fo me. It shows me the right way, to solve my start / stop the problem generated by the BB Administration Service EventID 7031 . Thank you very much.

  1. No trackbacks yet.

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s

%d bloggers like this: