CA Service Management

  • Private Community
Back to discussions
Expand all | Collapse all

Disable Tracing in CA BOXI 4.1 SP3

  • 1.  Disable Tracing in CA BOXI 4.1 SP3

    Posted Feb 01, 2016 03:24 AM

    Hi Team,

     

    I want to disable all the tracing in CA BOXI 4.1 SP3. Kindly provide me the steps for doing that.

     

    Is it necessary to turn on the tracing?

     

    Regards,

    Balram Singh Deswal



  • 2.  Re: Disable Tracing in CA BOXI 4.1 SP3
    Best Answer

    Broadcom Employee
    Posted Feb 01, 2016 10:25 AM

    Balram,

     

    Try the steps mentioned in this SAP article?  http://scn.sap.com/community/bi-platform/blog/2013/01/31/configuring-trace-logs-in-businessobjects-40

     

    1. For each Server Component (CMC -> Servers -> Server list),  Set Log Level = None on each server component
    2. For each Application (CMC -> Applications), ensure that each Application is also set with Log Level = None

     

    _R



  • 3.  Re: Disable Tracing in CA BOXI 4.1 SP3

    Posted Feb 01, 2016 11:08 AM

    Thanks Raghu for this useful link.

    If we disable all types of tracing, will there be any effect on Application?

     

    Regards,

    Balram



  • 4.  Re: Disable Tracing in CA BOXI 4.1 SP3

    Broadcom Employee
    Posted Feb 01, 2016 11:42 AM

    Usually it's set to UnSpecified. 

     

    None should not cause any harm from my experience.

     

    _R



  • 5.  Re: Disable Tracing in CA BOXI 4.1 SP3

    Posted Feb 01, 2016 11:50 AM

    Okay. Thanks.

     

    One more issue that I face is that I was not being able to login to BI launchpad from the CA Service Desk server. During Configure wizard of CA BOXI, it was giving error of 64-bit client configuration. So I uninstalled the client and server services from service desk server, installed them again and then run that configuration again. The error of 64-bit client got resolved. Now I am able to log in to the BI launchpad but now my crystal reports are giving error during generation. What could be the possible reason for that.

     

    Kindly advice.

     

    Regards,

    Balram



  • 6.  Re: Disable Tracing in CA BOXI 4.1 SP3

    Broadcom Employee
    Posted Feb 01, 2016 08:20 PM
    Would you be able to provide the error message? Are WEBI reports working fine ?


    _R




  • 7.  Re: Disable Tracing in CA BOXI 4.1 SP3

    Posted Feb 02, 2016 08:39 AM

    Hi Raghu,

     

    Our scope is only crystal reports to run fine. When I run those reports, sometimes they run, sometimes they given error of session time out and sometimes they give error to contact the administrator. Sometimes they run Ok. Kindly suggest what to do for such irregular behaviour of reports. I want them to give output every time they run from service desk. Screenshot cannot be provided due to security limitations at the client environment.

     

    Regards,

    Balram



  • 8.  Re: Disable Tracing in CA BOXI 4.1 SP3

    Broadcom Employee
    Posted Feb 02, 2016 09:05 AM
    I will be honest. Without the exact error messages, it will be tough to troubleshoot this one.  


    Timeouts could be tomcat timeout / odbc connection time out / SDM session timeout.  If your session  expired you need to re run the report for it to show up.  


    For other errors we would need more details. 


    Maybe we can start a new thread and not mix this with the original intention of the thread about disabling traces ?



    _R

     




  • 9.  Re: Disable Tracing in CA BOXI 4.1 SP3

    Posted Feb 02, 2016 09:17 AM

    Yes you are right. I will try to arrange for the screenshots and create a new thread for further discussion.

     

    Thanks for your support!

     

    Regards,

    Balram



  • 10.  Re: Disable Tracing in CA BOXI 4.1 SP3

    Posted Feb 04, 2016 04:01 AM

    Hi Raghu,

     

    Kindly provide your valuable feedback on the following threads:

    Delete all Tickets before going Live

    Volume Trend Crystal Report Giving Error

     

     

    Deleting Tickets is the priority one

     

    Thanks & Regards,

    Balram