BES Admin Console Fails to Load

[alastairh]

My customer is moving over to new servers and requires to move their BES installation. So far I have done the following:

1. Backed up the existing BESMgmt database on the old server
2. Ran BES installation on the new server creating the default blank database
3. At this point all BES Services were running and web console accessible
4. Stopped all services on the new install and restored the backed up database to the new installation.
5. After restoring the database I updated references to the server name in the ServerConfig and MDSConfig tables.
6. Stopped BES on the old server and then started the services back up on the new server.

At this point the Blackberry devices started to successfully receive email and it seemed that the migration had went smoothly with only 10 mins downtime to the users between stopping services on one server and starting on the other.

However, my issue is that the web console fails to now load for management and windows event logs mention BAS-AS may be corrupted. I have since uninstalled and reinstalled BES and the same issue happens.

BES is installed with its own SQL Instance on Windows Server 2008 R2.

Does anyone have any suggestions as to how to fix the admin console issues.

Regards

Alastair

[NetworkGuy]

Check your services and make sure they all sign in as the exact same user.
The local admin account is not the same account as the domain admin account

I learned this the hard way during one of my upgrades.

If that is the problem, then reperform the install as the correct admin account.

[alastairh]

The BES install was performed as required under the BESAdmin account. All services are running under the BESAdmin account which has full local admin privileges.

All services, start, restart and stop successfully without any issues. BES runs apart from the web server/console application of it.

Thanks for the quick reply after two installs I am starting to hit a dead in.

Regards

[Zippygit]

What version of BES, you running a HA pair. I've has similar issues if the certificate/keystore is not implemented properly. IN by case (Running 5.0.3 MR3) BAS once started uses ~700MB of ram.. if you have certificate issues the BASAS process will not use more than 200 MB of ram. Once the issue is resolved it starts normally.

Hope this helps

Z