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

Can't open Blackberry BESX admin page

I was trying to resolve an issue on our BESX 5.0.3 server where I couldn't add new Blackberry devices but managed to cause another issue in doing so - I now can no longer log into the administration page. It just returns with the error that IE cannot load the page.

The error in the log (EXCHANGE_BBAS-AS_01_20111018_0001) is below.

Any idea on how to fix? I have tired reinstalling the BESX server.
0
AlwaysAStudent
Asked:
AlwaysAStudent
1 Solution
 
mattclarifiedCommented:
Hi,

you didn't attach the error!  I had a similar problem a while ago and it was down to the certificates on the BAS server, ended up being such an issue I documented the whole thing.

I have attached my documentation, hopefully it will fix the error you're getting if the BBAS-AS error has something like;
 “LifecycleException:  service.getName(): "jboss.web";  Protocol handler start failed: java.io.IOException: Keystore was tampered with, or password was incorrect” after service is started.

M@
Blackberry-Administration---page.docx
0
 
bewaarseCommented:
Hi,

First we should try and change the BlackBerry Administration Service Application Server port:

    Stop the BlackBerry Administration Server - Application Server service.
    Open the BlackBerry Server Configuration Tool from Start > Programs > BlackBerry Enterprise Server.
    Select the Administration Service - High Availability tab.
    Change the HTTPS Service Port value from 443 to a port that does not conflict with any other software (for example, 663).
    Click Apply, and then OK.
    Start the BlackBerry Administration Server Application Server service.
    Access the BlackBerry Administration Service using the new port e.g. https://server.domain.com:663/webconsole/app.

if still the problem persist please check the following link to resolve the issue BlackBerry KB: 18185:

http://btsc.webapps.blackberry.com/btsc/search.do?cmd=displayKC&docType=kc&externalId=KB18185

0
 
AlwaysAStudentAuthor Commented:
Hi all, sorry about that, here's the error from that log.

The problem came after the administration page refused to let me log in, even when I was sure the password was correct. A troubleshooting page I found online said that I should delete the keystore key in the registry and it hasn't worked since then. Reinstalling after that didn't help.

I'll have a look at what you guys have suggested - thanks!
(10/19 08:05:42:655):{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

Open in new window

0
 
AlwaysAStudentAuthor Commented:
Thank you so much, changed my BESAdmin password to not include special characters then followed your guide to fix the keystore error which then came up next.
0
 
AgwayCommented:
Hi AlwaysAStudent - not sure if you check this account or not but here goes.

I seem to be locked out of our BESADmin account and I cant find how to change the password...
I read online that the password can change and in order to change it, you have to change a key in SQL MGMT 08 to be a number i.e. 4561245641526calkihnas and then it will change the password to berry... I cant get this to work either.


Can anyone help?
0

Featured Post

Get expert help—faster!

Need expert help—fast? Use the Help Bell for personalized assistance getting answers to your important questions.

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