SAP Knowledge Base Article - Preview

2305884 - Invalid Authentication error when attempting to flush an offline OData client after the device is inactive

Symptom

  • Receiving "invalid authentication" error when attempting to flush the offline OData store. Flushing a 2nd or 3rd time will successfully create data.
  • The use case is that the device is idle for awhile with no activity.
  • Client log shows:
    04-14 08:59:12.494: E/OfflineManager(20178): (KrollRuntimeThread) [767,250416] Error sync flushing queued requests!
    04-14 08:59:12.494: E/OfflineManager(20178): com.sap.smp.client.odata.exception.ODataNetworkException: Unknown network error occured
    04-14 08:59:12.494: E/OfflineManager(20178): at com.sap.smp.client.odata.offline.ODataOfflineStore.flushQueuedRequests(ODataOfflineStore.java:905)
    04-14 08:59:12.494: E/OfflineManager(20178): at com.propelics.sapsmpodata.offline.OfflineManager.flush(OfflineManager.java:325)
    04-14 08:59:12.494: E/OfflineManager(20178): at com.propelics.sapsmpodata.ODataOfflineStoreProxy.flush(ODataOfflineStoreProxy.java:166)
    04-14 08:59:12.494: E/OfflineManager(20178): at org.appcelerator.kroll.runtime.v8.V8Object.nativeFireEvent(Native Method)
    04-14 08:59:12.494: E/OfflineManager(20178): at org.appcelerator.kroll.runtime.v8.V8Object.fireEvent(V8Object.java:62)
    04-14 08:59:12.494: E/OfflineManager(20178): at org.appcelerator.kroll.KrollProxy.doFireEvent(KrollProxy.java:918)
    04-14 08:59:12.494: E/OfflineManager(20178): at org.appcelerator.kroll.KrollProxy.handleMessage(KrollProxy.java:1141)
    04-14 08:59:12.494: E/OfflineManager(20178): at org.appcelerator.titanium.proxy.TiViewProxy.handleMessage(TiViewProxy.java:356)
    04-14 08:59:12.494: E/OfflineManager(20178): at android.os.Handler.dispatchMessage(Handler.java:95)
    04-14 08:59:12.494: E/OfflineManager(20178): at android.os.Looper.loop(Looper.java:137)
    04-14 08:59:12.494: E/OfflineManager(20178): at org.appcelerator.kroll.KrollRuntime$KrollRuntimeThread.run(KrollRuntime.java:118)
    04-14 08:59:12.494: E/OfflineManager(20178): Caused by: com.sap.smp.client.odata.offline.ODataOfflineException: [-10207] Communication with the server failed due to invalid authentication
    04-14 08:59:12.494: E/OfflineManager(20178): ... 11 more
  • Server log shows:
    2016 04 14 08:49:46#0-400#ERROR#com.sap.odata.offline.util.NativeLogger###Thread-252####4599e27a-1cf4-46c1-a6ba-000000000000#####<115> [-10279] Connection was dropped due to lack of network activity |
    2016 04 14 09:04:44#0-400#ERROR#com.sap.odata.offline.util.NativeLogger###Thread-252####4599e27a-1cf4-46c1-a6ba-000000000000#####<143> [-10279] Connection was dropped due to lack of network activity |


Read more...

Environment

SMP 3.0 SP 10 PL07
Offline OData client

Product

SAP Mobile Platform 3.0

Keywords

Session  Timeout OData offline SMP , KBA , MOB-SDK-OOD , SAP Mobile SDK Offline OData Client , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP ONE Support launchpad (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.