Thank you for visiting the BlackBerry Support Community Forums.
BlackBerry will be closing the BlackBerry Support Community Forums Device Forums on April 1st (Developers, see below)
BlackBerry remains committed to providing excellent customer support to our customers. We are delighted to direct you to the CrackBerry Forums, a well-established and thorough support channel, for continued BlackBerry support. Please visit http://forums.crackberry.com or http://crackberry.com/ask. You can also continue to visit BlackBerry Support or the BlackBerry Knowledge Base for official support options available for your BlackBerry Smartphone.
"When we launched CrackBerry.com 10 years ago, we set out to make it a fun and useful destination where BlackBerry Smartphone owners could share their excitement and learn to unleash the full potential of their BlackBerry. A decade later, the CrackBerry community is as active and passionate as ever and I know our knowledgeable members and volunteers will be excited to welcome and assist more BlackBerry owners with their questions."
- Kevin Michaluk, Founder, CrackBerry.com
Developers, for more information about the BlackBerry Developer Community please review Join the Conversation on the BlackBerry Developer Community Forums found on Inside BlackBerry.
04-18-2008 04:25 PM
I am following the KB (KB10278) on migrating BES 4.1 (MSDE) to new hardware. My new server has a different Windows name than the original (BES-1 and BES-2). When I come to the part of the doc for BES installation on the new hardware it says "When prompted for BES name, use the same name as the existing BES name." When I enter the "existing" name it says it is not a valid Windows name. It will only let me use the same name as the new (BES-2) Windows name. Will this cause a problem later when I go to restore the existing database?
ALSO- I am using the same BESMgmt name for the databases.
04-19-2008 06:45 PM
When you restore the database you'll be overwriting all of these settings ... but you should be moving the database first (per the instructions).
If you connect to the BESMgmt database and execute:
select * from serverconfig
in query analyzer, or whatever interface you're using for sql client access, you want to call your BES the same thing as listed in the column "ServiceName"
You could also do:
select ServiceName from serverconfig
and it'll give you the name you need to enter during the install. Its possible the server name is BES-11 ...
04-22-2008 08:36 AM
It is very crucial that during the knife edge cutover process you call the installation (which will create new registry keys for your new server) with the same BESName as the server you are cutting over from.
If you are for any reason during a fresh clean install of BlackBerry Enterprise Server unable to specify a BESName (on the 7th screen during installation, right above the next button in a field called "BlackBerry Enterprise Server Name") then you might have the incorrect installer.
During a fresh clean install, usually this BESName will be filled out for you, the same as the netbios name of your Microsoft Windows Server you are attempting to install BlackBerry Enterprise Software on.
During a cutover process, this 7th setup screen (BES 4.1.x setup) needs to be tweaked, for a successful Knife Edge Cutover to take place.
The whole point of this is so that when you bring your database from BES-1 to BES-2, you arent creating a new BESName within BESMgmt database. There is nothing wrong with this, there are administrators out there with 5-10 BlackBerry Server's under 1 BlackBerry domain, but they designed it to be this way to serve their purposes.
An incorrect knife edge cutover will yeild similar results, even though this is not what the process was defined for.
Let's step back and re-check why the installation screen is not letting you use the BESName of the server your are cutting over from.
- Open BlackBerry Manager
- In the explorer view
- Under Servers
- Note down the BESName of the server you are cutting over from
- Ensure this is the exact name you are attempting to bring up the new BlackBerry Enterprise Server
Please keep us posted