cancel
Showing results for 
Search instead for 
Did you mean: 

Device Registration through Relay Server Android SUP 2.1.3

Former Member
0 Kudos

Hi,
I am trying to connect mobile device to SUP through Relay Server. But it always ends up with

10-03 17:45:52.874: I/MocaLog(1394): 03T174552, T3, Did NOT find good Relay Server URL Template

10-03 17:45:52.894: I/MocaLog(1394): 03T174552, T3, MoObject.execute -- caught TM exception - 15:com.sybase.messaging.traveler.TmException: Could not connect to server. Verify Relay Server URL Template

I followed this blog http://scn.sap.com/community/mobile/blog/2012/05/02/sup-212-native-android-mbo-non-doe-based-approac... .

Following are the snippets.

GeneratedDB

is there anything wrong?

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi Anand,

Did u find any solution for this issue because i am facing the same issue while connecting to relay

0 Kudos

Hi Anand,

I think your relay server suffix is not /ias_relay_server/client/rs_client.dll is not correct, please check and set correct URL suffix to resolve the issue.

/ias_relay_server/client/rs_client.dll is the suffix when you configure relay server on Windows IIS with default install path. It looks like on your relay server this is different.

To check, you can try to browse http://<relay>:<port>/ias_relay_server/client/rs_client.dll and i think it will not work.

Regards,

Abhishek Joshi

Former Member
0 Kudos

Hi Abhishek,
Thanks for your response.
Now I got another error. Log report,

10-04 10:35:59.106: I/MocaLog(568): 04T103559, T3, Found good Relay Server URL Template: /ias_relay_server/client/rs_client.dll/%cid%/tm

10-04 10:35:59.116: W/System.err(568): Bad file number

10-04 10:35:59.126: I/MocaLog(568): 04T103559, T3, Sending getkeys request

10-04 10:35:59.138: W/System.err(568): Bad file number

10-04 10:35:59.146: I/MocaLog(568): 04T103559, T3, Cookies - setRequest:

10-04 10:35:59.156: W/System.err(568): Bad file number

10-04 10:35:59.816: I/MocaLog(568): 04T103559, T3, error retrieving ServerVersionInfo: readByte: unexpected EOF

10-04 10:35:59.836: W/System.err(568): Bad file number

10-04 10:35:59.846: I/MocaLog(568): 04T103559, T3, current ServerVersionInfo: null,11

10-04 10:35:59.846: W/System.err(568): Bad file number

10-04 10:35:59.856: I/MocaLog(568): 04T103559, T3, tm uri:  'tm://mo/rmi?cid=farmMBS.msg&devid=Simulator5aa88b78-54e6-44a1-aef5-1fb1226f80ad__MySampleProject_WWF&devtype=android&connid=1&valcode=123'

10-04 10:35:59.866: W/System.err(568): Bad file number

10-04 10:35:59.876: I/MocaLog(568): 04T103559, T3, Sending getkeys request

10-04 10:35:59.876: W/System.err(568): Bad file number

10-04 10:35:59.896: I/MocaLog(568): 04T103559, T3, Cookies - setRequest:

10-04 10:35:59.896: W/System.err(568): Bad file number

10-04 10:36:00.056: D/dalvikvm(568): GC_FOR_MALLOC freed 617K, 56% free 3429K/7687K, external 3491K/4696K, paused 75ms

10-04 10:36:00.286: I/MocaLog(568): 04T103600, T3, MoObject.execute -- caught TM exception - 7:com.sybase.messaging.traveler.TmException: readByte: unexpected EOF

0 Kudos

Hi Anand,

Looks like file size is big enough. Could you please try with small size first? Once it works then you can try to increase the TIMEOUT for the big one.

Regards,

Abhishek Joshi