Besx 5.0.4 Sbs11
 

Hi All,
I have a client using BESX 5.0.4 and SBS 2011 and have been for a while.
Last week the users reported that their Blackberry's stopped receiving email. Rebooted. No joy. A colleague re-ran the installer over the top and they all started working again. I am assuming it picked up the existing database as we didn't need to reactivate.

However, I can't login into the web console. It just says page not displayed. I installed Google Chrome to make sure it wasn't just IE.

I have done some digging and the Java path in the registry is correct. The devices can send and receive email without an issue.

Does anyone have any ideas?!
Kind regards,

Re: Besx 5.0.4 Sbs11
 

look in the BAS AS logs for any errors and post them

Re: Besx 5.0.4 Sbs11
 

Hi KnottyRope!

I found the log SBS_BBAS-AS_20140828_0001 - am assuming this is the one?

It is full of the below:
(08/28 14:59:13:792):{Thread-5} [com.arjuna.ats.jta.logging.loggerI18N] [WARN] [com.arjuna.ats.internal.jta.recovery.xarecovery1] Local XARecoveryModule.xaRecovery got XA exception javax.transaction.xa.XAException: Error trying to connect to provider java:/ClusterJMSProvider, XAException.XAER_RMERR
(08/28 15:01:23:857):{Thread-5} [com.arjuna.ats.jta.logging.loggerI18N] [WARN] [com.arjuna.ats.internal.jta.recovery.xarecovery1] Local XARecoveryModule.xaRecovery got XA exception javax.transaction.xa.XAException: Error trying to connect to provider java:/ClusterJMSProvider, XAException.XAER_RMERR
(08/28 15:03:33:922):{Thread-5} [com.arjuna.ats.jta.logging.loggerI18N] [WARN] [com.arjuna.ats.internal.jta.recovery.xarecovery1] Local XARecoveryModule.xaRecovery got XA exception javax.transaction.xa.XAException: Error trying to connect to provider java:/ClusterJMSProvider, XAException.XAER_RMERR
(08/28 15:05:43:864):{Thread-5} [com.arjuna.ats.jta.logging.loggerI18N] [WARN] [com.arjuna.ats.internal.jta.recovery.xarecovery1] Local XARecoveryModule.xaRecovery got XA exception javax.transaction.xa.XAException: Error trying to connect to provider java:/ClusterJMSProvider, XAException.XAER_RMERR
(08/28 15:07:53:922):{Thread-5} [com.arjuna.ats.jta.logging.loggerI18N] [WARN] [com.arjuna.ats.internal.jta.recovery.xarecovery1] Local XARecoveryModule.xaRecovery got XA exception javax.transaction.xa.XAException: Error trying to connect to provider java:/ClusterJMSProvider, XAException.XAER_RMERR
(08/28 15:08:24:897):{Thread-17} [com.rim.bes.bas.baa.corews.CoreHealthCheck] [INFO] [BAA-1000] {unknown} BAA HealthCheck
(08/28 15:08:32:887):{Thread-18} [com.rim.bes.bas.bws.BWSHealthCheck] [INFO] [BWS-1000] {unknown} BWS BWSHealthCheck
(08/28 15:10:03:988):{Thread-5} [com.arjuna.ats.jta.logging.loggerI18N] [WARN] [com.arjuna.ats.internal.jta.recovery.xarecovery1] Local XARecoveryModule.xaRecovery got XA exception javax.transaction.xa.XAException: Error trying to connect to provider java:/ClusterJMSProvider, XAException.XAER_RMERR
(08/28 15:12:14:056):{Thread-5} [com.arjuna.ats.jta.logging.loggerI18N] [WARN] [com.arjuna.ats.internal.jta.recovery.xarecovery1] Local XARecoveryModule.xaRecovery got XA exception javax.transaction.xa.XAException: Error trying to connect to provider java:/ClusterJMSProvider, XAException.XAER_RMERR
(08/28 15:14:24:123):{Thread-5} [com.arjuna.ats.jta.logging.loggerI18N] [WARN] [com.arjuna.ats.internal.jta.recovery.xarecovery1] Local XARecoveryModule.xaRecovery got XA exception javax.transaction.xa.XAException: Error trying to connect to provider java:/ClusterJMSProvider, XAException.XAER_RMERR
(08/28 15:16:34:175):{Thread-5} [com.arjuna.ats.jta.logging.loggerI18N] [WARN] [com.arjuna.ats.internal.jta.recovery.xarecovery1] Local XARecoveryModule.xaRecovery got XA exception javax.transaction.xa.XAException: Error trying to connect to provider java:/ClusterJMSProvider, XAException.XAER_RMERR
(08/28 15:18:24:863):{Thread-17} [com.rim.bes.bas.baa.corews.CoreHealthCheck] [INFO] [BAA-1000] {unknown} BAA HealthCheck
(08/28 15:18:32:853):{Thread-18} [com.rim.bes.bas.bws.BWSHealthCheck] [INFO] [BWS-1000] {unknown} BWS BWSHealthCheck
(08/28 15:18:44:226):{Thread-5} [com.arjuna.ats.jta.logging.loggerI18N] [WARN] [com.arjuna.ats.internal.jta.recovery.xarecovery1] Local XARecoveryModule.xaRecovery got XA exception javax.transaction.xa.XAException: Error trying to connect to provider java:/ClusterJMSProvider, XAException.XAER_RMERR
(08/28 15:20:54:278):{Thread-5} [com.arjuna.ats.jta.logging.loggerI18N] [WARN] [com.arjuna.ats.internal.jta.recovery.xarecovery1] Local XARecoveryModule.xaRecovery got XA exception javax.transaction.xa.XAException: Error trying to connect to provider java:/ClusterJMSProvider, XAException.XAER_RMERR
(08/28 15:23:04:329):{Thread-5} [com.arjuna.ats.jta.logging.loggerI18N] [WARN] [com.arjuna.ats.internal.jta.recovery.xarecovery1] Local XARecoveryModule.xaRecovery got XA exception javax.transaction.xa.XAException: Error trying to connect to provider java:/ClusterJMSProvider, XAException.XAER_RMERR
(08/28 15:25:14:381):{Thread-5} [com.arjuna.ats.jta.logging.loggerI18N] [WARN] [com.arjuna.ats.internal.jta.recovery.xarecovery1] Local XARecoveryModule.xaRecovery got XA exception javax.transaction.xa.XAException: Error trying to connect to provider java:/ClusterJMSProvider, XAException.XAER_RMERR
(08/28 15:27:24:432):{Thread-5} [com.arjuna.ats.jta.logging.loggerI18N] [WARN] [com.arjuna.ats.internal.jta.recovery.xarecovery1] Local XARecoveryModule.xaRecovery got XA exception javax.transaction.xa.XAException: Error trying to connect to provider java:/ClusterJMSProvider, XAException.XAER_RMERR
(08/28 15:28:24:829):{Thread-17} [com.rim.bes.bas.baa.corews.CoreHealthCheck] [INFO] [BAA-1000] {unknown} BAA HealthCheck
(08/28 15:28:32:819):{Thread-18} [com.rim.bes.bas.bws.BWSHealthCheck] [INFO] [BWS-1000] {unknown} BWS BWSHealthCheck
(08/28 15:29:34:483):{Thread-5} [com.arjuna.ats.jta.logging.loggerI18N] [WARN] [com.arjuna.ats.internal.jta.recovery.xarecovery1] Local XARecoveryModule.xaRecovery got XA exception javax.transaction.xa.XAException: Error trying to connect to provider java:/ClusterJMSProvider, XAException.XAER_RMERR
(08/28 15:31:44:538):{Thread-5} [com.arjuna.ats.jta.logging.loggerI18N] [WARN] [com.arjuna.ats.internal.jta.recovery.xarecovery1] Local XARecoveryModule.xaRecovery got XA exception javax.transaction.xa.XAException: Error trying to connect to provider java:/ClusterJMSProvider, XAException.XAER_RMERR
(08/28 15:33:54:590):{Thread-5} [com.arjuna.ats.jta.logging.loggerI18N] [WARN] [com.arjuna.ats.internal.jta.recovery.xarecovery1] Local XARecoveryModule.xaRecovery got XA exception javax.transaction.xa.XAException: Error trying to connect to provider java:/ClusterJMSProvider, XAException.XAER_RMERR

Thank you for your help!

Re: Besx 5.0.4 Sbs11
 

try this

KB19525-"Failed creating initial list of hosts" appears in the BlackBerry Administration Service Application Service logs and the BlackBerry Administration Service is unable to start when using TCPPing

Re: Besx 5.0.4 Sbs11
 

Hi Knottyrope,

The line in the config file is exactly like what it says in Resolution 1:
<TCPPING initial_hosts="host1[17600],host2[17600]" port_range="10"

In Resolution 2, I can ping my server name. I did a ipconfig /flusheddns and restarted the BAS-AS service for good measure. However it is still the same.

Kind regards,

Re: Besx 5.0.4 Sbs11
 

KB34207-BlackBerry Administration Service is unable to communicate with other members of cluster if there are ports blocked among the nodes

or

KB33436-BlackBerry Administration Service will not stay running after applying 5.0 SP4 Maintenance Release 1 to 6

Re: Besx 5.0.4 Sbs11
 

you don't solve a solution and I wont be going to your site.

Re: Besx 5.0.4 Sbs11
 

Hi Knottyrope,

Thank you for your assistance! None of those did the trick I am afraid.

However, bit of a development. Over the weekend Java updated to version 7 and it stopped some of the BES services and they wouldn't start. Said that some files were missing. I uninstalled the update and restarted. Same thing. I then installed BESX over the top, it complained that it couldn't stop a services and wanted a restart. Once the server restarted it carried on. All ok. The handhelds are now getting mail but I still can't get into the console!

Kind regards,

Re: Besx 5.0.4 Sbs11
 

you might be better off reinstalling BAS or uninstall and install it again

since you wont lose the database, the phones will not have to be re activated