I am attempting to configure the System Audit function on a MS SQL Server and whenever I click on one of the "Filter" options such as Databases, Objects, Logins, etc I am prompted with the following error message:

Quote:

The specified schema name "db_audit" either does not exist or you do not have permission to use it.

If I click "OK" to dismiss the error I am able to make my desired selection in the filtering options, however when I finally click the "Enable System Audit" button I am prompted with the same error again and the enable action fails.

I am using a trusted connection to the "DB LIB" connection where the account I am using has admin rights on the SQL Server.

What am I doing wrong during the configuration process?

Wed Jul 23, 2008 4:58 pm

SysOpSite Admin

Joined: 26 Nov 2006Posts: 6608

Which version of DB Audit Management Console are you running?

Just in case… you can check it in the Help/About menu.

Wed Jul 23, 2008 5:15 pm

cbt_dba

Joined: 03 Sep 2007Posts: 4

I'm running 4.0.14

Thu Jul 24, 2008 9:36 am

SysOpSite Admin

Joined: 26 Nov 2006Posts: 6608

You likely had DB Audit installed in the past or and then removed or changed some settings, or did it fro ma different computer. Please check a couple of things

1. If db_audit login exists on the server, and its default database is set to the correct audit repository. If you are not sure, just drop the login and drop db_audit user from the repository database to start fresh.

2. The connect profile settings in the DB audit Management console correct point to the right database. You can check them in the registry, but it might be just easier to use Tools/change Local Audit Repository Location menu to update the profile settings.

Please let us know if the above suggestions help or if my guess that in the past DB Audit has been already installed on that server is wrong.

By the way, are you aware that the last released version is 4.1.22

Thu Jul 24, 2008 10:36 am

cbt_dba

Joined: 03 Sep 2007Posts: 4

During my trouble shooting of this issue I did reinstall the software so that may have left behind some settings as you suggested.

(2) As I described earlier in this post I then ran into the "The specified schema name "db_audit" either does not exist...." error when trying to enable the System Audit.

I then followed your instructions regarding dropping and recreating the db_audit login and user as well as using the Tools>Change Local Audit Repository Location menu item to update the profile settings.

After doing this, the error "The specified schema name "db_audit" either does not exist...." still persists.

Is there still a permissions conflict or perhaps is there a way to manually create the various tables and stored procedures in the database I have chosen as the audit repository?

Lastly, is the current license I have for version 4.0 also valid for 4.1.22 so that I can simply download and install the new version?

If you got "annual maintenance" option with your license, the upgrade to 4.1 is free, if you don't, you can always add it; I think it is about $90 per license or close to that. The reason why I'm referring to that version is because in 4.1 you can specify custom password before install and avoid the hassle with manual db_audit account setup and password manipulations.

The current problem is caused by some kind of a discrepancy as a result of manual steps. The Management console is looking for db_audit user/schema in a wrong place and that's why you get "db_audit" doesn't exist. It also possible that you created the login, but didn't create db_audit user mapped to that login in the chosen repository database. Do you get the same error after using Tools/Change…Location menu?

Also, have you checked the Windows application Event Log on the SQL server computer? Are there any errors/messages recorded by DB Audit. If yes, what do they say?

Thu Jul 24, 2008 11:41 am

SysOpSite Admin

Joined: 26 Nov 2006Posts: 6608

DB Audit is a database security solution, it has nothing to do with counting business inventories.

Mon Oct 12, 2009 7:50 am

zeomkean

Joined: 19 Mar 2015Posts: 1Country: Pakistan

For a rapid deployment, you have several options, one is to use DB Audit API and call it from a batch file or from a program and tell it what you want to setup. Another solution is to script out the setup and Pass4sure a+ book
run it a batch/SQL script, but that could be a bit more complicated if you also use system auditing or some other features.