So short version of a long story is that the server hosting the SQL databases for my BES fried. I am running BB Professional Software version 4.1 with 5 CAL's. The BPS is running on my domain controller and the database was running on a backup domain controller. I have reloaded the backup server with Windows Server 2003 and SQL express 2005 is running on it for another application (security cameras).

When I went in to the change the database to the reloaded server (using the same computername) things went to hell. Do I need to reinstall 4.1 to have the database created again? I am tempted to load SQL express 2005 on my domain controller (SBS 2003 Standard) and having it run off the same local machine instead of remoting in to the reloaded server.

Rigth now when I try to configure the BES server and choose the reloaded server it hangs when I put in the machine name and the database. Obviously this would be caused by there being now database named BESmgmt?

What do you guys think...reinstall from scratch? Install 2005Express on teh same computer as the BES is running? Figure out how to recreate the database on the remote server?

Thanks for any help.

Should I just download BB Professional 4.1 again and to an install over the version already on there? Will it recreate the DB?

So the production SQL is mirrored to a backup server? What kind of backup method is being used?

Is the DB name the same? Are all the SQL services started? Where is the backup server? Doees the BESAdmin have rights on that SQL Server? Double check that the permissions are the same and that there are no connection issues between the BES and that SQL Server.

No the old SQL database was on a remote server and the main HD crashed. I was not responsible for the server at the time. I have since fixed the server and reloaded Server 2003 and SQL express 2005. There was no backup done of the sql database on teh old server...so the BlackBerry Professional software is running on the domain controller with no connection to any database.

Ok, I get it now. I hope that you have a copy of your CALs, SRP and authentication key.

If you have all that you can simply create a blank DB on the SQL server and point the BES to it.

Here's how you do it:

1. Whatever version you are running, get the Database folder from the extracted installation files and place it on whatever drive you want on the SQL Server

2. Open a command prompt and navigate to the Database folder

3. Type "createdb.exe besmgmt.cfg" without the quotes

4. Run the Change DB Wizard and point to the BES to it again

That should get you up and running. If you prefer to reinstall the BES you can, whatever is easier for you at this point.

Just remember to do a backup of your DB after any major upgrades or changes. Then you can just restore it and you're good to go.