BlackBerry Forums Support Community               

Closed Thread
 
LinkBack Thread Tools
Old 01-29-2013, 01:57 PM   #1 (permalink)
New Member
 
Join Date: Jan 2013
Model: 9360
PIN: N/A
Carrier: Bell
Posts: 4
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default BES Transporter

Please Login to Remove!

I'd like to start by stating that no formal training on BES administration but I've inherited a BES migration from 4.1.7 to 5.0.4. The 5.0.4 has already had a dozen or so users added but I have over 100 more users to migrate. The Transporter seems like the best option considering the circumstances but when I ran my first test the process completed with a MigrationCompletePending message. The test account was removed from the original BES but never appeared on the new one.

I've seen a post here suggesting to not assign policy during the transport so I left all those fields blank for my second test - still no joy.

Any recommendations?

I am using the transporter from brk 5.0.4.8 which is the latest available. My new BES is running at version 5.0.4 MR 1 (Bundle 52).

Thanks,
Cam
Offline  
Old 01-29-2013, 02:30 PM   #2 (permalink)
Knows Where the Search Button Is
 
AbidingSeraph's Avatar
 
Join Date: Apr 2006
Model: 9850
Carrier: Verizon
Posts: 46
Post Thanks: 3
Thanked 0 Times in 0 Posts
Default Re: BES Transporter

Is the transporter able to make a successful connection to the destination database?
Offline  
Old 01-29-2013, 03:31 PM   #3 (permalink)
New Member
 
Join Date: Jan 2013
Model: 9360
PIN: N/A
Carrier: Bell
Posts: 4
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default Re: BES Transporter

Connection tests on source and destination BESMgmt databases were successful. No errors or warning in the Preview step.
Offline  
Old 01-29-2013, 04:22 PM   #4 (permalink)
Knows Where the Search Button Is
 
AbidingSeraph's Avatar
 
Join Date: Apr 2006
Model: 9850
Carrier: Verizon
Posts: 46
Post Thanks: 3
Thanked 0 Times in 0 Posts
Default Re: BES Transporter

Have you tried migrating any other accounts, and does the error happen for all account migration attempts?
Offline  
Old 01-29-2013, 09:00 PM   #5 (permalink)
New Member
 
Join Date: Jan 2013
Model: 9360
PIN: N/A
Carrier: Bell
Posts: 4
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default Re: BES Transporter

I've tried twice now, the only difference being the group and policy assignments being left as default during the second transport. I read on another forum that this had allowed a transport when the assignment had resulted in MigrationCompletePending.

I also receive the following warnings in the BBET log:

SWITCH_SERVICE is still pending, device may be out of coverage
SET_IT_POLICY is still pending, device may be out of coverage

While going through the transporter logs I noticed my destination BES shows up as [5.0.3.13] when Programs lists it as 5.0.4 MR1; could the mismatch cause this or is it just how the versions are displayed?
Offline  
Old 01-30-2013, 12:42 PM   #6 (permalink)
Knows Where the Search Button Is
 
AbidingSeraph's Avatar
 
Join Date: Apr 2006
Model: 9850
Carrier: Verizon
Posts: 46
Post Thanks: 3
Thanked 0 Times in 0 Posts
Default Re: BES Transporter

I'm no expert on Transporter, but I use it occasionally. If you are using the same manifest file each time you attempt a migration, you might try to create a new manifest file and retry.

Also, if possible I would try and migrate an account in which you are able to verify that the device is not out of coverage and that is successfully communicating with BES.
Offline  
Old 01-30-2013, 02:52 PM   #7 (permalink)
New Member
 
Join Date: Jan 2013
Model: 9360
PIN: N/A
Carrier: Bell
Posts: 4
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default Re: BES Transporter

Unfortunately I have used new manifest files each full attempt. I realized after I attempted to migrate my first test account a second time that the manifest keeps track of accounts that have already been transported.

Didn't help that my test user also existed in the destination database despite not appearing in BAS manage users.

Both tests were done with a fully functional BlackBerry. I've tested activation on the new and old BES with this device to confirm and my signal strength is indicated as full.

I'm going to try a test with wireless connectivity and see whether that makes any difference. I'll post my results.

Still looking for help though if anyone has anything else to try.

Thanks,
Cam
Offline  
Old 05-18-2013, 06:24 PM   #8 (permalink)
Thumbs Must Hurt
 
Join Date: May 2007
Location: Columbus, OH
Model: 9000
PIN: N/A
Carrier: AT&T
Posts: 62
Post Thanks: 0
Thanked 0 Times in 0 Posts
Default Re: BES Transporter

The target BES needs to have all it's modules from the same version.

A couple years ago I used Transporter to move 2100 Users from BES 4 to BES 5.
The few that failed went out of coverage DURING the move.

I wrote an SQL query to read the Last Active Device, then automatically created the Manifest file. Worked like a charm, I moved about 100 people a night.
Offline  
Closed Thread


Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

vB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are On

Similar Threads for: BES Transporter
Thread Thread Starter Forum Replies Last Post
Special BES Express plans (UK) classact Carrier Specific Issues 0 05-16-2010 09:32 PM
Most bizarre BES problem I have ever had Jadey BES Admin Corner 24 08-14-2008 03:45 PM
Another Activating Initializing on BB Professional patrickd26 BES Admin Corner 4 05-06-2008 05:12 AM
Geographic Issues Affecting BES Migration nocerini BES Admin Corner 3 09-27-2007 11:13 AM
Eval to Full BES 4.0 for Domino - Changing SRP Hatchy BES Admin Corner 0 01-17-2006 07:59 AM





Copyright 2004-2014 BlackBerryForums.com.
The names RIM and BlackBerry are registered Trademarks of BlackBerry Inc.