Second BES Same BesMgmt DB - Upgrade Error
 

Hello Bes Type People,

Well here is my first post: Hope it makes sense.

I currently have a single bes (4.1.3) running with a remote database. I am running Exchange 2007 SP1 (I know not yet supported but wha the hell it works). I want to install a second bes (4.1.3) using the same BESMgmt database. I have two SRP ID's. I am performing the install as an initial 3.6 install then an upgrade to 4.1.3 (becasue vodafone won't give me the software becasue i installed SP1). I have successfully installed 3.6. Now when I go to install 4.1.3 I get the following error in my log.

=== Log started on 2/20/2008 at 17:11:15 ======================================
Log file C:\Program Files\Research In Motion\BlackBerry Enterprise Server\Logs\Installer\UserMigration.log creation OK
Initializing database BESMgmt at machine dbgb0100 using trusted authentication
Database connection OK
Loading status from file C:\Program Files\Research In Motion\BlackBerry Enterprise Server\Logs\Installer\UserMigrationStatus.bin
Status loaded from C:\Program Files\Research In Motion\BlackBerry Enterprise Server\Logs\Installer\UserMigrationStatus.bin
Migrating BES WGB00202 to primary BES WGB00202 using MAPI profile WGB00202
Migration writes status to the registry
BlackBerry Server WGB00202: Needs to be migrated
MAPI: Initialized MAPI with profile WGB00202
MAPI: Opened message store with profile WGB00202
BlackBerry Server WGB00202: Does not exist in the bes admin's mailbox
Migration finished with return code 12001
Writing status to file C:\Program Files\Research In Motion\BlackBerry Enterprise Server\Logs\Installer\UserMigrationStatus.bin
Status written to C:\Program Files\Research In Motion\BlackBerry Enterprise Server\Logs\Installer\UserMigrationStatus.bin
Uninitializing migration module
Disconnecting the database
Database disconnect OK
Closing the log file
=== Log ended on 2/20/2008 at 17:11:25 ======================================

Please help, alos if you have any tips the architecture i am choosing that would be greatly appreciated.


THANK YOU!

I think the error is resulting from the 3.6 and 4.1 database schema not being compatable with eachother. You need to have both BES at the same version pointing to one DB.

Try Cause 4

Also, you are installing 3.6 on a different machine right now correct? It has its own database, correct? What version of 3.6?

When you install the new server pick a new database name ... something like BESMgmtTemp

Then after you get it upgraded to 4.1.3 (or 4.1.4, or whatever version you want to be at), run the change database wizard and connect to the already existing production database. Then delete the BESMgmtTemp database.

Thanks for the speedy response guys! Much appreciated.

I was trying to point the 3.6 install installation on my second server at the 4.1 database. Due to schema differences this is clearly not going work.

hdawg: THANK YOU!

I'll temporarily install to a local database to get the version up to 4.1. Then repoint to the remote database. That will reolve my issue I'm sure.

One other point, I am terrified that when point the second BES to the remote database I'll get an SRP clash and get shutdown by RIM.

As I understand it as long as I specify a seperate SRP key on the second BES and then point it to the remote database then I should get no issues.

Can anyone confirm that this is correct? Plus if you have any other pointers regarding this setup they'd be greatly appreciated.

You're quite welcome.

That is absolutely correct. Just make sure you don't have two servers online ever at the same time using the same SRP.

OK, we're not quite right just yet. I have installed SQL 2000 SP3 on the second BES. Installed 3.6 using the local database. However, when I get the the User Migration section of the 4.1.3 upgrade process I still get the same error; see log below...


=== Log started on 2/21/2008 at 15:11:16 ======================================
Log file C:\Program Files\Research In Motion\BlackBerry Enterprise Server\Logs\Installer\UserMigration.log creation OK
Initializing database BESMgmt at machine WGB00202 using trusted authentication
Database connection OK
Loading status from file C:\Program Files\Research In Motion\BlackBerry Enterprise Server\Logs\Installer\UserMigrationStatus.bin
Status loaded from C:\Program Files\Research In Motion\BlackBerry Enterprise Server\Logs\Installer\UserMigrationStatus.bin
Migrating BES WGB002021 to primary BES WGB002021 using MAPI profile WGB00202
Migration writes status to the registry
BlackBerry Server WGB002021: Needs to be migrated
MAPI: Initialized MAPI with profile WGB00202
MAPI: Opened message store with profile WGB00202
BlackBerry Server WGB002021: Does not exist in the bes admin's mailbox
Migration finished with return code 12001Writing status to file C:\Program Files\Research In Motion\BlackBerry Enterprise Server\Logs\Installer\UserMigrationStatus.bin
Status written to C:\Program Files\Research In Motion\BlackBerry Enterprise Server\Logs\Installer\UserMigrationStatus.bin
Uninitializing migration module
Disconnecting the database
Database disconnect OK
Closing the log file
=== Log ended on 2/21/2008 at 15:11:20 ======================================

Any ideas? Need any more info from me?

Got it....

PICNIC.

I was attempting the upgrade before I had even defined the new server, configured the SRP ID and other server properties, in the manager for 3.6.

So of course there was no info inthe bes_admin mailbox relating to my new server. The server had not been set up yet...

I have now configured this information, started the upgrade and successfully began the upgrade process.

:).