Auditing Problem

[Former Member]

Hello,

We have a default BO installation on win 2008 server and it is sp5 patch 1. We had configured auditing using ODBC data source to the sql server and It worked fine until last saturday 8:40 pm. For some reason it stopped working and I am trying to figure out what might be the cause.

Here are some symptoms:

1. In CMC auditing it says:
   • "Warning: No connection to Auditing Data Store from CMS BOP140.CentralManagementServer."
   • WARNING: Auditing data may remain in server buffers
   • And after we opened up SQL server configuration manager of the BO server machine and restarted SQL server, the following error added up to the list on CMC:   Warning: Client auditing is unavailable.
2. In the SQL server configuration manager in the BO server machine, we realize that the SQL server agent is down. Is it supposed to be that way?
3. We tried re-configuring, re-creating the ODBC datasource on server and saw each time the connection is successful. We also tried using sa user just incase. We also tried changing the servername/SQL_instance_name to ./SQL_instance_name just to indicate the SQL server is on the same machine and to avoid any network connectivity error, however it was no use.
4. Using an SQL server client tool, we also connected to the SQL server and made sure that database size can automaticly increase. Also, there we made sure the user we had to connect had db_owner authentication.
5. We restarted BO servers several times after each operation.
   

The problem might not be BO related, I suspect some ports might be closed in the network or something but before I go to the network guys in the department, can you help me explore any other possibility that is causing this?

Thank you in advance

[Former Member · Accepted solution]

Hello,

The problem is resolved. It turned out that although the database size could grow on its own, since it is sql express edition that comes with the default, it is limited to 4 gb.

Under the directory,

E:\SAP BusinessObjects\MSSQLSERVER2008\instance.root\MSSQL10.BOE140\MSSQL\Log

in the most recent error log file, it said

2013-07-23 10:55:59.75 spid52 CREATE DATABASE or ALTER DATABASE failed because the resulting cumulative database size would exceed your licensed limit of 4096 MB per database.

2013-07-23 10:55:59.75 spid52 Error: 1105, Severity: 17, State: 2.

2013-07-23 10:55:59.75 spid52 Could not allocate space for object 'dbo.ADS_EVENT_DETAIL' in database 'BOE140_Audit' because the 'PRIMARY' filegroup is full. Create disk space by deleting unneeded files, dropping objects in the filegroup, adding additional files to the filegroup, or setting autogrowth on for existing files in the filegroup.

Thus, upon deleting the records older than 120 days in CMC auditing tab, the issue is resolved.

Thank you for your time

[Former Member · Accepted solution]

Hi,

I found same problem. I would like to know how to delete record older than 120 days in CMC audit?

Thank for you advise.

[Former Member · Accepted solution]

Delete events older than (days) field, enter the number of days you want information to

remain in the database. (Minimum value 1, maximum value 109,500.)

Caution:

Data older than the number of days set here will be permanently deleted from the ADS; it cannot

be recovered. You may want to consider periodically moving records to an archive database if you

want to maintain long-term records.

1611909 - How to configure Auditing Data Store in BI4.0 platform

[Former Member]

This message was moderated.

[former_member182521]

Hello Emre,

• The error message Warning: Client auditing is unavailable signfies that the Client Auditing Proxy Service is missing from the Adaptive Processing Server. Kindly refer the note below for the resolution http://service.sap.com/sap/support/notes/1694890

• For the issue Warning: No connection to Auditing Data Store from CMS BOP140.CentralManagementServer." WARNING: Auditing data may remain in server buffers , please refer the SAP Note below http://service.sap.com/sap/support/notes/1812416

• Please note 1433 is the port used by the SQL Server by default.

Hope this helps

Regards,

Mani