Symptom
After a device has been registered successfully and is online in Sybase Control Center (SCC) the subscription
is pending and the connection is shown as "failed" on the device.
The MOCA client log contains http 404 and 503 errors.
Log sample:
01T161556, T4, HttpCommMgr: Conn did receive response, response status = 404
01T161556, T4, HttpCommMgr: stopSendWithStatus: HTTP error 404
01T161556, T4, HttpCommMgr: readResponse failed
01T161556, T4, ReadTMHeader failed - error -9
01T161556, T4, ClientQueue - failed to connect.
01T161556, T4, 515, 0 Error retrieving public key from server
01T161556, T4, Disconnected D2S connection
01T161621, T3, Error connecting to server.
01T161621, T3, 503, 0 Connect failed.
01T161621, T3, App Log - Error: 503 Detail: Could not connect to server.
01T161621, T3, HttpCommMgr: Connection failed, error: Could not connect to the server., code = -1004
Read more...
Environment
- Sybase Unwired Platform (SUP) 2.1.x
- SAP Mobile Platform (SMP) 2.3.x
- Sybase Control Center/SAP Control Center (SCC)
- 2 Relay Server behind a Load Balancer
- SAP Mobile Sales 2.0.9
Product
Keywords
RelayServer Relay rsoe 404 503 MobileSales LoadBalancer , KBA , loadbalancer , scc , registration , subscription , moca , MOB-SUP-SCC , Sybase Control Center Administration , Problem
About this page
This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).Search for additional results
Visit SAP Support Portal's SAP Notes and KBA Search.