[withanhdammit]

My production BES for Exchange is 4.1.6 and I'm going to 5.0.1 on a new server. I know that the BES Transporter tool is what I need to use for moving my users over. I plan on only moving a couple of us IT users over first for testing, then moving the rest of the users.

I have BES 5.0.1 running with a temp SRP and as far as I can tell, all is good with it. I just installed the BES Transporter tool and am running through the configuration.

Step 1 = User Manifest - no problem

Step 2 = BlackBerry Databases - problem
When I try to configure either the Source Domain or the Destination Domain I get the same result. I configure the source database and select new.
Label = BES01
SQLServer = bes01.domain.local
Auth = Windows (current user) <-- logged in locally as BESAdmin user
Database = BESMgmt


If I configure the destination database it gives me the identical error, I also tried setting the destination SQLServer to 'localhost' with no change in the result.




What am I missing here?

Thanks!

h

[withanhdammit]

I think I'm getting closer, my destination database is working


My source database is also getting closer, I think it is MSSQL2000 and the default instance name for that is MSSQLServer. When I use bes01\mssqlserver it returns a connection string error, I can also use \\bes01 and get the same connection string error, if I use bes01 by itself I get the original error that it cannot find the sql instance


I also tried using SQL authentication instead of Windows authentication but that returns similar results. I also confirmed that the BES01 is using Windows Auth to access the BESMgmt database


I'm pretty stumped here

[Joluth]

Have you verified that the account that you are logged on as has the correct permissions to the source DB? I don't recall off hand what the minimum is, but I am using an account with full access to both the 4.1 and 5.0 DBs.

[withanhdammit]

Yes, I am logging in with Windows Auth as BESAdmin. I have tried the Domain Admin as well as the SQL sa user. All yield the identical result.

[withanhdammit]

It took a bunch of googling to get this figured out, but after the error changed to "Connection string not valid" I realized that I was able to see the BES01, I just couldn't access it. I then came to understand that it's SQL2000 MSDE not SQL2000 Express which made a difference. Then I started looking for why SQL2000 MSDE couldn't connect to a remote system and learned that by default SQL2000 MSDE is set to not allow remote connections. Ah ha! Now I'm on to something.

I kept looking on my BES01 for the SQL configuration tool, but could not find it to see what network protocols were enabled. A little more googling led me to How to enable remote access to MSDE which then allowed me to enable Named Pipes and TCP/IP and viola! problem solved.

h

[knottyrope]

good job solving it.

[trombini]

good work !!

your migration occour normal after that ?