## 7.1 Troubleshooting in Analysis
You can run Analysis in different troubleshooting modes. After the first Analysis installation, no troubleshooting mode is active.
You can specify the troubleshooting options in the Analysis backstage area: Select File Analysis Troubleshoot &lt;troubleshooting mode&gt; .
The following troubleshooting modes are available:
- Support Mode
In the Support Mode, the system stores exceptions, error messages and traces. BW Server Tracing for the Analysis plug-in is also active.
## · Profiling Mode
In the Profiling Mode, client profiling is active. BW Server Tracing and Workbook Profiling for the Analysis plug-in are active. The system also stores exceptions and error messages.
- Advanced Mode
You can specify the options for troubleshooting in the Advanced Support and Profiling Mode dialog. These tabs are available in the dialog: General (for all plug-ins) and Analysis (for the Analysis plug-in). The options on the three tabs are described later in this chapter.
The Support Mode and the Profiling Mode can be active at the same time.
You can check the statistics under File Analysis Troubleshoot Show Profiling Statistics or Show Workbook Profiling Statistics .
Note that writing profiling statistics may influence the performance. You can select Deactivate in the Troubleshoot area to deactivate all troubleshooting modes if they are no longer needed.
## Advanced Mode: General Tab
## Log Severity
The Log Severity defines the amount of log and trace information that is stored. In this area, you can select:
## · Support
By default, the system stores exceptions and error messages. If the check box Support is selected, the system stores exceptions, error messages and traces.
The information is stored as .glf files under %temp%\SAP\COF .
The system can also store messages and traces that are defined in the log.config file under %appdata% \SAP\COF . For more information, contact your system administrator.
- Profiling
To activate the Analysis client profiling, select the Profiling check box. If the setting is activated, Analysis will capture every interaction.
You can choose between Standard Profiling and Modified Profiling .
You can also activate the client profiling with the file system setting clientProfiling .
In the Client Profiling Statistics dialog, the captured interactions are displayed as steps in a tree view and you can navigate to each interaction. You can see the overall processing time per step (in ms), the time the user spent in dialogs, the number of RFC calls per step and the time that was spent for RFC. In section Update UI, you can see if a navigation step has caused (unexpected) RFC calls.
At the bottom of the Client Profiling Statistics dialog, you find a summary containing the time that was used on client side for processing (in ms), the number of RFC calls (count) and the time that was used for that (in ms) and the time the user spent in dialogs (in ms).
## Advanced Mode: Analysis Tab
## Enable BW Server Tracing
To activate the SAP BW trace tool environment, select the Enable BW Server Tracing check box.
You can also activate the BW server tracing with the file system setting AbapTrace in the Ao\_app.config file.
The trace tool environment (transaction code RSTT in the connected BW system) has special tools to log and play back traces and process automatic regression tests.
For more information about the trace tool environment, see the SAP BW documentation on the SAP Help Portal.
## Enable Workbook Profiling
To activate the SAP BW query runtime statistics, select the Enable Workbook Profiling check box.
You can also activate the workbook profiling with the file system setting Profiling in the Ao\_app.config file.
Using the query runtime statistics, you can find out how much time it takes to execute certain user actions in Analysis and the BW analytic engine. The system records the performance-critical parts of the processing (statistics events). It calculates the net times by calculating the runtime of an event using the difference between the start and end times (minus the times for other events called from within the event).
For more information about the query runtime statistics, see section Query runtime statistics in the Analysis Administrator guide.
## Enable NCO Tracing
This setting may be used for SAP error handling.
Analysis uses the .Net connector (NCO) for calling ABAP RFCs from client. NCO supports the logging of RFC traces. You can activate the tracing by selecting Enable NCO Tracing and choosing the desired level (usually 3).
Note that you need to restart Analysis after changing the trace level to apply the new level.
If you now work with Analysis, log files will be created in the %temp% folder of windows. There you can find a dev\_nco\_rfc.log file and several files "nco\_rfc\_XXXX\_Y.trc". Additionally, there are the Analysis log files of type .glf, for example, AO\_Trace\_* .glf. Y ou can zip all of them to attach them to the message.
## Enable CPIC Tracing
This setting may be used for SAP error handling. Common Programming Interface - Communication (CPIC) is the communication layer under JRFC (or JCo).
You can activate the tracing by selecting Enable CPIC Tracing and choosing the desired level. You can choose a trace level from 1 to 3, where 3 is the highest and most detailed level of tracing.
Note that you need to restart Analysis after changing the trace level to apply the new level.
If you now work with Analysis, log files will be created in the %temp% folder of windows. There you can find a nco\_cpic\_XXX.trc file that you can attach to the message.
##  Note
If you want to gather the log and trace information for a special issue, for example, to be used for SAP error handling, please follow these steps:
1. Make sure that only one Excel instance is running.
2. Enable NCO Level 3 and CPIC Level 3.
3. Close the Excel instance and make sure that no Excel instance is running (Windows Task-Manager).
4. Delete all files from the Analysis log directory (%temp%\SAP\COF).
5. Restart Analysis and reproduce the issue. The log files (* .glf, * .log, * .trc) are stored in the log directory, and you can attach them to a ticket.
## Show Suppressed Messages
Select this check box if you want the suppressed messages to be shown.