Symptom
- The application is successfully registered in the SMP server.
- The next step of creating the Offline store on the client device fails.
- The SMP server log shows:
2017 09 14 11:40:58#0-400#WARN#com.sap.odata.offline.scripts.ODataSyncHandler###Thread-346##38a91a50-ee64-4009-a53f-c5f57b48d401#com.cintas.crmdynamics#0a9d0a98-f5cf-488f-9ad6-8a4cbad54df9#RequestResponse#200##Delta download for an Offline OData client failed. |
2017 09 14 11:40:58#0-400#WARN#com.sap.odata.offline.scripts.ODataSyncHandler###Thread-346##38a91a50-ee64-4009-a53f-c5f57b48d401#com.xxxxxxx.xxxxxxx#0a9d0a98-f5cf-488f-9ad6-8a4cbad54df9#RequestResponse#200##
[-100099] An error occurred while parsing the metadata document for OData service with service root "http://xxxxxxx.xx.xxxxx.com:8000/com.xxxxxx.xxxxxxxx/".
Error caused by: Missing message for key 'org.apache.olingo.odata2.api.ep.EntityProviderException.INVALID_NAMESPACE2'!
Read more...
Environment
-
SAP Mobile Platform (SMP) SDK 3.0 SP15
- SMP Data Runtime Server 3.0 SP13
- Windows 10 phone
- OData Server running version 4.
Product
SAP Mobile Platform 3.0
Keywords
OData Version 4 Offline invalid tag/namespace , KBA , MOB-ONP-OOD , SAP Mobile On Premise Offline OData Server , 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.