Troubleshoot Synchronization

Provides troubleshooting information for problems that can occur with embedded synchronization components, such as the cache database (CDB), the remote device database, or the synchronization server.

• Synchronization Failed while Downloading Data
  Problem: You receive a synchronization failure message while downloading data.
• Multi-threaded Delete Failures Not Logged
  Problem: If you have multiple requests from different devices trying to delete the same record at the same time, and a thread successfully deletes the record, but a second thread fails because that record is now removed from the server, no failure message appears in the SAP Mobile Server log.
• Device Synchronization Returns no Data
  Problem: Improper syntax in generated code calls causes device synchronization to return no data.
• Errors When Reusing Primary Keys
  Problem: Reusing an enterprise information system (EIS) primary key generates an error. If you insert a record that has the same primary key that has been deleted, the SAP Mobile Server fails to retrieve the inserted data.
• SAP Mobile Server Reports Exception or Fails During Synchronization
  Problem: Sometimes when assigning a personalization key that uses a binary datatype to an operation argument or load argument with BIGBINARY type, the server throws exceptions during synchronization.
• MOBILINK: HTTP_UNKNOWN_SESSION Errors During Synchronization
  Problem: An application randomly gets a MOBILINK: HTTP_UNKNOWN_SESSION error during synchronization when using an Apache reverse proxy to connect the device to SAP Mobile Server.