System.Web.Services.Protocols.SoapException:

I am new to DB Audit. We have set up a few tables for DB Audit and receieve the following error. The server principal "sa" it not able to access the database "our db name" under the current security context. There are Web Services writing/updating/deleting records in to the db that we want to audit. Any help would be appreciated. Thanks...

Please provide more details about your environment. Which database system type are you auditing? Is this a SQL Server system? Which version?

Did you setup system-level auditing for monitoring user/system activities or data-change auditing for capturing data changes?

Which DB Audit version are you running?

Thanks for the quick reply. It is SQL Sever 2005(9.00.3054.00 SP2 Enterprise Edition (64-bit), 3.2 of DB Audit, System Level Auditing is disabled.

From your reply I assume you are doing data-change auditing against SQL Server 2005 database. You should set the TRUSTWORTHY ON flag for the database being audited. Without this flag, the auditing procedures are unable to write to the repository database, and as a result, updates fail and you are getting exceptions in your Web application.

Note that DB Audit version 4 does it automatically whenever you enable the data-change auditing. I highly recommend upgrading to version 4 for this and many other reasons.

Thank you for your timely responses. We will be setting the flag that you mention and evalute the option of upgrading. I will follow on the success or failure of the trustwothy flag in the 3.21 Environment.

We still get the same error message on 3.21 version. We are seeing this on two different SQL boxes but have the same configuration.

Please check a few things:

1. The TRUSTWORTHY flag has been set on the audited database.
2. "sa" login has access to the repository database, and "sa" login is mapped to "dbo" user in that database.
3. The repository database has an owner, normally "dbo"
4. You can update audited tables in the SQL Query Analyzer or MS Management Studio. If you get an error, please provide the complete error text.

Msg 916, Level 14, State 1, Procedure audit_tr_200801091001196740, Line 36
The server principal "sa" is not able to access the database "LW_Auditing" under the current security context.

Is this a response to question #4 from the previous post?

What about #1? Have you set the required flag?

After recreating another db and rerunning and then dropping the target information and resetting, everything appears to be working. Thanks again on your very timely responses.

Thanks for the status update