cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

SUP / Blackberry 6: Register User for application fails

Go to solution
tobit_kollenberg
Explorer

on ‎08-07-2012 2:58 PM

0 Kudos

Hi,

we are trying to use an self made application with the SUP OData SDK on Blackberry. But unfortunately, the user registration step fails and we don't know why.

Here is the code we are using within the BB-App:

UserManager.initialize("appIdentifier");
UserManager.setConnectionProfile(<serverIP>, 5001, "0");
UserManager.registerUser("user", "12345678");

The registerUser step results always in an UserManagerException which is nearly empty, except the error code which is 501.

We are using the BlackBerry 6 Simulator in the same LAN where the SUP is available.

The following log messages are from the Debug log.

[0.0] SUP ODP:  08:21:22.829 2012-08-07 D com.sybase.mobile.lib.client.MessagingClient reset all connectio[0.0] n tracking flags 
[0.0] SUP ODP:  08:21:22.833 2012-08-07 I com.sybase.mobile.lib.client.MessagingClient successfully set co[0.0] nnection properties 
[0.0] SUP ODP:  08:21:22.836 2012-08-07 D com.sybase.mobile.lib.client.UserManager connection properties s[0.0] et.. 
[0.0] SUP ODP:  08:21:22.840 2012-08-07 D com.sybase.mobile.lib.client.UserManager host: <ip-address> 
[0.0] SUP ODP:  08:21:22.843 2012-08-07 D com.sybase.mobile.lib.client.UserManager port: 5001 
[0.0] SUP ODP:  08:21:22.847 2012-08-07 D com.sybase.mobile.lib.client.UserManager farmID: 0 
[0.0] SUP ODP:  08:21:22.850 2012-08-07 D com.sybase.mobile.lib.client.UserManager username: tkg 
[0.0] SUP ODP:  08:21:22.853 2012-08-07 I com.sybase.mobile.lib.client.MessagingClient entering startClien[0.0] t 
[0.0] SUP ODP:  08:21:22.858 2012-08-07 I com.sybase.mobile.lib.client.MessagingClient checking if Messagi[0.0] ngClient is initialized 
[0.0] SUP ODP:  08:21:22.862 2012-08-07 D com.sybase.mobile.lib.client.MessagingClient reset all connectio[0.0] n tracking flags 
[0.0] SUP ODP:  08:21:22.865 2012-08-07 D com.sybase.mobile.lib.client.MessagingClient push object registe[0.0] red: false 
[...]
[0.0] SUP ODP:  08:21:24.100 2012-08-07 I com.sybase.mobile.lib.client.MessagingClient$SUPConnectionStateL[0.0] istener connection state changed 
[0.0] SUP ODP:  08:21:24.104 2012-08-07 D com.sybase.mobile.lib.client.MessagingClient$SUPConnectionStateL[0.0] istener connection state current change: status: DISCONNECTED 
[0.0] SUP ODP:  08:21:24.109 2012-08-07 D com.sybase.mobile.lib.client.MessagingClient$SUPConnectionStateL[0.0] istener connection state current change: connection type: 1 
[0.0] SUP ODP:  08:21:24.113 2012-08-07 D com.sybase.mobile.lib.client.MessagingClient$SUPConnectionStateL[0.0] istener connection state current change: error code: 0 
[0.0] SUP ODP:  08:21:24.118 2012-08-07 D com.sybase.mobile.lib.client.MessagingClient$SUPConnectionStateL[0.0] istener connection state change: error message: null 
[0.0] SUP ODP:  08:21:24.122 2012-08-07 D com.sybase.mobile.lib.client.MessagingClient$SUPConnectionStateL[0.0] istener setting isConnected value: false 
[...]
[0.0] 07T082125, T1, getDeviceSettings from server: Simulator20cce8f83463c1e4__appIdentifier : [0.0] Thu Feb 01 00:00:00 America/New_York 2001
[...]
[0.0] 07T082127, T3, tm uri:  'tm://mo/rmi?cid=0&devid=Simulator20cce8f83463c1e4__appIdentifier[0.0] &devtype=rim6&connid=S2D&rp=Y&valcode=12345678' 
[...]
[0.0] 07T082127, T1, writeToStream parameter: name='dtDeviceTimestamp' type=14 passtype=1
[...]
[0.0] SUP ODP:  08:21:28.492 2012-08-07 I com.sybase.mobile.lib.client.MessagingClient successfully starte[0.0] d client 
[0.0] SUP ODP:  08:21:28.498 2012-08-07 D com.sybase.mobile.lib.client.UserManager client started after re[0.0] gistraion 
[0.0] SUP ODP:  08:21:28.503 2012-08-07 D com.sybase.mobile.lib.client.UserManager checking if registratio[0.0] n succeeded.. 
[0.0] SUP ODP:  08:21:28.507 2012-08-07 I com.sybase.mobile.lib.client.MessagingClient checking if registr[0.0] ation succeeded.. 
[0.0] SUP ODP:  08:21:28.512 2012-08-07 D com.sybase.mobile.lib.client.MessagingClient neither connected, [0.0] nor disconnected with error, so sleeping for 1s 
[...]
[0.0] SUP ODP:  08:21:29.575 2012-08-07 D com.sybase.mobile.lib.client.MessagingClient neither connected, [0.0] nor disconnected with error, so sleeping for 1s 
[...]
[0.0] 07T082208, T3, MoObject.execute -- caught TM exception - 6:com.sybase.messaging.traveler.TmException[0.0] : TM Error: getKeysFromServer TM Error: InterruptedIOException:Local connection timed out after ~ 40[0.0] 000
[...]
[0.0] 07T082211, T3, execute:  objectName='MOInternalMO' methodName='Echo' param count(false)=0
[...]
[0.0] 07T082211, T3, tm uri:  'tm://mo/rmi?cid=0&devid=Simulator20cce8f83463c1e4__appIdentifier[0.0] &devtype=rim6&connid=S2D&rp=Y&valcode=12345678' 
[...]
[0.0] BbiAuth:ERR:No BBI Auth Token Request Engine available
[...]
[0.0] 07T082253, T3, MoObject.execute -- caught TM exception - 6:com.sybase.messaging.traveler.TmException[0.0] : TM Error: getKeysFromServer TM Error: InterruptedIOException:Local connection timed out after ~ 40[0.0] 000
[...]
[0.0] SUP ODP:  08:23:43.538 2012-08-07 I com.sybase.mobile.lib.client.MessagingClient$SUPConnectionStateL[0.0] istener connection state changed 
[...]
[0.0] SUP ODP:  08:23:43.548 2012-08-07 D com.sybase.mobile.lib.client.MessagingClient$SUPConnectionStateL[0.0] istener connection state current change: status: WAITING_TO_CONNECT 
[...]
[0.0] SUP ODP:  08:23:43.556 2012-08-07 D com.sybase.mobile.lib.client.MessagingClient$SUPConnectionStateL[0.0] istener connection state current change: connection type: 1 
[...]
[0.0] SUP ODP:  08:23:43.562 2012-08-07 D com.sybase.mobile.lib.client.MessagingClient$SUPConnectionStateL[0.0] istener connection state current change: error code: 0

Of course, it looks like an timeout and that the server is not reachable. But we can access the server via the simulator browser.

Has anybody an idea about whats wrong here?

BTW, we have no problems to register our users on iOS or Android...

Thanks and regards

Show replies
Show replies
Answer

Accepted Solutions (1)

Accepted Solutions (1)

rohith_deraje
Advisor
Advisor
‎08-07-2012 5:45 PM
0 Kudos

Hi,

1. Please check if MDS is running when you try to conect.

2. Please check the messaging port is 5001 on your SUP.

Sample code for registration is available at guide http://scn.sap.com/docs/DOC-23532

Regards

Rohith 

Show replies
Show replies
tobit_kollenberg
Explorer
‎08-08-2012 7:01 AM
0 Kudos

Hi Rohith,

thanks for your reply, the MDS was the right hint. It seems like that it is not possible to use the SUP OData SDK on Blackberry via WiFi. Is that correct?

Regards,

Tobit

rohith_deraje
Advisor
Advisor
‎08-08-2012 8:08 AM
0 Kudos

Hi Tobit,

BB registration from device using wifi seems to be having issue in 2.1.x. However you can use 2G/3G connection and connect through realy server. This should be working fine.

Regards

Rohith

Answers (0)

Ask a Question