05-14-2013 12:10 PM
I'm having problems using the transporter tool. When it asks for the source db and I try to get it to connect to the old server, it gives me an error syaing there is a network or instance-related. It says the server is not found or is not accessible. It tells me to verify the instance name (which I put in the "Label" box) is correct and that the SQL Server is configured to allow remote connections. I followed the steps here and it still hasn't worked for me. It also does it for the destination db. I don't have any problems connecting to the databases when I'm using SSMS and the firewall is turned off.
Solved! Go to Solution.
05-23-2013 08:15 AM
Thank you for your question regarding the BlackBerry Enterprise Server Transporter tool.
When adding an instance name it goes into the SQL server field. (Ex: SQL/Instance)
The label field is there to simply to determine the source and destination.
Let us know if you have any other questions.
Come follow your BlackBerry Technical Team on Twitter! @BlackBerryHelp
Click "Accept as a Solution" for posts that have solved your issue(s)!
05-28-2013 08:29 AM
Hey Fozzie, thanks for the reply. I'm confused by your response. Are you saying that I should already have the instances available in the drop down menu in the Transporter tool? I don't have those. My only option is to select the "<new>" option and type in the labels for the databases on each server, new and old. For instance, I have two BB databases, BES and BESX. BES is the old database on the old server that I'm trying to migrate from. When I open the transporter tool and try to select the source db, the label is not there. So I select the "<new>" option provided in the dropdown and proceed to type the label for the source db and "chriserver-2" for my "SQL Server" name. Is there something I'm missing? What should I be typing in the "Label" and "SQL Server" fields?
05-30-2013 08:46 AM - edited 05-30-2013 08:47 AM
Just to clarify, this is the way you would want to setup the BlackBerry Enterprise Transporter.
Label: Old Server or New server (this name does not matter, it is just a classification name)
SQL Server: SQLServer/instance (this is used for the SQL Server name and the instance we are connecting too)
Authentication: What ever account you are going to use to connect to the SQL Server
I have also added some sceenshots of how it should be setup.
1.png is my source server and 2.png is my destination server.
05-30-2013 09:41 AM
As an additional note, the documentation that Blackberry gives here, leads you to believe that you only have to put the server name, which is why I was putting the instance name in the label box, of which I was not aware was so inconsequential.
I'm rockin the BlackBerry PRIV, Passport, Z30, Z10, Q10, BlackBerry Mini Stereo Speaker, 64 gig PlayBook,BT Headset HS-700
05-30-2013 10:08 AM
I use the server shown in SSMS when using transporter
if you dont use SQL often, it can be a hassle
I had tons of fun migrating a dozen databases with different software packages on a 5 year old SQL server and none of them were the same for SQL naming.
BESAdmin's, please make a signature with your BES environment info.
BES 12 and BES 5.0.4 with Exchange 2010 and SQL 2012 Hyper V