Siebel Medical Handheld Guide > Troubleshooting > Siebel Handheld Application Log Files >

Handheld Device Log

The siebel_ log.txt file is found in the /Program Files/Siebel Handheld directory on the handheld device. It is controlled by reg key DefaultLogLevel, with values 0-4. For more information about DefaultLogLevel, see Siebel Handheld Application setup.ini Parameters.

The default value of the reg key during installation is 2. This file logs all of the following:

• Database objects that were imported during synchronization.
• All SQL statements generated by the application. You must set a parameter in the setup.ini file to turn this log on. DefaultLogLevel=3 and 4 will log SQL statements to the device log.

  For more information about setting DefaultLogLevel, see Siebel Handheld Application setup.ini Parameters.

• All system error messages. You must set a parameter in the setup.ini file to turn this log on. DefaultLogLevel=4 will give the most detailed log with debug info.

  For more information about setting DefaultLogLevel, see Siebel Handheld Application setup.ini Parameters.

• All of the messages displayed on the Sync Manager dialog box as well as some basic information about synchronization, such as data source and connect string. You can set the logging level for this file using the DefaultLogLevel parameter in the setup.ini file.

Logging Synchronization Errors for Siebel Handheld Applications

Synchronization for a Siebel Handheld application logs all the strings that the user sees in the synchronization message window, as well as many informational messages that do not get displayed in the UI. These informational messages are used to help track down where an error occurred. Synchronization for a Siebel Handheld application determines which messages get logged based on a value stored in the registry under the key DefaultLogLevel. The values range from 0 to 4, where 0 logs all error messages and strings that the user sees, and 4 logs all data that is sent and received during synchronization.

If synchronization for your Siebel Handheld application fails, check the siebel_log.txt file immediately after the failure. If you need more detail, increase the logging level of DefaultLogLevel and run synchronization for the Siebel Handheld application again. For more information about changing DefaultLogLevel, see Siebel Handheld Application setup.ini Parameters.

You can determine when and where an error occurs during synchronization of your Siebel Handheld application by referring to siebel_log.txt and the Sync Object Manager log.

The device log, siebel_log.txt, shows the last HTTP command that was sent to server, for example, ExecuteLogin, Init, ProcessTransactionEx, ExtractDB, and so on. The Sync Object Manager log receives the request and invokes the corresponding method.

For example, in the device log (siebel_log.txt), the following code indicates that the device is sending an initialization request to the Siebel Server:

INFO 0x6F46107E 03/30/2005 16:58:27 http ://PPP_PEER:2323/medicalce/start.swe?SWEExtSource=siebelpda&SWEExtCmd=Init&PatchLevel=7.7.2.2PDA%5b18356_1] 8.471262E-309NU&SyncFormat=CE0&SyncNodeId=&TimeStamp=1112230707

INFO 0x6F46107E 03/30/2005 16:59:20 <Init ReturnCode="OK" Complete="100">

The server log (Sync Object Manager log, that is, CompNameObjMgr_enu_xxxxx.log), shows that the Init request is received by the server and the Init method is invoked:

ObjMgrBusServiceLog InvokeMethod 4 0 2005-03-23 10:45:27 Begin: Business Service 'Handheld Synchronization' invoke method: 'Init' at 10c2bc68

HandheldSyncLog Debug 5 0 2005-03-23 10:45:27 Request Init received

(Where CompName is the server component name of the synchronization for the specific Siebel Handheld application.)

In addition to the device log, check the CompSync log in laptop (for Companion Synchronization) or SalesCEObjMgr_enu_xxxxx.log in Siebel Server (for DSS). For more information about changing logging levels, see Configuring Logging Levels for Direct Server Synchronization and Configuring Logging Levels for Companion Synchronization.