BES Errors…Shocking I Know

Quick post:

Log Name:      Application
Source:        BlackBerry Mail Store Service [ComputerName]
Date:          1/29/2011 11:42:27 PM
Event ID:      10000
Task Category: None
Level:         Error
Keywords:      Classic
User:          N/A
Computer:      bes.domain.com
Description:
MailStoreExchange::RefreshGALUsingMAPI – Error in HrFindExchangeGlobalAddressList, result=0x80004005.

Log Name:      Application
Source:        BlackBerry Mail Store Service [ComputerName]
Date:          1/29/2011 11:42:27 PM
Event ID:      20000
Task Category: None
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      bes.domain.com
Description:
[ODBCRecord::DeleteRecord] No rows found to delete.  SQL = “DELETE FROM MsAddresses WHERE MailStoreDomainId = ? AND SequenceNumber > ?”.

Log Name:      Application
Source:        BlackBerry Mail Store Service [ComputerName]
Date:          1/29/2011 11:42:27 PM
Event ID:      20000
Task Category: None
Level:         Warning
Keywords:      Classic
User:          N/A
Computer:      bes.domain.com
Description:
[ODBCRecord::DeleteRecord] DATA = “MailStoreDomainId[1] SequenceNumber[111] “.

Solution – Verify the registry setting in KB19451. If it’s correct just restart the “BlackBerry MailStore Service”.

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:

SELECT Value

FROM BESMgMT.dbo.BASTraits

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:

-Djboss.partition.name=RIM_BES_BAS_HA_53748561_SERVERNAME

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.

BES 5.0 SP2 Part 1

When trying to install service pack 2 for BES 5 I got an error that says, “The setup application cannot remove a BlackBerry Enterprise Server service because the service did not stop or the removal process failed. To restart the computer, click OK. If you click Cancel, the setup application closes and the BlackBerry Enterprise Server will not work.” Since I didn’t have much of a choice I clicked OK & rebooted the server (Thanks a lot RIM).

After the server rebooted I logged back in as BESAdmin. The service pack installation started right back up. Thankfully this time the installation proceeded as normal…or so I thought.

To be continued…