Skip to Content
avatar image
Former Member

CMS Auditing Events

Hi,

When monitoring my servers in the CMC I can see that the CMS has a warning in the health column. The reason for this warning is that the current number of auditing events in the queue exceed a specified value.

In the server properties I can see the following metric:

Auditing Metrics:

Current Number of Auditing Events in the Queue = 6393

But how to I resolve the issue? Where can i find the queue?

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • Nov 21, 2011 at 02:49 PM

    Hi,

    Check if you have files in the auditing folder:

    <INSTALL>\SAP BusinessObjects Enterprise XI 4.0\Auditing

    This folder might be different in your system. Check the Placeholders (CMC > Servers > Right click on the node you want to check and select "Placeholders")

    You might have problems updating the records on your auditing database: check the logging folder to see the CMS log files.

    More information in the "Auditing" section of the BI4.0 guide:

    http://help.sap.com/businessobject/product_guides/boexir4/en/xi4_bip_admin_en.pdf

    Regards,

    Julian

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hi again

      I have the files in the auditing folder on the server and the placeholders are ok too. I also checked the data conneciton and it works fine.

      When i look into the admin guide I don't even see a decsription / explanation of the Auditing Metrics :

      Current Number of Auditing Events in the Queue

      I the log file (in the logging folder) I get the following:

      FILE_TYPE:DAAA96DE-B0FB-4c6e-AF7B-A445F5BF9BE2

      ENCODING:UTF8

      RECORD_SEPARATOR:30

      COLUMN_SEPARATOR:124

      ESC_CHARACTER:27

      COLUMNS:Location|Guid|Time|Tzone|Importance|Severity|Exception|DeviceName|ProcessID|ThreadID|ThreadName|ScopeTag|MajorTick|MinorTick|MajorDepth|MinorDepth|RootName|RootID|CallerName|CallerID|CalleeName|CalleeID|ActionID|DSRRootContextID|DSRTransaction|DSRConnection|DSRCounter|User|ArchitectComponent|DeveloperComponent|Administrator|Unit|CSNComponent|Text

      SEVERITY_MAP: |Information|W|Warning|E|Error|A|Assertion

      HEADER_END

      .\sisecserver_impl.cpp:367:-: TraceLog message 4136

      |6c6eab56-183f-85f4-da13-2bd70d439ef1|2011 11 14 11:03:36:268|+0100|>>|A| |cms_vtbo02.CentralManagementServer| 1396|1940|| |112|0|2|0|CMC.WebApp|vtbo02:1220:37.29788:1|BIPSDK.SecurityInfo2:getKnownRights|vtbo02:1220:37.29788:54|cms_vtbo02.CentralManagementServer.processSerializedBatch|localhost:1396:1940.111711:1|CmMe3s.3MUC2tHb2_tUrLPY7459|||||||||||assert failure: (.\sisecserver_impl.cpp:367). (wireProps != NULL : no message).

  • avatar image
    Former Member
    Jan 06, 2012 at 02:23 PM

    I am facing the same issue with my CMS health status in RED with over 7000 current number of auditing events in queue. If I go to the auditing option and turn off auditing, it will go back to green. However, even if I turn on medium auditing (pre defined setting), the health would go back to RED. Is there any way to handle this?

    Add comment
    10|10000 characters needed characters exceeded