cancel
Showing results for 
Search instead for 
Did you mean: 

REX 3.1 apps unable to connect CRM thru SMP 2.2

Former Member
0 Kudos

Hi Team,

We have a  Requirment - Access CRM applications thru REX apps.

1) We have CRM, SMP2.2 and Relay Server in our landscape;

2) Installed REX 3.1 on Adroid device and access the REX application with below configuration setup -
Settings:
Server: IP Address

FormID: XXXAICRSMBS
UsreID: DemoRex2
Activation Code: 123
Port: 80
Suffix:
Secure Connection: OFF

3) Smart device was connected and I can see it is online in SCC(SMP), that means the request was successfully passed thru Relay and reached to SCC.

4) REX application asked me to enter CRM system credentials. Entered CRM system Credentials.

We go the below error -

com.sybase.persistence.SynchronizeException:
com.ianywhere.ultralitejni12.implementation.JniException: UltraLiteJ
Error[-1305]: MobiLink communication error -- code: 57, parameter:
BG6SAP1008, system code: 0Details:
StreamErrorCode = 57
StreamErrorMessage = BG6SAP1008

at
com.sybase.sup.client.persistence.RbsDatabaseDelegate.internalSynchronize(RbsDatabaseDelegate.java:809)
at
com.sybase.sup.client.persistence.RbsDatabaseDelegate.synchronizeWithCallback(RbsDatabaseDelegate.java:419)
at
com.sybase.sup.client.persistence.RbsDatabaseDelegate.synchronize
(RbsDatabaseDelegate.java:136)
at
com.sybase.sup.client.persistence.RbsDatabaseDelegate.onlineLogin
(RbsDatabaseDelegate.java:1067)
at SAPRetailExAND.SAPRetailExANDDB.onlineLogin
(SAPRetailExANDDB.java:450)
at com.sap.abo.ConnectionManager.authenticateUser
(ConnectionManager.java:261)
at com.sap.abo.ConnectionManager.loginToSynchronize
(ConnectionManager.java:202)
at
com.sap.rex.ui.onboarding.AppLoginActivity$LoginToSyncWithServer.doInBackground(AppLoginActivity.java:617)
at
com.sap.rex.ui.onboarding.AppLoginActivity$LoginToSyncWithServer.doInBackground(AppLoginActivity.java:534)
at android.os.AsyncTask$2.call(AsyncTask.java:287)
at java.util.concurrent.FutureTask.run(FutureTask.java:234)
at android.os.AsyncTask$SerialExecutor$1.run(AsyncTask.java:230)
at java.util.concurrent.ThreadPoolExecutor.runWorker
(ThreadPoolExecutor.java:1080)
at java.util.concurrent.ThreadPoolExecutor$Worker.run
(ThreadPoolExecutor.java:573)
at java.lang.Thread.run(Thread.java:838)
Caused by: com.ianywhere.ultralitejni12.implementation.JniException:
UltraLiteJ Error[-1305]: MobiLink communication error -- code: 57,
parameter: BG6SAP1008, system code: 0
at
com.ianywhere.ultralitejni12.implementation.JniConnection.ulcSynchronize(Native Method)
at
com.ianywhere.ultralitejni12.implementation.JniConnection.synchronize
(Unknown Source)
at
com.sybase.sup.client.persistence.RbsDatabaseDelegate.internalSynchronize(RbsDatabaseDelegate.java:709)
... 14 more       
Steps for Reconstruction 

We have verifed the SCC known issues for MobiLink communication error -- code: 57 --> it is saying about Hostname setup . we did it but no luck.

Thanks,

Nagaraju

Accepted Solutions (0)

Answers (3)

Answers (3)

nageshcaparthy
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi Siva,

MobiLink Error clearly says that the Server is not reachable. I believe  BG6SAP1008 is your SUP CRM server.


Can you please check and confirm if its your CRM server name.


You can more information on MobiLink in the following link :


http://infocenter.sybase.com/help/index.jsp?topic=/com.sybase.help.sqlanywhere.12.0.1/mlserver/runni...


FYI, Rex 3.1 works only with SUP 2.2 SP02 or SMP 3.0.


Regards,


Nagesh

midhun_vp
Active Contributor
0 Kudos

It is referring to an error in the module BG6SAP1008.

"

UltraLiteJ Error[-1305]: MobiLink communication error -- code: 57,

parameter: BG6SAP1008,  "


So check whether you installed the add ons related to the app properly.


- Midhun VP

Jitendra_Kansal
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi Siva,

can you quickly check if connection in SCC is pinged successfully for backend system

domains>default>packages>connections

select CRM backend system and go to its properties.

when you click on Test Connection, is this ping successful?

Regards,

Jitendra

Former Member
0 Kudos

Hi Jitendra,

yes, Ping test was successful.

Thanks,

Naga