The way this system works is the BB device connects via 3G to the providers
BIS system which in turn hooks into the main BB core (SRP) system. The
default configuration in most cases is to configure email settings on the
main BB system to collect emails from the users existing email account.
(i.e.
http://providername.blackberry.com)
This has its limitations regarding synchronising with enterprise features -
e.g. Calendars, Contacts, Mailbox, etc. This can be done manually by
interfacing directly with Outlook using the BB Desktop software.
The alternative is to install a BB Enterprise Server Express (BES) that
links directly with the local Exchange server and commnicated directly
with the main BB core and in turn with the BB device itself. This provides
full synchronisation facilities OTA.
The installation needs to be done carefully to avoid weird problems.
1. The BESAdmin user account need to be configured properly with the
correct Exchange permissions, etc.
2. This account must not be hidden from the GAL.
3. I have found it easier if the account is temporarily added to the Domain
Admin group for the installation.
4. You must install the BES while logged in as BESAdmin.
If after installation you find the Admin website is not running it could be
a problem with the web keystore. Look for "Keystore was tampered with, or
password was incorrect" in the BAS-AS logs.
The trick is to manually rebuild the key store as follows:
-----------
As I alluded to in the edit of my previous post this was not a problem with
the password and logging in to BAS itself but rather an inconsistency with
the web.keystore file and the registry, apparently it's a known problem
with corruption that can occur during upgrade/installation.
The following steps are butchered from a document on btsc that details a
similar problem with BlackBerry Monitoring Service;
* Stop the BlackBerry Administration Service - Application Server and
BlackBerry Administration Service - Native Node Container
* Rename the web.keystore file to web.keystore.OLD under C:\Program
Files\Research In Motion\BlackBerry Enterprise Server\BAS\bin.
* Open a command prompt and navigate to C:\Program Files\Research In
Motion\BlackBerry Enterprise Server\BAS\bin.
Type the following command
webGenKey.bat "C:\Program Files (x86)\Java\latest java release directory\"
"C:\Program Files (x86)\Research In Motion\BlackBerry Enterprise
Server\BAS" mypassw0rd mybes.mydomain.com
Confirm a new web.keystore file now exists in the following path:
C:\Program Files\Research In Motion\BlackBerry Enterprise Server\BAS\bin.
* Open BlackBerry Server Configuration
Go to tab Administration Service - Web keystore
Change your password from (e.g.) mypassw0rd to something else (you're
limited to a particular list of special characters here so be aware) and OK
*Start the BlackBerry Administration Service - Application Server
(BlackBerry Administration Service - Native Node Container will start
automatically)
* Wait for the BAS-AS process to stabilise at around 630,00 - 650,00 K via
Task Manager
* Load your BAS page
Ta daaa
Thanks to all who took the time to reply, hopefully this will help someone
who finds themself in a similar situation.
------------
Source:
http://supportforums.blackberry.com/t5/BlackBerry-Enterprise-Solution/Cannot-connect-to-BAS-after-upgrade-to-5-0-3/td-p/1206507
