Blackberry SUP connection error on device 9800

[Former Member]

Hi,

I am writing app using SUP 2.1.3 Odata SDK.

I am able to initilise, register, login and connect through Blackberry 9800 Simulator.

Same app I am trying using device.

1) I have uploaded all proxy cod files required for app, [ if this would have been problem then module not found error would have been thrown ]

2) I have checked Service book and it has IPP entry for BIS/BES service and I have active sim card

On

UserManager.initialize(

ResourceManager.getString(XYZResource.

DEFAULT_APPNAME)

and

UserManager.isRegistered()

I am getting this error log : File system error (1003)

also got this [0.0] TAC:TAI.handleRegRsp : ALREADY_REGISTERED  but not sure from where it is coming

Did any one in SAP and Sybase run this on device?

If yes please help.

Regards,

Hemal

[Former Member]

Hi Srikanth,

I tried these things.

Now I have 2 different User for simulator and device.

I have deleted all cod files and application and trying to use sup user to register and log in as per my profile ( device or simulator).

Simulator get loged in on SUP and then gets SAP odata with SAP credentials but on device i get debug log as file error 1303. I have got BES and BIS service book enabled.

So your suggestion is not wokring here. Please help as we are not able to show our app to customer while we have finished wokring on simulator. SUP is very fustrating in that sense but I hope you will able to guide.

[former_member205692]

Hi Hemal,

Did you get this working on the device? If not, the issue could be that you are not using a relay server to connect while using the application on the device.

On the simulator you would be on the corporate network but when using the device you are on mobile network so to access SUP you might have to do it via a relay server.

Regards,

Suhas

[Former Member]

Hi Suhas,

Thanks for reply but it still now wokring and I tried send this problem to varoius people but with little help or no luck.

I have got MDS service runing in my device.

When I use networkdignostic tool ( a java app) on blackberry it shows MDS connection available and working.

I have got fresh installation of my app along with all 4 requires SUP libs/dependent modules ( common, moca, messeging and sup_json) on device.

SUP control centre user is also new ( seprate form one i used for simulator).

I have got filter in place to choose right credintals based on profile ( either simulator or device).

When I do

UserManager.initialize(

ResourceManager.getString(XYZResource.

DEFAULT_APPNAME) and then check for user isRegistered and then setConnection profile.

On setConnectionProfile and call

UserManager.asyncRegisterUser(username, actcode);

: if i use relay server url along with farm id and correct port it comes back with

UserManageException -- 7003 which means REGISTRATION_FAILED_FOR_UNKNOWN_ERROR

and if I use direct SUP server url with 5001 port and farm id as "0" , in ecplise log it says :

catastrophic error occured and relay url template error.

I have to then delete all libs and apps form device.

In all it is been very very painfull process and still can not get to work.

Same code is wokring properly on simulator so very disapplinted with support I get here.

I am been doing mobile development from many years but this has to be worst support side till now.

Regards,

Hemal

[Former Member]

This is the error I get :

[394.976] 13T172315, T4, A catastrophic error occurred and MOCA server queue processing is shutting down.  Exc[394.976] eption: net.rim.device.api.system.ControlledAccessException

[Former Member]

We checked log on relay server iis and request do come to it properly

it get proper relay url but then it gives error..

so one must help here!!!!!!

here is log from BB decvie coming to eclipse consol

[675.89] 13T180548, T4, Found good Relay Server URL Template: /ias_relay_server/client/rs_client.dll/%cid%/tm[675.89]

[675.914] VM:CMPOv=3

[675.914] 13T180549, T4, A catastrophic error occurred and MOCA server queue processing is shutting down.  Exc[675.914] eption: net.rim.device.api.system.ControlledAccessException

[675.929] VM:CMPOv=2

[Former Member]

Hi,

    Below is the simple code to make registration for a User:

     UserManager.initialize(appName);// appName is  the Application created with Basic security configuration                                                             // in SCC

     UserManager.setConnectionProfile(relayserver.sybase.com",80,farmid);

     if (!UserManager.isRegistered())

     UserManager.registerUser("aa","123");//aa is Manual User created for appname in SCC

Can you please try a simple app with this above code, and check what error you are getting or is user getting registered ?Do check wheather relayserver state is running in outbound enabler tab.

Thanks,

Srikanth M

[Former Member]

Ok will try with that now.

Can you give me actual appName -- ?

and farmid -- ? to be use in code?

About relay server, it is runing as we have try using iPhone also Blackberry simulator is hitting relay server which is wokring fine.

Regards,

Hemal

[Former Member]

Hi,

  appName here is the Application created with Basic security configuration in Sybase Control Center  and

farmid is the relay server fram-id.

Please let me know if we are not clear.

Thanks,

Srikanth M                                   

[rohith_deraje]

Hi Hemal,

you can refer to the beginners guide at http://scn.sap.com/docs/DOC-23532. This gives you the basic details needed to connect the app to SUP. Hope this will help you.

Regards

Rohith

[Former Member]

Hi Hemal,

If things are working fine on simulator and the user is getting registered, then probably your app should run on the device as well.  Provided you are using a 2G or 3G network  and trying to connect to SUP via a relay server. The snippets in the mocalogs hint that everything you have done is reasonable.

Hope you have compiled your project with BB jdk 6.0.0. I think you would have done it properly.

My curiosity here is "controlledAccessException", i have faced it many times.

First change the application name , i.e the project name, compile it again and load the "newappname.cod" along with other cods and try.

If you are still getting it consistently follow this:

1. Delete all the 2.1.3 application first.

2. Then using java loader run the below mentioned delete command ( Just copy the below given commands to a notepad change the location to your javaloader.exe location and change application name to your application cod name,  then save it with file name  "XYZ.bat"  and type is AllFiles (*.*) in the same folder where you have your javaloader.exe , connect the device to the PC and run the XYZ.bat)

-------------------------------------------------------------------------------------------------------------------------------------------------

set JAVALOADER="Your location of javaloader\JavaLoader.exe"

%JAVALOADER% -usb erase -f MocaClientLib.cod MessagingClientLib.cod CommonClientLib.cod sup_json.cod Yourapplication1.cod Yourapplication2.cod

pause

-------------------------------------------------------------------------------------------------------------------------------------------------

This should solve the problem, if this doesn't solve then a security wipe of the device is a must to get rid of controlled access exception. Note that doing a security wipe out of the device will clear enterprise activation as well!!! you will have to get it redone.

Note: All my above suggestions are valid only after you have hit the relay server . I see that in the above comment of yours, you are already doin it, "Found good url template " in the mocalog is sufficient hint to make sure that you are hitting the relay server properly.

Regards,

Phaneeshln

[Former Member]

Hi Rohit,

Thanks for the reply.

Guide you have refered is something we have already refereed.

We have Application name, connection created in SCC properly.

We have used it sucessfully in iPhone Simulator and Device, Android simulator and device and Blackberry simulator.

Also code sinppet is guide is exactly waht we are doing ( and also sucessfully except blakcbery device) but still its not working unfortunately.

I am not saying we are not doing anything wrong here as I am sure there is something I am missing but not able to find out what is main problem.

Thanks this time and all future help.

Regards,

Hemal

[Former Member]

Hi Phaneesh,

This very fist somewhat helpfull answer so far. Really appricate.

One thing different I am doing is I am using Blackberry JRE 5.0 compile, preverify application against. Althouh I am using BB 9800 with OS 6, we have cleint requirement to support device with OS 5 so I choose BB JRE 5 to begin with.

From your post it looks we need BB JRE/JDK 6.0.0 instead ( it is not mentioend as mandtory anywhere in at SUP docs at sybase infocentre). So I will try this and update you soon.

As you rightly said I do hit relay server and I am very confident about it as I monitored realy server logs in realtime when I hit from device over 3G. And I got server log showing request coming in. Then I compare that with the log while request generated from simulator and it was identical in nautre except last numbes were differnet e.g. 234, 117 Boyand this point everythign becomes blak hole. As I do not see relay coming to SUP at all and not logs on SUP side and BB client logs shows ControlledAccessException.

Also thanks very much for Javaloader batch file tip. I am using that command anyways but batch file approach would be certainly more usefull.

Although my mian intrest to make this applciation work on BB device so I will change name of project, applciation name and try but I did not understood reason behind it. I will do that in anycase as suggested by you.

We have got device from our cusotmer with entrprice activation thus we have MDS transort enabled and I can see that in service book and I can hit relay as well so will see but I can not do security wipe.

Thanks for all the help so far.

Regards,

Hemal

[Former Member]

Hi Phaneesh,

I tried with BB JDK/JRE 6 this time still error is same.

Here is complete Log from device :

[883.015] FirstTimeLoginScreen:in doRegister
[883.062] VM:NCICv=25,w=0
[883.085] VM:CMPOv=3
[883.148] VM:CMPOv=8
[883.179] VM:CMPOv=4
[883.242] VM:CMPOv=8
[883.289] VM:CMPOv=3
[883.328] VM:CMPOv=4
[883.375] VM:CMPOv=5
[883.414] VM:CMPOv=4
[883.429] VM:CMPOv=2
[883.46] VM:CMPOv=3
[883.507] VM:CMPOv=5
[883.578] VM:CMPOv=9
[883.609] CMM: -5(593) no sig from 0x33
[883.656] VM:FSOMv=4
[883.679] VM:CMPOv=3
[883.726] VM:CMPOv=2
[883.75] VM:CMPOv=2
[883.765] VM:CMPOv=2
[883.859] VM:CMPOv=2
[883.945] VM:FSOMv=2
[883.968] VM:CMPOv=3
[883.984] VM:CMPOv=2
[884.031] VM:LMMOr=1d390800,t=net.rim.device.internal.io.store.FileImpl
[884.046] VM:CMPOv=2
[884.101] VM:CMPOv=6
[884.171] VM:CMPOv=2
[884.265] VM:CMPOv=3
[884.335] VM:CMPOv=9
[884.429] VM:CMPOv=9
[884.554] VM:CMPOv=3
[884.609] VM:CMPOv=2
[884.765] 17T112640, T1, ThreadID = Thread[Thread-506613760,5] maps to short thread id 1
[884.789] VM:CMPOv=3
[884.804] 17T112640, T1, Starting Log.  Current time: 20120917T112640
[884.843] VM:CMPOv=5
[884.851] 17T112640, T1, MocaLog Logging Level: Everything
[884.882] VM:CMPOv=4
[884.89] 17T112641, T1, MocaLog AppId: ManageTimeSheet
[884.906] VM:CMPOv=2
[884.914] 17T112641, T1, iMo Version Number: 2.1.3.6319
[884.937] VM:CMPOv=3
[884.945] 17T112641, T1, MessagingClientLib: initInstance. App ID: ManageTimeSheet, Log Level 4
[884.96] VM:CMPOv=2
[884.968] 17T112641, T1, Starting CmoBinary::cleanOldFiles
[885.054] VM:CMPOv=11
[885.07] 17T112641, T1, Searching file pattern: file:///store/home/user/Sybase/MessagingLib/mobinary/mobinary[885.07] _cookie_*
[885.085] VM:CMPOv=2
[885.148] 17T112641, T1, Finished CmoBinary::cleanOldFiles
[885.195] VM:CMPOv=6
[885.335] VM:CMPOv=7
[885.414] VM:CMPOv=7
[885.484] VM:CMPOv=7
[885.554] BBSUPAppController:After user initialize ....
[885.617] VM:CMPOv=6
[885.71] VM:CMPOv=10
[885.796] VM:CMPOv=9
[885.867] VM:CMPOv=7
[885.929] VM:CMPOv=6
[885.929] JVM: bklt @885929: timer
[885.929] JVM: bklt[1] @885929: usrIdle 4, usrTime 30, usrAct 1
[885.929] JVM: bklt[1] @885929: chkIdle 24, currTime 31
[885.929] JVM: bklt @885929: setTimer 26
[886.039] VM:CMPOv=11
[886.375] VM:CMPOv=8
[886.804] NVS: same 69
[886.804] NVS: commit 0
[886.859] VM:CMPOv=2
[887.359] FS: CLEAN(854 5)
[888.234] VM:CMPOv=5
[888.679] BBSUPAppController:registerUser12
[888.703] FS: CLEAN(968 5)
[889.945] BBSUPAppController:asyncRegisterUser called
[890.75] FS: CLEAN(1158 5)
[891.867] VM:CMPOv=4
[891.968] VM:EGLCv=16496
[892.101] VM:EGLCv=16736
[892.156] VM:EGLCv=17004
[892.156] FS: CLEAN(1161 5)
[892.531] VM:EGLCv=17268
[892.562] VM:EGLCv=17548
[892.601] VM:EGLCv=17836
[892.648] VM:EGLCv=18124
[892.671] 17T112649, T2, ThreadID = Thread[Thread-314182656,5] maps to short thread id 2
[892.687] VM:CMPOv=2
[892.703] 17T112649, T2, MessagingClientLib: setConnectionProperties
[892.773] VM:CMPOv=9
[892.781] 17T112649, T2, ClientConfig: commit
[892.914] VM:CMPOv=17
[892.929] 17T112650, T2, ClientConfig: notify change: 1
[893.039] VM:CMPOv=14
[893.062] 17T112650, T2, ClientConfig: notify listeners prop: 1
[893.117] VM:CMPOv=7
[893.25] 17T112650, T2, ClientConfig: notify change: 2
[893.296] VM:CMPOv=6
[893.312] 17T112650, T2, ClientConfig: notify listeners prop: 2
[893.335] VM:CMPOv=3
[893.382] 17T112650, T2, ClientConfig: notify change: 3
[893.484] VM:CMPOv=13
[893.5] 17T112650, T2, ClientConfig: notify listeners prop: 3
[893.695] VM:CMPOv=25
[893.703] 17T112651, T2, ClientConfig: notify change: 10001
[893.867] VM:CMPOv=21
[893.89] 17T112651, T2, ClientConfig: notify listeners prop: 10001
[893.976] VM:CMPOv=11
[893.992] 17T112651, T2, ClientConfig: notify change: 10002
[894.093] VM:CMPOv=13
[894.109] 17T112651, T2, ClientConfig: notify listeners prop: 10002
[894.14] VM:CMPOv=4
[894.203] VM:CMPOv=8
[894.218] VM:EGLCv=18532
[894.226] FS: CLEAN(1162 5)
[894.898] VM:EGLCv=18828
[894.921] VM:EGLCv=19080
[894.945] VM:EGLCv=19336
[894.968] VM:EGLCv=19624
[894.984] 17T112652, T2, MessagingClientLib: register MocaObject.
[895.031] VM:CMPOv=6
[895.039] 17T112652, T2, MessagingClientLib: initClient.
[895.054] VM:CMPOv=2
[895.07] 17T112652, T2, OBEngine version: 1.0.0
[895.101] VM:CMPOv=4
[895.117] 17T112652, T2, ClientConfig: commit
[895.14] VM:CMPOv=3
[895.148] 17T112652, T2, ClientConfig: notify change: 1401
[895.234] VM:CMPOv=11
[895.25] 17T112653, T2, ClientConfig: notify listeners prop: 1401
[895.335] VM:CMPOv=11
[895.398] VM:CMPOv=7
[895.523] 17T112653, T2, ClientConfig: commit
[895.546] VM:CMPOv=3
[895.546] 17T112653, T2, ClientConfig: notify change: 1202
[895.632] VM:CMPOv=11
[895.648] 17T112653, T2, ClientConfig: notify listeners prop: 1202
[895.828] VM:CMPOv=23
[896.195] VM:CMPOv=47
[896.242] 17T112654, T2, ClientConfig: commit
[896.343] VM:CMPOv=13
[896.359] 17T112654, T2, ClientConfig: notify change: 1203
[896.359] FS: CLEAN(1167 5)
[896.867] VM:CMPOv=65
[896.882] 17T112655, T2, ClientConfig: notify listeners prop: 1203
[896.898] VM:CMPOv=2
[896.921] 17T112655, T2, ClientConfig: commit
[896.945] 17T112655, T2, ClientConfig: notify change: 1200
[896.96] 17T112655, T2, ClientConfig: notify listeners prop: 1200
[897.007] VM:CMPOv=4
[897.109] VM:CMPOv=2
[897.132] VM:CMPOv=3
[897.25] VM:CMPOv=7
[897.257] 17T112655, T2, Reencode persistent data, wait for ticket. Current generation: 0, stored generation: [897.257] -1
[897.281] VM:CMPOv=3
[897.289] 17T112655, T2, Reencode persistent data. Got ticket.
[897.32] VM:CMPOv=4
[897.335] 17T112655, T2, encodeMocaQueues
[897.359] VM:CMPOv=3
[897.375] 17T112655, T2, ClientConfig: commit
[897.398] VM:CMPOv=3
[897.46] VM:CMPOv=8
[897.515] 17T112656, T2, MocaClient register MocaObject named: MocaClientAgent
[897.546] FS: CLEAN(1185 5)
[899.148] VM:-LGCMt=206,s=144188,p=
[899.156] VM:CMPOv=207
[899.164] 17T112657, T2, MocaClient register MocaObject named: SettingsExchange
[899.328] 17T112657, T2, MocaClient register MocaAsyncResponse named: SettingsExchangeRestartResponse
[899.343] 17T112658, T2, MocaClient register MocaObject named: RobieFileTransfer
[899.351] 17T112658, T2, MocaLibrary: CLIENT_INITIALIZED:
[899.367] 17T112658, T2, MocaClient register MocaObject named: SUP
[899.39] 17T112658, T2, MessagingClientLib: register MocaObject.
[899.445] VM:CMPOv=7
[899.46] 17T112658, T2, MocaClient register MocaObject named: GetDeviceLogs
[899.531] VM:CMPOv=9
[899.562] VM:EGLCv=19924
[899.664] 17T112658, T2, MessagingClientLib: addConnectionStateListener
[899.695] VM:CMPOv=4
[899.726] VM:EGLCv=20220
[899.734] FS: CLEAN(1192 5)
[900.992] 17T112659, T2, MessagingClientLib: addConfigurationChangeListener
[901.007] VM:CMPOv=2
[901.054] VM:EGLCv=20552
[901.085] VM:EGLCv=20888
[901.093] 17T112700, T2, MessagingClientLib: startClient.
[901.117] 17T112700, T2, Applog Status - 11:27:00 Engine Startup
[901.14] VM:CMPOv=3
[901.148] 17T112700, T2, MessagingClientLib: setConfigProperty
[901.195] VM:CMPOv=6
[901.21] 17T112700, T2, MessagingClientLib: propertyDisplayOnly
[901.234] VM:CMPOv=3
[901.257] 17T112700, T2, MessagingClientLib: setConfigProperty (2701): 679370763
[901.335] VM:CMPOv=9
[901.343] 17T112700, T2, ClientConfig: commit
[901.359] VM:CMPOv=2
[901.367] 17T112700, T2, ClientConfig: notify change: 2701
[901.398] VM:CMPOv=4
[901.421] 17T112700, T2, ClientConfig: notify listeners prop: 2701
[901.5] VM:CMPOv=10
[901.523] VM:CMPOv=2
[901.539] 17T112700, T2, MessagingClientLib: getConfigProperty
[901.57] VM:CMPOv=4
[901.843] 17T112701, T2, Push port changed. Setting push port. Old port: 0 New port: 46013
[901.843] VM:FSOMv=2
[901.937] VM:CMPOv=12
[901.953] 17T112701, T2, MessagingClientLib: setConfigProperty
[902.0] VM:CMPOv=6
[902.015] 17T112701, T2, MessagingClientLib: propertyDisplayOnly
[902.117] VM:CMPOv=13
[902.132] 17T112701, T2, MessagingClientLib: setConfigProperty (2702): 46013
[902.156] VM:CMPOv=3
[902.164] 17T112701, T2, ClientConfig: commit
[902.203] VM:CMPOv=5
[902.21] 17T112701, T2, ClientConfig: notify change: 2702
[902.296] VM:CMPOv=11
[902.32] 17T112702, T2, ClientConfig: notify listeners prop: 2702
[902.398] VM:CMPOv=10
[902.484] VM:CMPOv=11
[902.5] 17T112702, T3, ThreadID = Thread[Thread-174823424,5] maps to short thread id 3
[902.507] FS: CLEAN(1196 5)
[903.101] VM:CMPOv=77
[903.117] VM:EGLCv=21140
[903.132] 17T112702, T3, Starting Push Listener.
[903.148] VM:CMPOv=2
[903.179] 17T112703, T3, MessagingClientLib: getConfigProperty
[903.203] VM:EGLCv=21440
[903.218] 17T112703, T3, Push enabled. Client will be running in Push mode.
[903.281] VM:CMPOv=8
[903.304] VM:EGLCv=21796
[903.39] VM:EGLCv=22148
[903.554] VM:EGLCv=22492
[903.695] VM:EGLCv=22832
[903.703] FS: CLEAN(1209 5)
[904.992] 17T112705, T4, ThreadID = Thread[Thread-137416704,5] maps to short thread id 4
[905.007] VM:CMPOv=2
[905.007] 17T112705, T4, MocaProcessServerQueue.ProcessTillStopped started.
[905.078] 17T112705, T2, MocaProcessQueue.start -- queue processing started
[905.101] 17T112705, T4, Device not in low storage state: 0, null
[905.125] 17T112705, T2, MocaProcessQueue.start -- queue processing started
[905.14] VM:CMPOv=2
[905.164] 17T112705, T5, ThreadID = Thread[Thread-136273920,5] maps to short thread id 5
[905.226] VM:CMPOv=8
[905.234] 17T112705, T5, MocaProcessClientQueue.ProcessTillStopped started.
[905.25] VM:CMPOv=2
[905.265] 17T112705, T4, MocaConnectionConditions::isLowStorage- Storage sufficient unchanged (0)
[905.304] VM:CMPOv=5
[905.32] 17T112705, T2, MocaClient Started
[905.375] VM:CMPOv=7
[905.39] 17T112705, T4, Device not in low storage state: 0, null
[905.406] VM:CMPOv=2
[905.429] 17T112705, T2, requestServerSettings
[905.507] VM:CMPOv=10
[905.523] 17T112706, T4, MocaConnectionConditions::isLowStorage- Storage sufficient unchanged (0)
[905.546] VM:CMPOv=3
[905.57] 17T112706, T2, Get client timestamp: null
[905.671] VM:CMPOv=13
[905.687] 17T112706, T4, Device not in low storage state: 0, null
[905.789] VM:CMPOv=13
[905.804] 17T112706, T2, getDeviceSettings from server: 358922041622310__ManageTimeSheet : Thu Feb 01 00:00:00[905.804]  Europe/Dublin 2001
[905.851] VM:CMPOv=6
[905.859] 17T112706, T4, MocaConnectionConditions::isLowStorage- Storage sufficient unchanged (0)
[906.007] VM:CMPOv=19
[906.023] 17T112707, T2, Applog Status - 11:27:06 Queued Settings Request
[906.062] VM:CMPOv=5
[906.085] 17T112707, T4, Attempting Connect.
[906.14] VM:CMPOv=7
[906.156] 17T112707, T2, execute:  objectName='monet:SettingsExchange.dll:SettingsExchange' methodName='GetDev[906.156] iceSettings' param count(false)=2
[906.25] VM:CMPOv=12
[906.257] 17T112707, T4, execute:  objectName='MOInternalMO' methodName='Echo' param count(false)=0
[906.335] VM:CMPOv=10
[906.351] 17T112707, T2, Device not in low storage state: 0, null
[906.406] VM:CMPOv=7
[906.421] 17T112707, T4, execute:  refreshing stale ServerVersionInfo
[906.468] VM:CMPOv=6
[906.578] 17T112707, T2, MocaConnectionConditions::isLowStorage- Storage sufficient unchanged (0)
[906.609] VM:CMPOv=4
[906.632] 17T112708, T4, Starting URL Template discovery
[906.664] VM:CMPOv=4
[906.671] 17T112708, T2, writeToStream parameter: name='sDeviceName' type=0 passtype=1
[906.679] FS: CLEAN(1235 5)
[907.257] VM:CMPOv=75
[907.265] JVM: bklt @907265: timer
[907.265] JVM: bklt[1] @907265: usrIdle 31, usrTime 30, usrAct 1
[907.265] JVM: bklt[1] @907265: chkIdle 46, currTime 31
[907.265] JVM: bklt[1] @907265: enableBacklight 0
[907.265] JVM: bklt[1]: setTimeout 30
[907.273] 17T112708, T4, Testing Relay Server URL Template:/tm/?cid=%cid%
[907.289] VM:CMPOv=2
[907.398] 17T112709, T2, writeToStream parameter: name='dtDeviceTimestamp' type=14 passtype=1
[907.468] VM:CMPOv=2
[907.57] FD Turned Off;
[907.57] 17T112709, T2, MOCA message for server queued. RequestID=1 (monet:SettingsExchange.dll:SettingsExcha[907.57] nge.GetDeviceSettings)
[907.765] 17T112709, T2, Send Client Settings to server
[907.843] 17T112709, T5, MoDataBuffer:getArray()
[907.914] VM:CMPOv=9
[908.062] 17T112709, T2, Get client timestamp: null
[908.125] VM:CMPOv=8
[908.312] 17T112710, T5, MoDataBuffer:getArray(), got ticket.
[908.351] VM:CMPOv=5
[908.453] 17T112710, T2, MocaLibrary: CLIENT_STARTED:
[908.593] VM:CMPOv=14
[908.757] VM:EGLCv=23148
[908.82] 17T112710, T5, parseStream parameter 0
[908.859] VM:CMPOv=5
[908.914] VM:CMPOv=5
[908.929] VM:EGLCv=23456
[909.023] 17T112711, T5, parseStream parameter name='sDeviceName' type=0 passtype=1
[909.031] FS: CLEAN(1236 5)
[910.101] VM:CMPOv=137
[910.117] VM:EGLCv=23720
[910.125] FS: CLEAN(1241 5)
[910.343] 17T112712, T5, parseStream parameter 1
[910.359] VM:CMPOv=2
[910.375] VM:EGLCv=23996
[910.382] 17T112712, T5, parseStream parameter name='dtDeviceTimestamp' type=14 passtype=1
[910.382] VM:FSOMv=1
[910.429] 17T112712, T5, process client queue - processing RequestID=1 (monet:SettingsExchange.dll:SettingsExc[910.429] hange.GetDeviceSettings)
[910.953] JVM: bklt[1] @910953: JBSC on=0
[910.953] JVM: bklt[1] @910953: SC 0, fadeEnd: 910953
[910.953] JVM: bklt[1]: setTimeout 30
[911.46] 17T112713, T4, Testing Relay Server URL Template:/cli/iarelayserver/%cid%/tm
[911.523] VM:CMPOv=8
[911.531] FD Back On
[911.546] FD Turned Off;
[913.046] 17T112715, T4, Testing Relay Server URL Template:/ias_relay_server/client/rs_client.dll/%cid%/tm
[913.07] VM:CMPOv=3
[913.078] FD Back On
[913.085] FD Turned Off;
[914.468] 17T112717, T4, ClientConfig: commit
[914.492] VM:CMPOv=3
[914.5] 17T112717, T4, ClientConfig: notify change: 1305
[914.554] VM:CMPOv=7
[914.57] 17T112717, T4, ClientConfig: notify listeners prop: 1305
[914.632] VM:CMPOv=8
[914.632] JVM: bklt[1] @914601: JBSC on=1
[914.632] JVM: bklt[1] @914601: SC 1, fadeEnd: 914601
[914.632] JVM: bklt @914632: setTimer 30
[914.671] 17T112717, T4, Found good Relay Server URL Template: /ias_relay_server/client/rs_client.dll/%cid%/tm[914.671]
[914.703] VM:CMPOv=4
[914.718] 17T112717, T4, A catastrophic error occurred and MOCA server queue processing is shutting down.  Exc[914.718] eption: net.rim.device.api.system.ControlledAccessException
[914.734] VM:CMPOv=2
[914.804] JVM: bklt[1] @914804: JBSC on=1
[914.804] JVM: bklt[1] @914804: SC 1, fadeEnd: 915054
[914.804] JVM: bklt @914804: setTimer 31
[914.734] VM:CMPOv=2
[914.804] JVM: bklt[1] @914804: JBSC on=1
[914.804] JVM: bklt[1] @914804: SC 1, fadeEnd: 915054
[914.804] JVM: bklt @914804: setTimer 31
[924.71] 17T112727, T1, network - signalLevel - iLevel -70
[924.726] SE13 Locale: 1701726018
[924.734] Signal level only changed - ONS not updated
[945.703] JVM: bklt @945703: timer
[945.703] JVM: bklt[1] @945703: usrIdle 31, usrTime 30, usrAct 1
[945.703] JVM: bklt[1] @945703: chkIdle 30, currTime 31
[945.703] JVM: bklt @945703: setTimer 1
[946.593] JVM: bklt @946593: timer
[946.593] JVM: bklt[1] @946593: usrIdle 32, usrTime 30, usrAct 1
[946.593] JVM: bklt[1] @946593: chkIdle 31, currTime 31
[946.593] JVM: bklt[1] @946593: enableBacklight 0
[946.593] JVM: bklt[1]: setTimeout 30
[950.96] JVM: bklt[1] @950960: JBSC on=0
[950.96] JVM: bklt[1] @950960: SC 0, fadeEnd: 950960
[950.96] JVM: bklt[1]: setTimeout 30
[952.14] JVM: bklt[1] @952140: JBSC on=1
[952.14] JVM: bklt[1] @952140: SC 1, fadeEnd: 952140
[952.14] JVM: bklt @952140: setTimer 30
[952.468] JVM: bklt[1] @952468: JBSC on=1
[952.468] JVM: bklt[1] @952468: SC 1, fadeEnd: 952718
[952.468] JVM: bklt @952468: setTimer 31
[961.226] VM:CMPOv=16
[961.226] VM:ECTTt=16,c=20,p=net_rim_sync_daemon
[961.242] VM:CMPOv=2
[983.414] JVM: bklt @983414: timer
[983.414] JVM: bklt[1] @983414: usrIdle 31, usrTime 30, usrAct 1
[983.414] JVM: bklt[1] @983414: chkIdle 30, currTime 31
[983.414] JVM: bklt @983414: setTimer 1
[984.367] 17T112827, T1, network - signalLevel - iLevel -70
[984.382] VM:CMPOv=2
[984.382] JVM: bklt @984382: timer
[984.382] JVM: bklt[1] @984382: usrIdle 32, usrTime 30, usrAct 1
[984.382] JVM: bklt[1] @984382: chkIdle 31, currTime 31
[984.382] JVM: bklt[1] @984382: enableBacklight 0
[984.382] JVM: bklt[1]: setTimeout 30
[984.39] SE13 Locale: 1701726018
[984.39] Signal level only changed - ONS not updated
[988.726] JVM: bklt[1] @988726: JBSC on=0
[988.726] JVM: bklt[1] @988726: SC 0, fadeEnd: 988726
[988.726] JVM: bklt[1]: setTimeout 30
[1016.5] VM:CMPOv=7
[1016.5] VM:IDLCt=7
[1016.539] VM:CMPOv=2
[1016.593] VM:CMPOv=2
[1030.226] VM:EGLCv=24292
[1030.226] FS: CLEAN(1243 5)
[1030.656] VM:EGLCv=24656
[1030.671] BBSUPAppController:Registration failed..! --- This is form call back of asyncRegisterUser which was failure with UserManagerException : Number: REGISTRATION_FAILED_UNKNOWN_ERROR 70003
[1030.679] 17T113052, T1, network - signalLevel - iLevel -70
[1030.695] SE13 Locale: 1701726018
[1030.703] Signal level only changed - ONS not updated
[1030.75] SE13 Locale: 1701726018
[1030.757] 17T113052, T1, network - signalLevel - iLevel -70
[1030.789] Signal level only changed - ONS not updated

[Former Member]

Hi Hemal,

I belive you have tried after changing the name of your application . And prior to installing the app have you deleted the cods using java loader .

Just another confirmation . have u used erase -f while deleting the cods with java loader? using -f  in the erase command is very important.

Regards,

phaneeshln

[Former Member]

Yes I have used -f option along with erase command. This command  deletes all cods MocaClientLib,  MessagingClientLib, CommonClientLib, sup_json also my application cod restarts my device as well properly.

But I have not change name of the application or project  yet. Do you think that would have an impact? I can try that anyway.

Thanks for your reply.

Regards,

Hemal

[Former Member]

Changing the name can be definetly a solution to the controlled access exception. If that doesn't work then a security wipe is the only option.

Controlled access exception is generated when you are trying to access something you are not authorized to!!!. Some time we see this behavior when the device has been corrupted or so.

The logic behind changing the name is that we store the application related information in many access controlled persistent stores, and how we access the persistent store has got something to do with the name of the application (its our internal security logic) , change both the project name as well as the Application name in the scc. Try with this new set of names.

Please try this and let me know.

And if this doesn't solve the problem then as i said before security wipe is a must.

Regards,

Phaneeshln

[Former Member]

Hi Phaneesh,

Thanks for the helpfull answer and clerfication.

I am changing my project name and module name and try as per your suggestion.

Change app name in SCC is slight problem as this client project but I will try that as well and let you know.

Meanwhile, then as per your suggestion if I try this on BB device not use earlier for this work/project that should work right without Controlled access exception, right?

Thanks again.

Regards,

Hemal

[Former Member]

Hi Hemal,

Yes, If you use a different device on which a 2.1.3 app has never been installed then everything should be fine.

I have a few clarification, on very obvious things which usually any Blackberry developer would have done correctly, just want to be sure we are not missing anything here.

1.When you installed your code signing keys have you installed in your BB eclipse plugin have you installed all the 3 files client -RBB, client - RCR, client -RRT with the same signing password?

2.And have you deployed a productive application on the device by signing it with the same environment (same eclipse) which you are using to sign the 2.1.3 application? And has the productive application worked properly? I am stressing productive application because i am sure these application use controlled access APIs . If any productive application has worked properly then we can, to a good extent, assume that your code signing method is correct. You cannot judge the same by trying to deploy a " hello world" application, as it does not call any controlled access APIs.

Nevertheless, first I am curious to know if things are working for you now or not.

Regards,

Phaneeshln

[Former Member]

Hi Phanessh,

Thanks for reply.

Clerification for both the points you have mentioned:

I have RBB, RCR, RRT sign key from long period. Our signing process is well in place and we have used same process to deployed Blackberry apps in Appworld as well.

But to 100% sure, before replying to this I tried once more with BB Persistance store API sample code. I modified it slightly and signd it and deployed on device. It came with prompt for trusted app and was able to acces Persistance object.

Also this SUP 213 app is also signed with same API.

I do understand that ControlledAccess exception will come only if we do not have permisson to access it. But one point came to my mind is that this error comes from MocaServer i.e. MocaClientAPI. I have not signed this llib/modules. I have just used it as it is as supplied by SUP MobileSDK213. Do I need to sign it sepretely?

I am still yet to try out app with changed project name and changed app name as I had to give away device for demo. So I will try this today and let you know soon.

[Former Member]

Hi Hemal,

Then your there is no problem with the way you are signing the application. We can certainly rule out code signing issue.

You need not sign the following jars, as you already have the corresponding cods of the same-

MocaClientLib.jar MessagingClientLib.jar CommonClientLib.cod sup_json.jar

Just include the above mentioned jars in your build path and don't export it ( exporting is technically not possible as well ) . And the other jars which you are using has to be also put in the build path and exported as well. When you build your project you get Yourapp.cod

So finally when you load the application you have to load the following.

Yourapp.cod MocaClientLib.cod MessagingClientLib.cod CommonClientLib.cod sup_json.cod .

I belive you are already doing all this things properly.

I will be waiting to hear from you.

Regards,

Phaneeshln

[Former Member]

Hi Phaneesh,

Thanks very much for the reply.

As you rightly pointed ( and also from SUP Odata SDK Document) I have included  MocaClientLib.jar MessagingClientLib.jar CommonClientLib.cod sup_json.jar in build path but have not selected them for export.

Also I deploy above monetioned cod files using command line batch file ( similar or almost same as you had mentioned in earlier post) and then I use eclipse debug configuration to put app on device and then run the app.

I will put forward my results soon.

Regards,

Hemal

[Former Member]

Hi,

   In Sybase control Center delete the previous existing users and remove the application(all the loaded cod files) from device.Then reload application on to the device again and try registration.

Thanks,

Srikanth M