Audit log not logging

Thank you for your time.
I have a database that i need to have auditing on. The database was moved
to a larger server. I had auditing on before the move, but now in my SQL
Sercer audit log I only have the error message 15457 Severity: 0, State: 1.
I need auditing on for this database, and have not been able to find
anything online that explaines what might have caused the logging to stop or
how to fix this issue. The users can still login, but SQL Server isn't
auditing it anymore.
Thank you again for your time.As there is two types of auditing, have a look at the
following article
http://msdn.microsoft.com/library/default.asp?
url=/library/en-us/adminsql/ad_security_2ard.asp, if its
C2 auditing then it needs to be used in the same line as
starting your SQL Server service.
Peter
"Denial ain't just a river in Egypt."
Mark Twain
>--Original Message--
>Thank you for your time.
>I have a database that i need to have auditing on. The
database was moved
>to a larger server. I had auditing on before the move,
but now in my SQL
>Sercer audit log I only have the error message 15457
Severity: 0, State: 1.
>I need auditing on for this database, and have not been
able to find
>anything online that explaines what might have caused the
logging to stop or
>how to fix this issue. The users can still login, but
SQL Server isn't
>auditing it anymore.
>Thank you again for your time.
>.
>|||What were you auditing? Perhaps there was a startup param set on your old
server. Perhaps you chose to auditing logins via Enterprise Manager (right
click on the server name, properties, Security tab).
--
Keith
"Marc M" <Marc M@.discussions.microsoft.com> wrote in message
news:A89E9DBD-9C96-400B-8208-6AA7EF86141F@.microsoft.com...
> Thank you for your time.
> I have a database that i need to have auditing on. The database was moved
> to a larger server. I had auditing on before the move, but now in my SQL
> Sercer audit log I only have the error message 15457 Severity: 0, State:
1.
> I need auditing on for this database, and have not been able to find
> anything online that explaines what might have caused the logging to stop
or
> how to fix this issue. The users can still login, but SQL Server isn't
> auditing it anymore.
> Thank you again for your time.|||Thank you for the article. That is what I was trying to audit. I had the
auditing working before the database was moved, but now I only get the error
message in the audit log. I didn't know about the SQL Profiler before.
Thanks for pointing that out.
"Peter The Spate" wrote:
> As there is two types of auditing, have a look at the
> following article
> http://msdn.microsoft.com/library/default.asp?
> url=/library/en-us/adminsql/ad_security_2ard.asp, if its
> C2 auditing then it needs to be used in the same line as
> starting your SQL Server service.
> Peter
> "Denial ain't just a river in Egypt."
> Mark Twain
>
> >--Original Message--
> >Thank you for your time.
> >I have a database that i need to have auditing on. The
> database was moved
> >to a larger server. I had auditing on before the move,
> but now in my SQL
> >Sercer audit log I only have the error message 15457
> Severity: 0, State: 1.
> >I need auditing on for this database, and have not been
> able to find
> >anything online that explaines what might have caused the
> logging to stop or
> >how to fix this issue. The users can still login, but
> SQL Server isn't
> >auditing it anymore.
> >Thank you again for your time.
> >.
> >
>|||Thank you for the suggestion to check the old server, I'll look at that to
see if there is anything running that we didn't get moved.
We were trying to audit the logins and logouts of the users of the database.
I already have in place the auditing through Enterprise Manager, and were
looking at it throught the logs associated with that. I really apprecitate
the level of detail provided on how to activeate it and would apprecitate
that level of detail on the solution for why we are only getting the error
15457 in those logs.
Thank you for your help.
"Keith Kratochvil" wrote:
> What were you auditing? Perhaps there was a startup param set on your old
> server. Perhaps you chose to auditing logins via Enterprise Manager (right
> click on the server name, properties, Security tab).
> --
> Keith
>
> "Marc M" <Marc M@.discussions.microsoft.com> wrote in message
> news:A89E9DBD-9C96-400B-8208-6AA7EF86141F@.microsoft.com...
> > Thank you for your time.
> > I have a database that i need to have auditing on. The database was moved
> > to a larger server. I had auditing on before the move, but now in my SQL
> > Sercer audit log I only have the error message 15457 Severity: 0, State:
> 1.
> > I need auditing on for this database, and have not been able to find
> > anything online that explaines what might have caused the logging to stop
> or
> > how to fix this issue. The users can still login, but SQL Server isn't
> > auditing it anymore.
> > Thank you again for your time.
>