SAP Knowledge Base Article - Preview

2529211 - With bad network and/or slow backend reaction time the synchronization fails with offline OData client

Symptom

When an offline OData application goes online and tries to sync, then fails because of bad network and/or slow response time, and the user retries the sync, it will restart the process instead of continuing the sync from where it had to stop.

Log shows:

An unexpected problem occured while communicating with back end <BackendURL>
WARN Delta download for an Offline OData client failed.
INFO Finished a delta download for an Offline OData client.
WARN An unexpected problem occured while communicating with back end <BackendURL>
WARN An unexpected problem occured while communicating with back end <BackendURL>
WARN An unexpected problem occured while communicating with back end <BackendURL>

OR

The application is still not able to sync and it throws error:

[-10180] A communication error has occured. Reason: -1305(MOBILINK_COMMUNICATIONS_ERROR) error 313 (The operation couldn't becompleted. Network is down) (system code50).


Read more...

Environment

 SAP Mobile Platform (SMP) SDK 3.0

Product

SAP Mobile Platform SDK 3.0

Keywords

mobilink, offline, odata, store, create, creation, network, performance, slow, sync, syncing, synchroinzation, communication, fail, failed, failure, fails, server, back end, back-end , 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.