Skip to Content

Trick : How you can stop server trace log to generate (in BO) this way also

We know the importance of generating BO traces without requiring a restart and how it helps us either to perform a root-cause-analysis or to dig-n-dive deep.  But then, when the work is done the logs are too huge (of course, we did need it that excessive and intensive) but it consumes tremendous disk space (I’m talking gigs).

You certainly do have a way to stop it- but sometimes the standard way doesn’t work – Apparently and evidently, I have seen this at least couple of times in my life, that when you stop the server tracing by setting the parameter active = false in the trace.ini file, even then the parameter DOES NOT allow the traces to be stopped.  The tracing level option at the server properties level is ALREADY set to none (if BI4.x)- and (if XI 3.1 – there is no -trace applied) still no luck. This situation is though not common; but I have seen with other customers as well.

Please see Tracing in SAP BusinessObjects Enterprise XI3.1 on how to set tracing without requiring a restart of servers

This goes on for days; now your logs keep filling i.e. no. of servers * every 60 seconds of poll time * no. of days = problems 😆

Let’s cheat with Logs now 😉

In this case what best you can do is, it reads the other parameters – the trick is with the parameter

log_dir =  <folder path of logs where it is to be generated> by default, this parameter has value = \logging\

This is the folder that defaults to the logging folder in the installation directory of the BusinessObjects, unless explicitly specified.


Simply change the location of the folder path where logs are generated to something which doesn’t exists on your computer.  I take this funny example, I don’t have any folder called “logs_please_dont_appear” under any drive 😀

Now what I do is, I specify this as the location for the parameter log_dir = C:\logs_please_dont_appear

How this works – it wants to now generate traces but it doesn’t find the location to put the logs for.  Interestingly, since I’ve cheated it – now the logs just don’t appear – as you have convincingly pleased the logs to not appear 😛


I don’t say to follow this as a usual practice to stop tracing but this will certainly help when it doesn’t stop normally.  If you ask, what if the log_dir parameter is not readable as well (it never did for me at least in my lifetime) –  I would happily advice you to knock SAP’s door.  This blog creates enough awareness on how you can also stop the logs to generate when in this situation.

Very Important Note – This is my first blog 😎

Comments are closed.
    • @chetan: Thank you.

      Possibly or may be you have misread this blog- and I am completely aware you can disable it – but – my intention to write this is when it DOES NOT read the active = false; and the tracing option at the server properties is already set to none (if BI4.x) and if XI3.1 there is no -trace applied.

      What would you do then?  May be here I would like to know how do you disable it? Please advise 🙂

      I know it works all time but I am focusing on when it doesn’t read it – and I have seen this situation at least twice and may be you have not – and am helping others who are facing it or faced it.  🙂

      I have highlighted the word in the blog now – so it is read better now on wards .

  • Interesting read !

    Would like to know if this still also stop the tracing process or simply stops the writing process.

    Usually active=false does the job and would be the best practice in this case! 🙂

    • @sid: Thank you.

      It wants to write trace logs; but it can’t – so evidently, it just stops the writing process.  I agree the best practice but am being specific when it is unusual such that when you have turned on tracing through trace.ini and now when you want to disable it and

      it doesn’t read the active = false at all.

      You see here the situation we have now.  What is the practice you would follow now 😕

  • If the logs are enabled for all major servers and we use this trick, it could cause in server failure.

    I agree with Chetan and jsut disable them when required.

    • @jatin: Thank you.

      At least I have never seen server failing using this trick; I partially agree with Chetan because disabling is not an option available when you have turned on traces through trace.ini file, it starts tracing and now when you want to stop it, the active = false is not readable and the tracing at the server properties level is set to none already.  What option you have to disable it?

  • If “active=false” or any other parameter is not working, you must get your environment verified by SAP support because the product is designed to work so. Because the issue is specific to your environment and cannot be a bug as it works for others. It also means that there might be several config issues with this environment and so on….

        • There are no configuration issues as far as I know with respect to this and to the people where they faced this – product runs fine for everything else.

          I don’t call it as bug either.  It’s just that specific thing stopped working suddenly somehow- there are other people and customers I know who faced it and I helped them in the past – nevertheless, this trick creates an awareness that am sure others have not known earlier.

          Thank you,  Rahul

Comments are closed.