Re: Another 17055 error problem

anonymous_at_discussions.microsoft.com
Date: 02/05/04 

Date: Wed, 4 Feb 2004 17:34:42 -0800

I meant in the filter settings is where I turned those
off.
>-----Original Message-----
>I'm not quite sure what you mean by "I have turned off
the information also"
>?
>Changing the audit setting requires a restart of the
service I think to take
>effect
>
>--
>HTH
>
>Jasper Smith (SQL Server MVP)
>
>I support PASS - the definitive, global
>community for SQL Server professionals -
>http://www.sqlpass.org
>
>
><anonymous@discussions.microsoft.com> wrote in message
>news:932701c3eac2$bc05d640$a301280a@phx.gbl...
>> Those are now off and it made no change. I have turned
>> off the information also and that stops the log from
>> filling up. But it does not stop the problem.
>>
>> Thanks
>>
>> >-----Original Message-----
>> >That just looks like you have Auditing set to either
>> Success or All. You can
>> >check this by looking at the Security Tab on the Server
>> Properies dialog.
>> >
>> >--
>> >HTH
>> >
>> >Jasper Smith (SQL Server MVP)
>> >
>> >I support PASS - the definitive, global
>> >community for SQL Server professionals -
>> >http://www.sqlpass.org
>> >
>> >
>> >"Bob" <anonymous@discussions.microsoft.com> wrote in
>> message
>> >news:955c01c3ea8c$b7036580$a001280a@phx.gbl...
>> >> After applying some updates (root certificate,jet4.0
SP8
>> >> and security updates 810217,828749and 824145), I now
get
>> >> the following error:
>> >>
>> >> 18454 :
>> >> Login succeeded for user '<user name>_SQL'.
Connection:
>> >> Non-Trusted.
>> >>
>> >> Where <user name> is the login name.
>> >>
>> >> We are running SQL2000. Permissions are set for
Windows
>> >> and SQL.
>> >>
>> >> Any thoughts?
>> >
>> >
>> >.
>> >
>
>
>.
>