B04 - trace logs being generated on all client PCs

[former_member272336]

Hi,

All users using bi launchpad to view webi reports are seing trace logs created on the client PC.

Understand would see trace logs on servers but users reporting seeing tracelogs on their desktop PCs.

Using BO4 SP6.

What causes this?

We want to stop client PCs being filled up with trace logs.

I.E 8 mainly but other browsers used e.g Firefox all supported - client PC operating system Windows XP Professional 2002 Service Pack 3

All supportde.

Thanks

Philip

[former_member190781 · Accepted solution]

Hi Philip,

Please go through the KB article below.

1866196 - TraceLog_*_trace.glf created on Desktop after upgrading to SP06

Hope it answers your query.

Regards,

Sohel

[former_member272336 · Accepted solution]

Hi Sohel,

Thanks for reply - yes confirms a bug.

Thanks again.

Philip

[Former Member]

The behavior seems to be a bit wierd here, as you mentioned that issue occurs when users are performing activty in BO web application at client PCs.

Identify whether the end users facing issue with traces are developers and using client tools in the same.

The issue would have come up due to the trace WebIRichClient_trace.ini file being applied simultaneously at all client end created by sys admin using scripts. To stop this trace; ensure that in the .ini file tracing is set to false.

Check whether new traces are still getting created.

If not you can proceed to remove these files later.

[former_member272336]

Hi,

no webirichclient_trace.ini set up on these machines.

Thanks

[Former Member]

Hi

In addition to Nikhil's questions

Please check the placeholders in AdaptiveJobServers>Properties.

Also check the bo_trace.ini file in path

<BO Installation folder>\SAP BusinessObjects Enterprise XI 4.0\conf ----------------------------------------------------------------------------------------------------

As per SAP Note "1586166 - How to enable tracing for BI4.0 client applications"

There are two ways of tracing the BI client applications listed in the Environment section – select which ever suits you better:

Trace configuration file

Environment variable

For both scenarios a trace configuration file is required, the difference is only in the file name and location.

Trace Configuration file

The content of the file should be:

active = true;
importance = '<<';
size = 100000;
keep = true;
log_dir = @"<output_path>";

NOTE:

<output_path> is the location where the log files will be created

An equivalent to '<<' in the importance parameter is xs (e.g.: importance = xs;)

The @ sign before the "<output_file>" is important to locate the directory, especially for Java based clients (IDT, WRC)

If severity parameter is used in the trace configuration file, make sure it has a space between the single quotas, in order to get a full trace, e.g.:

active = true;
importance = '<<';
severity = ' ';
size = 100000;
keep = true;
log_dir = @"<output_path>";

1. 1. Tracing via trace file

Each client searches for the trace configuration file in different folders. Bellow is the list of the paths and file names for each client application. To enable tracing, create a trace configuration file with the name and in the location appropriate for the client.

Universe Designer Tool:

..\SAP BusinessObjects\designer_trace.ini

..\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\win32_x86\designer_trace.ini

  Information Designer Tool:

<USER_HOME>\.businessobjects\bimodeler_14\config\BO_Trace.ini

..\SAP BusinessObjects\SAP BusinessObjects Enterprise XI 4.0\conf\BO_Trace.ini

  Web Intelligence Rich Client:

..\SAP BusinessObjects\WebIRichClient_trace.ini

1. 2. Tracing via environment variable

Tracing via environment variable simplifies tracing by using the same name and location of the trace configuration file regardless of the client application being traced. To enable tracing, create the trace configuration file and the environment variable pointing to the file:

Right-click My Computer > click Properties > Advanced tab > Environment Variables

Click New in the System or User variables section

Create BO_TRACE_CONFIGFILE variables. For example:

Variable Name: BO_TRACE_CONFIGFILE

Variable_Value: c:\botrace\BO_trace.ini

OK > OK to exit the dialog boxes

NOTE:

On Windows 7 the Environment variables are in Start > right-click Computer > Properties > Advanced System Settings > Advanced tab

User environment variables overwrite System environment variables – make sure the variable is created only once

It is also possible to create a BO_TRACE_LOGDIR environment variable, however if log_dir parameter is used in the trace configuration file, it will override the BO_TRACE_LOGDIR environment variable

Always make sure you specify the location of the log files (either in the trace configuration file log_dir parameter, or via BO_TRACE_LOGDIR environment variable to avoid creating the logs in multiple folders

If both tracing via a trace file, and environment variable is configured, the BO_TRACE_CONFIGFILE takes precedence

Database connection tracing

In certain occasions, more details are required on the database communication. There is a way to trace the communication between the client application and the DB driver via the connection server (CS) layer. Most of the relational databases connections could be traced via the CS (cs.cfg). Please check the referenced Knowledge Bases at the end of this document for specific database connection tracing

To enable CS database tracing follow these steps:

Navigate to the cs.cfg file located in "..\SAP BusinessObjects Enterprise XI 4.0\dataAccess\connectionServer"

Open the cs.cfg file in a text editor such as Notepad

Make sure the trace near the bottom of the file is activated

<Traces Active="Yes">

Save and close the file

NOTE:

The CS trace is enabled by default

For UDT and WRC there will be no extra file created, the logs will be written into the application log

For IDT the CS logs will be written into "InformationDesignTool_<PID>_<timestamp>_trace.glf"

Log file output

Each BI client application creates different trace logs. Include all files when sending to SAP support:

Universe Designer Tool:

designer_<PID>_<timestamp>_trace.glf

designer_sdk_<PID>_<timestamp>_trace.glf

Information Designer Tool:

idt_<PID>_<timestamp>_trace.glf

InformationDesignTool_<PID>_<timestamp>_trace.glf

Web Intelligence Rich Client:

wicdztrace folder

WebIRichClient_<PID>_<timestamp>_trace.glf

WebIRichClient_sdk_<PID>_<timestamp>_trace.glf

Hope this helps...

Thanks & Regards

Sandeep

[Former Member]

what location are they getting created at?

what are the file names of these logs?

do users use WebI Rich Client?

-Nikhil Nair

[former_member272336]

Hi,

On users desktops.

trace....

Not using webi rich client.

Using launchpad.

Not deliberatley activtade tracing.

Thanks

[denis_konovalov]

what are file names that are generated ?

If they are generated on the desktop itself - something in the way user profiles are setup redirects there.

I can believe that using BILaunchpad might generate some logs, but not on the desktop.

[former_member272336]

Hi,

Names are tracelog_<numbers>.glf

Thanks

[former_member272336]

Hi,

Thanks all for all advice.

Do you have any further info on why bi launchpad generating thes logs - how could configure user profile to redirect logs somehwere else.

We haven't deliberatley activated client-side tracing on the client PCs.

If they are generated on the desktop itself - something in the way user profiles are setup redirects there.

I can believe that using BILaunchpad might generate some logs, but not on the desktop.

Thanks