Welcome!

Welcome to the official BlackBerry Support Community Forums.

This is your resource to discuss support topics with your peers, and learn from each other.

inside custom component

BlackBerry® Enterprise Service 10

Reply
New Contributor
Posts: 6
Registered: ‎05-19-2008
My Device: Not Specified

Migration Issue (BES 4.1.6 to 5.0) BET and error message "Test BUA call failed"

Hey Guys, 

 

This is really doing my swede in so any help would be appreciated.  I able to migrate the users across using BET but I am unable to assign them to the default IT Policy which I am presuming is why I cannot get them into the interface. 

 

 

Ok so the migration seems to finish correctly but you can see the error "Test BUA call failed, BAS assignments unavailable" this I believe is the error that the Blackberry User Admin service is throwing. I used the correct credentials and although I had some JVM.dll error which are now sorted I think everything should be cool. 

 

Have any of you got any ideas of how to fix this issue?

 

Simon. 

 

 

(07/21 14:31:52) **** START USER SUMMARY ****
(07/21 14:31:52) user1@yourdomain.co.uk              MIGRATION_COMPLETE_PENDING
(07/21 14:31:52) user2@yourdomain.co.uk              MIGRATION_COMPLETE_PENDING
(07/21 14:31:52) user3@yourdomain.co.uk             MIGRATION_COMPLETE_PENDING
(07/21 14:31:52) **** END USER SUMMARY ****
(07/21 14:31:52) Preview Complete!
(07/21 14:31:53) BUA call complete. Result=-1
(07/21 14:31:53) Test BUA call failed, BAS assignments unavailable
(07/21 14:31:53) Global validation tasks completed
(07/21 14:34:46) Preview Starting
(07/21 14:34:46) Manifest: C:\Program Files (x86)\Research In Motion\BlackBerry Resource Kit\BlackBerry Enterprise Transporter\Manifests\lndnberrysvr-tmtnappsvr3.xml
(07/21 14:34:46) Preparing to process 3 users
(07/21 14:34:46) {user1@yourdomain.co.uk  } Skipping previously completed user
(07/21 14:34:46) {user1@yourdomain.co.uk  } Completing job TransId=10
(07/21 14:34:46) {user2@yourdomain.co.uk  } Skipping previously completed user
(07/21 14:34:46) {user2@yourdomain.co.uk} Completing job TransId=11
(07/21 14:34:46) {user3@yourdomain.co.uk } Skipping previously completed user
(07/21 14:34:46) {user3@yourdomain.co.uk } Completing job TransId=12

 

 

 

Please use plain text.
Forums Advisor I
bbinmyhart
Posts: 715
Registered: ‎07-02-2008
My Device: Z10

Re: Migration Issue (BES 4.1.6 to 5.0) BET and error message "Test BUA call failed"

BUA installed on wkst?
Please use plain text.
New Contributor
Posts: 6
Registered: ‎05-19-2008
My Device: Not Specified

Re: Migration Issue (BES 4.1.6 to 5.0) BET and error message "Test BUA call failed"

Everything is installed on the server
Please use plain text.
Forums Advisor I
bbinmyhart
Posts: 715
Registered: ‎07-02-2008
My Device: Z10

Re: Migration Issue (BES 4.1.6 to 5.0) BET and error message "Test BUA call failed"

Not saying that is the problem but don't think you should install BUA or BET (as part od the RK) on either server but rather on a workstation.
Please use plain text.
Contributor
Speeder
Posts: 11
Registered: ‎07-27-2009
My Device: Not Specified

Re: Migration Issue (BES 4.1.6 to 5.0) BET and error message "Test BUA call failed"

You have to in BET, go to Config Tab > Blackberry Administration Service and enter the credentials.

 

Please use plain text.
New Contributor
mb96net
Posts: 3
Registered: ‎09-25-2009
My Device: Not Specified

Re: Migration Issue (BES 4.1.6 to 5.0) BET and error message "Test BUA call failed"

I have the same problem and I do have the credentials populated (I've tried many times and the password is correct).
Please use plain text.
New Contributor
mb96net
Posts: 3
Registered: ‎09-25-2009
My Device: Not Specified

Re: Migration Issue (BES 4.1.6 to 5.0) BET and error message "Test BUA call failed"

I had that JVM.dll issue too and I thought I had sorted it out as well by adding the latest version I had into the PATH, but you can't use the latest version it has to be version 5. I uninstalled BUA and reinstalled it allowing it to add the PATH variable itself and then BET worked (very nicely I might add).

 

The documentation from RIM and the packaging of all the resource kit seperately sucks. I would like to see one install file for the resource kit and give me checkboxes for the options I want to install. I think most BES admins will want to install many of the resource kit tools and it sucks having to download each tool individually.

 

enough ranting...cheers.

Please use plain text.
Contributor
BERRA
Posts: 20
Registered: ‎02-09-2010
My Device: backberry 8703e

Re: Migration Issue (BES 4.1.6 to 5.0) BET and error message "Test BUA call failed"

 

Hello mb96net,

 

what is your procedure to add the path for jvm.dll file , because i am having the same problem ,

 

 

thank you

 

Berra

Please use plain text.
New Contributor
mb96net
Posts: 3
Registered: ‎09-25-2009
My Device: Not Specified

Re: Migration Issue (BES 4.1.6 to 5.0) BET and error message "Test BUA call failed"

Like I mentioned, I uninstalled BUA and then re-installed it, but to update the path it's just the windows path system variable. In windows 2003 it's right click on my computer, go to the advanced tab and click on environment variables.

Please use plain text.
Contributor
BERRA
Posts: 20
Registered: ‎02-09-2010
My Device: backberry 8703e

Re: Migration Issue (BES 4.1.6 to 5.0) BET and error message "Test BUA call failed"

[ Edited ]

 

Thank you  mb96net for the quick reply ,

 

i'm still having same problem even when i updated re-installed and updatedthe jvm.dll path. i am still getting BAS assignments unavailable - BUA test call faild.

 

i tried log in using BAS and AD but still not working .

 

any help.

 

here the log

 

(02/09 15:35:40.069):{0x2684:1} [INFO] Hopper getting users from manifest
(02/09 15:35:40.069):{0x2490:8} [DEBUG] {besuser@domain.com} Next job task is VALIDATION
(02/09 15:35:40.100):{0x1ACC:4} [DEBUG] BUA console output:

(02/09 15:35:40.100):{0x1ACC:4} [INFO] BUA call complete. Result=1
(02/09 15:35:40.100):{0x1ACC:4} [WARNING] Test BUA call failed, BAS assignments unavailable
(02/09 15:35:40.100):{0x1ACC:4} [INFO] Global validation tasks completed
(02/09 15:35:40.100):{0x1ACC:4} [INFO] {besuser@domain.com} Validating user, TransId=1
(02/09 15:35:40.116):{0x1ACC:4} [DEBUG] {besuser@domain.com} Checking for user in SourceDatabase: besmgmt on bes02
(02/09 15:35:40.116):{0x1ACC:4} [DEBUG] {besuser@domain.com} User exists in SourceDatabase: besmgmt on bes02
(02/09 15:35:40.116):{0x1ACC:4} [DEBUG] {besuser@domain.com} Checking for user in DestinationDatabase: besmgmt on BES03\BLACKBERRY
(02/09 15:35:40.116):{0x1ACC:4} [DEBUG] {besuser@domain.com} User does not exist in DestinationDatabase: besmgmt on SLMKBES12\BLACKBERRY
(02/09 15:35:40.116):{0x1ACC:4} [INFO] {besuser@domain.com} Loading source data for user
(02/09 15:35:40.116):{0x1ACC:4} [INFO] {besuser@domain.com} User device version: 5.0.0.344
(02/09 15:35:40.116):{0x1ACC:4} [INFO] {besuser@domain.com} Loading destination data for user
(02/09 15:35:40.116):{0x1ACC:4} [INFO] {besuser@domain.com} Checking UserConfigId availability
(02/09 15:35:40.116):{0x1ACC:4} [INFO] {besuser@domain.com} UserConfigId can be preserved with DeviceUserId column
(02/09 15:35:40.131):{0x1ACC:4} [INFO] {besuser@domain.com} Validating user data
(02/09 15:35:40.163):{0x1ACC:4} [WARNING] {besuser@domain.com} WARNING: basConfig, BAS assignments unavailable - BUA test call failed, check credentials and that BUA is configured for the correct domain
(02/09 15:35:40.163):{0x1ACC:4} [WARNING] {besuser@domain.com} *** User has data warnings and can only be migrated with the ignore warnings option ***
(02/09 15:35:40.163):{0x1ACC:4} [WARNING] {besuser@domain.com} User validated with warnings, TransId=1
(02/09 15:35:40.163):{0x2490:8} [DEBUG] {besuser@domain.com} Next job task is COMPLETE
(02/09 15:35:40.163):{0x2490:8} [INFO] {besuser@domain.com} Completing job TransId=1
(02/09 15:35:40.163):{0x2490:8} [DEBUG] Transporter Preview Status: Processed=1, Valid=0, Warnings=1, Invalid=0
(02/09 15:35:40.163):{0x2490:8} [INFO] Hopper getting next load balanced user from manifest
(02/09 15:35:41.647):{0x24C0:9} [DEBUG] Shut down called
(02/09 15:35:41.663):{0x24C0:9} [INFO] Enterprise Transporter Shutting Down...
(02/09 15:35:41.663):{0x24C0:9} [INFO] **** START USER SUMMARY ****
(02/09 15:35:41.663):{0x24C0:9} [INFO] besuser@domain.com    VALIDATION_COMPLETE_WARNINGS
(02/09 15:35:41.663):{0x24C0:9} [INFO] **** END USER SUMMARY ****
(02/09 15:35:41.663):{0x24C0:9} [INFO] Preview Complete!
(02/09 15:35:44.350):{0x24C0:9} [INFO] Enterprise Transporter Shutdown!

 

Please use plain text.