BES install error after SRP details

[endorphin6]

Hi,
We have an issue with our BES install using a remote SQL server (we are moving from one server using msde2000 to another with a remote SQL server). We get through the first half of the install, but after the reboot and the license details are picked up (SRP section), a dialog box appears to "check name" for the BES admin account to use and you click OK and then a message appears "Blackberry Enterprise Installation" with an exclamation mark but no message. Has anyone seen this? We have gone through all the pre-req (with Telstra). Picture is attached;
Thanks.

[GaryCutri]

Are you upgrading your existing install or is this a clean install which will be used to migrate users?

When you say "the license details are picked up" do you mean it automatically detected them from your previous install?

[BESadmin]

endorphin6 can you please check your private messages as I put some contact details down so we can help you over the phone, this way we can get you up and running much faster.

[endorphin6]

Hi,
This is a clean install but we deattached the database from MSDE2000 and attached it to a remote SQL server and then started a clean install and pointed the celan install to the SQL server which picked up all the license details deom the BESMgmt database we moved to SQL. Hope this helps. Thanks heaps.

[GaryCutri]

Note: Before you go to far ensure you have a backup copy of your SRP ID, Auth CALs & all your user CALs.

Normally when I upgrade customers from MDSE to SQL and the BES installation is moving to another server I do the following.

1. Backup ALL licensing information for the existing BES.

2. Shutdown and unplug the old BES server.

3. Ensure port 3101 is allowed outbound to the new server.

4. Double check that the BESadmin account has been configured correctly.

3. Log on as BESadmin and install BES 4.1.3 on a new server and create a NEW database on the SQL server.

4. Add all your users back onto the new server in lots of 5 and wait 10 minutes between adding the next lot of 5.

5. After a few seconds of adding the users back onto the BES you will see their device PIN will be automatically detected (You will have to keep refreshing the screen). In a few moments the devices will automatically start to do an Enterprise Activation.

[endorphin6]

I found out that the issue with the install is the SQL server or the Database that we attached. I managed to attach to another similar database on our test SQL with the BES admin account no problems and the install proceeded.

Are the logins case sensitive on the SQL server and are there any other things to check on the SQL server. Or should have we created the datbase schema before moing the BESMgmt database accross from the MSDE.
Thanks.

[BESadmin]

Please refer to the following article:

How to move from MSDE to SQL

[endorphin6]

Hi,
We realised the important step was "Type the command createdb.exe BESMgmt.cfg". We did not relaise that this also updated the "master" database on the SQL server with the important Blackberry error codes (70000 etc). Once this was run, the move worked.
Thanks.