Siebel Service Handheld Guide > Working with Siebel Handheld Applications >

Troubleshooting Synchronization with the Siebel Handheld Application Client

This topic lists potential error messages that are associated with synchronization. In addition, this topic helps to understand transaction errors.

General Synchronization Errors

There are a number of different errors that can occur when synchronization does not complete successfully, for example:

  • Faulty wire connection
  • Server crash
  • Insufficient memory
  • Login error
  • Where Microsoft (MS) Embedded Visual Basis (EVB) is installed for PPC 2003 on a handheld device, MS EVB replaces any existing MS DLLS in the \Windows directory, resulting in the following error upon (second and subsequent) handheld synchronizations:

         The version of resource DLL MSDAEREN.DLL is not valid.

    To fix this problem, copy msdadc.dll, msdaer.dll, and msdaeren.dll from \Program Files\Siebel Handheld directory to the \Windows directory.

When these errors occur, the user must exit Siebel Handheld application synchronization and launch the application again.

NOTE:  When you restart Siebel Handheld application synchronization, you might see an error message indicating that another instance of syncmanager.exe is running. You are asked whether you want to terminate the first instance or not, and you must choose Yes.

Transaction Conflicts

Transaction conflicts are minimized when customers adhere to the standard configuration practices outlined in this document. However, even when proper configuration practices are followed, conflicts can occur for a variety of reasons. For example, if a field value is updated on both the Siebel Handheld Application Client and the Siebel Server between synchronization events, a transaction update conflict occurs. In this instance, the user is presented with an error dialog after synchronization has completed.

A transaction consists of one or more smaller transactions called mini-transactions. For example, if you update several fields in a record, the update to the record counts as a single transaction, and each update to a field is a mini-transaction. Individual fields are skipped when update conflicts occur. Changes to any field that has been updated on the server since the last synchronization (perhaps by another Siebel Handheld application user) are discarded (but logged and returned as errors to the user). All non-conflicting fields normally are updated. Except for field-level conflicts, which are skipped when they occur, a transaction is applied in its entirety, and at this point will either succeed or fail in its entirety.

Siebel Service Handheld Guide Copyright © 2013, Oracle and/or its affiliates. All rights reserved. Legal Notices.