Show TOC Entering content frame

This graphic is explained in the accompanying text Trace Options Locate the document in its SAP Library structure

The following table explains the trace options that you must select to generate the required trace files:

This graphic is explained in the accompanying text

If you encounter an error while saving data through the mobile client application, you must enable the Drvadodb and RFC trace options. However, if you encounter an error during data transfer between the mobile client and the CRM server, you must enable all the trace options.

Option

Description

Drvadodb Trace

Sets the values for the two registry entries, trc_level and trc_timeanddate under the path HKEY_LOCAL_MACHINE\SOFTWARE\SAP\MSA\RFC\DRVADODB.

·        trc_level

There are only two values for this entry, 0 and >=2. By default, trc_level is set to 0 and the DRVADODB.dll logs only information about the parameters in the registry into the TRC.txt file.

However, when you select this option, trc_level is set to 3 and the DRVADODB.dll logs details about the functions that are executed into the TRC.txt file. From this file, the SAP support team identifies the function that caused the error.

·        trc_timeanddate

There are only two values for this entry, 0 and 1. By default, trc_timeanddate is set to 0 and the DRVADODB.dll does not log the date and timestamp of each function into the TRC.txt file.

However, when you select this option, trc_timeanddate is set to 1 and the DRVADODB.dll logs the date and timestamp of each function that is executed into the TRC.txt file.

This graphic is explained in the accompanying text

After the TRC.txt file is generated, you must deselect this option to minimize the impact on performance when you access the user database.

RFC Trace

Sets the values for the three registry entries, trace, Home, and TableDump under the path HKEY_LOCAL_MACHINE\SOFTWARE\SAP\MTS\options.

·        Trace

There are only two values for this entry, 0 and 2. By default, trace is set to 0 and the LIBRFC32.dll does not create the rfc<number>_<number>.trc trace file.

However, when you select this option, trace is set to 2 and the LIBRFC32.dll creates the:

¡        rfc<number>_<number>.trc file that contains details about the conversion between the application data format and RFC data format

¡        dev_rfc.trc that contains a summary of errors that are logged in the rfc<number>_<number>.trc file

This graphic is explained in the accompanying text

In the rfc<number>_<number>.trc file, the <number> indicates a four digit number that is randomly generated during runtime.

·        Home

When you select this option, the rfc<number>_<number>.trc file is created in the C:\Temp folder. You can specify a different path for this file in the registry.

·        TableDump

There are only two tracing values for this entry, 0 and 1. By default, TableDump is set to 0 and the LIBRFC32.dll does not dump any data into the rfc<number>_<number>.trc file.

However, when you select this option, TableDump is set to 1 and the LIBRFC32.dll dumps the following data into the rfc<number>_<number>.trc file:

¡        Data persisted by DRVADODB.dll when you perform a save operation through the mobile client application.

¡        Data retrieved by the DRVADODB.dll from the user database when you import data by using ConnTrans or Client Console.

SQL Trace

Enables the Microsoft SQL Profiler and creates the SQLTrace.trc file that contains details about database related operations, such as SELECT, INSERT, UPDATE, and DELETE.

TL Trace

Sets the values for the two registry entries, RCV_TRACE and TL_TRACE_DIR under the path HKEY_LOCAL_MACHINE\SOFTWARE\SAP\MSA\MW\TL.

·        RCV_TRACE

There are only two values for this entry, 0 and 1. By default, RCV_TRACE is set to 0 and the TLX.dll does not create the TL_Trace.dat file.

However, when you select this option, RCV_TRACE is set to 1 and the TLX.dll creates the TL_Trace.dat file that contains details about the data processing phase, such as:

¡        The BDoc type associated with a BDoc message.

¡        The message types that are received from the CRM server.

In addition, if there is an error during data import, the TLX.dll creates the TL_Error.dat file that contains recordset information pertaining to a message.

·        TL_TRACE_DIR

When you select this option, the TL_Trace.dat file is created in the C:\Temp folder. You can specify a different path for this file in the registry.

Transfer Service Trace

Sets the trace level for the registry entry CurrentTracelevel under the path HKEY_LOCAL_MACHINE\SOFTWARE\SAP\MSA\TransferService\CurrentConfiguration.

CurrentTracelevel

There are only two values for this entry, 2 and 3. By default, the CurrentTracelevel is set to 2 and the QMTCLIENT.dll logs details about the data transfer process into the TransferService.log file that is present in the mobile client during data exchange between the CRM server and mobile client. This file is created in the default windows temporary folder.

The TransferService.log file contains details about the data transfer process, such as:

·        The number of messages sent to the CRM server from the outbound queue of the mobile client.

·        The number of messages received from the CRM server and persisted in the inbound queue of the mobile client.

·        The estimated and actual time taken to transfer these messages.

In addition, the file contains information about the errors that may occur during the data transfer process. The errors that commonly occur are network related, such as:

·        Incorrect configuration of destinations for the Communication Station and the CRM server

·        The failure of the link between the Communication Station and mobile client or Communication Station and CRM server during the data transfer process.

However, when you select this option, the CurrentTracelevel is set to 3. In such a case, apart from the above mentioned details, the QMTCLIENT.dll dumps the following into the TransferService.log file:

·        The messages sent from the outbound queue of the mobile client.

·        The messages received from the CRM server and persisted in the inbound queue of the mobile client.

ConnTrans Trace

Enables the logging of runtime information associated with the execution of ConnTrans into the ConnTrans_log.xml file. For information on the contents of the log file, see The ConnTrans Log File.

ConnTrans Statistics Trace

Enables the logging of transfer statistics into the StatisticsLog.xml file that captures statistics such as time taken to process the different stages (Send, Receive, and Import) of the data synchronization process. The system administrator can use this file to analyze and benchmark data related to the performance of ConnTrans.

 

Leaving content frame