Skip to Content

On WINDOWS

1. Create a directory : C:\Logs

2. Copy BO_trace.ini file inside this directory

3. Add two SYSTEM variables:
BO_TRACE_LOGDIR=C:\Logs
BO_TRACE_CONFIGFILE=C:\Logs\BO_trace.ini

4. Restart WIReportServer

5. You should have a log file in C:\Logs: 

C:\Logs\WIReportServer_XXXX_trace.log

For each WIReportServer workflow, you should have XML files in : C:\Logs\wicdztrace

6. The easiest way to send the logs is to zip the full arborescence c:\logs.
So weget the WIReportServerXXXX.log and the xml files.

On UNIX All

1. Create a directory /tmp/logs

2. Copy BO_trace.ini inside this directory

3. Export the following two variables at the *end* of the shell running WIReportServer: ${INSTALLDIR}/bobje/setup/env.sh
export BO_TRACE_LOGDIR=/tmp/logs
export BO_TRACE_CONFIGFILE=/tmp/logs/BO_trace.ini

5. You should have a log file in /tmp/logs:  /tmp/logs/WIReportServer_XXXX_trace.log

For each WIReportServer workflow, you should have XML files in :   /tmp/logs/wicdztrace

6. The easiest way to send the logs is to zip the full arborescence /tmp/logs/
So we get the WIReportServerXXXX.log and the xml files.

Inside Bo_trace.ini file you have to update as following.

active = true;

importance = ‘<<‘;

size = 10000000;

keep = true;

In the following scenarios, if there is any failure observed we require the traces to understand the root cause.

  1. Viewing a Webi document
  2. Editing a Webi Document
  3. Scheduling a Webi Document
  4. Drill-down a Webi Document etc..
To report this post you need to login first.

1 Comment

You must be Logged on to comment or reply to a post.

Leave a Reply