Login failed for user NT AUTHORITY\NETWORK SERVICE

Hi All,
I've done some searching around but can't find an answer to this problem.
I've recently noticed an error in the event logs relating to the Network
Service account trying to connect to my SQL 2005 server. The logs give me
the following information :-
12/06/2007 23:30:01,Logon,Unknown,Login failed for user 'NT
AUTHORITY\NETWORK SERVICE'. [CLIENT: 10.0.0.4]
12/06/2007 23:30:01,Logon,Unknown,Error: 18456<c/> Severity: 14<c/> State: 1
6.
This is all the info I have to go on. Can anyone provide me with some
assistance with trying to troubleshoot?Well, it seems that some process working in Network Service user context is
trying to connect your instance and Network Service has no permission to
connect the target database in SQL Server. Run SQL Server Profiler and catch
failed login attempts (catch Audit Login Failed event with ApplicationName
and DatabaseName columns selected to trace).
Regards
Pawel Potasinski
[http://www.potasinski.pl]
Uytkownik "Matt" <Matt@.discussions.microsoft.com> napisa w wiadomoci
news:AB02D9C1-DF84-4A43-BCA5-4A84B8323525@.microsoft.com...
> Hi All,
> I've done some searching around but can't find an answer to this problem.
> I've recently noticed an error in the event logs relating to the Network
> Service account trying to connect to my SQL 2005 server. The logs give me
> the following information :-
> 12/06/2007 23:30:01,Logon,Unknown,Login failed for user 'NT
> AUTHORITY\NETWORK SERVICE'. [CLIENT: 10.0.0.4]
> 12/06/2007 23:30:01,Logon,Unknown,Error: 18456<c/> Severity: 14<c/> State:
> 16.
> This is all the info I have to go on. Can anyone provide me with some
> assistance with trying to troubleshoot?|||Thanks Pawel,
The only way I am able to force the netork login failure is by restarting
the MSSQL server process. Of course, when I do this with the Profiler
running, I end up with a Trace error in the log as soon as the server goes
online and the logging stops. Any idea how I can make the Profiler keep
running even when the server gets restarted? Or is there a way that I can
make the profiler start when the server starts before loading anything else?
Matt
"Pawel Potasinski" wrote:

> Well, it seems that some process working in Network Service user context i
s
> trying to connect your instance and Network Service has no permission to
> connect the target database in SQL Server. Run SQL Server Profiler and cat
ch
> failed login attempts (catch Audit Login Failed event with ApplicationName
> and DatabaseName columns selected to trace).
> --
> Regards
> Pawel Potasinski
> [http://www.potasinski.pl]
>
> U?ytkownik "Matt" <Matt@.discussions.microsoft.com> napisa3 w wiadomo?ci
> news:AB02D9C1-DF84-4A43-BCA5-4A84B8323525@.microsoft.com...
>
>|||I ment to say "I end up with a Trace error in the log as soon as the server
goes
OFFLINE and the logging stops".
Just to be clear, I see the Failed Audit login message in the SQL log only
when I start the start the server. It doesnn't continuely happen, therefore
the only time I can try and trace the cause of the issue is as the server
starts up
"Matt" wrote:
[vbcol=seagreen]
> Thanks Pawel,
> The only way I am able to force the netork login failure is by restarting
> the MSSQL server process. Of course, when I do this with the Profiler
> running, I end up with a Trace error in the log as soon as the server goes
> online and the logging stops. Any idea how I can make the Profiler keep
> running even when the server gets restarted? Or is there a way that I can
> make the profiler start when the server starts before loading anything els
e?
> Matt
> "Pawel Potasinski" wrote:
>|||OK, with a bit of luck, patience and timing, I managed to get a trace of the
Audit Login Failed notice. It looks like our CRM application is having a ba
d
day and isn't able to logon to something. However, even though I enabled al
l
columns in the Profiler and made sure DatabaseName column was selected, I
only get columns ApplicationName - TextData listed. The all-important info
aon what table the service is trying to access is still missing.
Any thoughts?
"Matt" wrote:
[vbcol=seagreen]
> I ment to say "I end up with a Trace error in the log as soon as the serve
r
> goes
> OFFLINE and the logging stops".
> Just to be clear, I see the Failed Audit login message in the SQL log only
> when I start the start the server. It doesnn't continuely happen, therefo
re
> the only time I can try and trace the cause of the issue is as the server
> starts up
> "Matt" wrote:
>|||Matt (Matt@.discussions.microsoft.com) writes:
> OK, with a bit of luck, patience and timing, I managed to get a trace of
> the Audit Login Failed notice. It looks like our CRM application is
> having a bad day and isn't able to logon to something. However, even
> though I enabled all columns in the Profiler and made sure DatabaseName
> column was selected, I only get columns ApplicationName - TextData
> listed. The all-important info aon what table the service is trying to
> access is still missing.
It's seems difficult to find out which table the CRM app is trying to
access, when it does not comes as far as connecting...
Then again, if you get a single login failure when you start SQL Server,
and the CRM application does not produce an error, maybe this is not
really an issue to lose sleep over?
Erland Sommarskog, SQL Server MVP, esquel@.sommarskog.se
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pr...oads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodin...ions/books.mspx|||Matt,
Is this a standalone server or a cluster? have you recently upgraded to W2K3
SP2? We now see this when we patch or failover our clustered SQL2005 server.
Chris
"Matt" <Matt@.discussions.microsoft.com> wrote in message
news:8AEE2C89-5A8C-4005-A241-862CAE01CE38@.microsoft.com...[vbcol=seagreen]
>I ment to say "I end up with a Trace error in the log as soon as the server
> goes
> OFFLINE and the logging stops".
> Just to be clear, I see the Failed Audit login message in the SQL log only
> when I start the start the server. It doesnn't continuely happen,
> therefore
> the only time I can try and trace the cause of the issue is as the server
> starts up
> "Matt" wrote:
>

Login failed for user (null).

I recieved this error in my logs:

Login failed for user '(null)'. Reason: Not associated with a trusted SQL Server connection.

It appeared nearly 20 times, then about 30 minutes after the first occurence, I noticed in my Event Viewer this error:

The registration of DNS name XXX.XXX.XXX.XX.in-addr.arpa. for network name resource 'SQL Network Name(SQLServer)' failed for the following reason:

DNS operation refused.

After that I began recieving hundreds of errors like this one:

Login failed for user 'SQL user'. Only administrators may connect at this time.

I was unable to connect to the server to see what was going on so I had to failover the server. That's why my troubleshooting is limited to error logs. After the failover, everything came up fine with no more errors. Has anyone ever encountered this before?

BTW, This is a SQL 2000 Cluster on Windows 2000.This happened to me once. The issue I had was the sql server lost it's connection to the network. The techies checked it out for me and it needed a new nic card. It was fine after that.

Login failed for user '(null)'

I get the following error in the SQL Logs.

What does this error mean and how can I resolve this?

18452 :
Login failed for user '(null)'. Reason: Not associated with a trusted SQL Se
rver connection.

Thanks

Santhosh

Some client tries to login to SQL Server without passing the WIndows credentials.

HTH, Jens K. Suessmeyer.

http://www.sqlserver2005.de|||

How can I resolve this?

The scenario is... We use a third party backup software. This backup software uses SQL as its database to store session records. Whenever, the tape engine starts it logs on the above message and also during the backups it logs on the above message.

While configuring SQL to be as the backup software's database, there is a option to enter SQL Security. When we enter SA as security, we do not get this error. When we use windows security, we get this error.

Any help is appreciated.

Thanks

Santhosh

|||

Check the KBAs

http://support.microsoft.com/kb/265808

http://support.microsoft.com/kb/555332

And http://blogs.msdn.com/sql_protocols/archive/2005/09/28/474698.aspx if its a SQL 2005 box.

As suggested you have to check and configure the SQL Server authentication to allow this backup software to connect to database.

|||

Is the backup software running on the same machine as SQL Server? If not, are the machines in the same domain?

Thanks
Laurentiu

sql

Login Failed error 18456

I was reviewing our logs from yesterday and today and I have probably 100
errors:
12/21/2005 08:30:26,Logon,Unknown,Login failed for user 'ApplicationUser'.
[CLIENT: 1.1.1.119]
12/21/2005 08:30:26,Logon,Unknown,Error: 18456<c/> Severity: 14<c/> State:
16.
This is the login that we are using for our application login. We haven't
had any reports of anyone not being able to log on or anything but there are
over 100 errors in the error logs. The user has a server role of dbcreator,
and is mapped to several databases with a role membership of db_datareader,
db_datawrite, and public. Our application uses this account to login to SQL
Server.
We are using SQL Server version 2005.
What are the possible causes to this error? It seems like it is a simple
login failure, but trust me when i tell you...if people were not able to
logon we would hear about it.
Thanks for any insight you might be able to provide.
RonCould It be that the Standarddatabase of the user is not present
anymore ? This usally happens when you moved a database and scripted
out the users with their original database which isn=B4t present on the
destination system. Try to check that in Dev Studio.
HTH, Jens Suessmeyer.|||Pardon my newbe question...but what is the StandardDatabase? is it a
database that they were given rights to but then the database was removed?
Your response sounds right in the fact that we added the user to the Model
database so that they were given rights based on that database when every
new database was converted. We had a problem with the application and one
of the databases that was converted and ended up removing it temporarily to
fix the problem in the application...could that be the culprit?
Thanks!
Ron
"Jens" <Jens@.sqlserver2005.de> wrote in message
news:1135176452.767970.33270@.g47g2000cwa.googlegroups.com...
Could It be that the Standarddatabase of the user is not present
anymore ? This usally happens when you moved a database and scripted
out the users with their original database which isnt present on the
destination system. Try to check that in Dev Studio.
HTH, Jens Suessmeyer.

Login failed

I keep getting this error in the Queue Reader
How can I set the way the Publisher logs into the subsriber (push
subsription)?
Thank you,
Samuel
Samuel, I suggest you open a support incident with Microsoft on this one.
Its difficult to determine exactly what your problem is.
Hilary Cotter
Director of Text Mining and Database Strategy
RelevantNOISE.Com - Dedicated to mining blogs for business intelligence.
This posting is my own and doesn't necessarily represent RelevantNoise's
positions, strategies or opinions.
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Samuel Shulman" <samuel.shulman@.ntlworld.com> wrote in message
news:esrZY1a4GHA.3964@.TK2MSFTNGP04.phx.gbl...
>I keep getting this error in the Queue Reader
> How can I set the way the Publisher logs into the subsriber (push
> subsription)?
> Thank you,
> Samuel
>

Logging to second disk -- what happens when it crashes?

Currently we have SQL Server running on a single RAID5 array.
The data and the logs are all written to this array. We don't
have huge volume of activity, but it is growing. Most activity
is from our website that interacts a lot with the database.

We have read that it is a good idea to separate the data files
from the log files, having each on separate disks (or in the
case of RAID, separate arrays). So, we are considering adding
a separate SCSI hard drive, or maybe a RAID 1 system, and have
sql server log to that instead.

My question is, what happens if that secondary drive or array
completely fails. Let's say it melts. Assuming the OS doesn't
crash (Windows 2003 Server), what will SQL Server 2000 do when
the drive stops working and it is trying to write its data
logging to it? Will it continue to function and write alert
events? Will it shutdown? If it shuts down, how do we alter its
configuration to tell it to use another drive for the logs?

Also, what kind of throughput would we need to be doing to see
any kind of benefit to making this change? It is easier to
justify the expense of another disk or RAID setup if it is
actually going to matter. ;-)

Thanks all!

Thomas"Thomas" <thomas-ggl-02@.data.iatn.net> wrote in message
news:a9081691.0406021521.54c0f399@.posting.google.c om...
> Currently we have SQL Server running on a single RAID5 array.
> The data and the logs are all written to this array. We don't
> have huge volume of activity, but it is growing. Most activity
> is from our website that interacts a lot with the database.
> We have read that it is a good idea to separate the data files
> from the log files, having each on separate disks (or in the
> case of RAID, separate arrays). So, we are considering adding
> a separate SCSI hard drive, or maybe a RAID 1 system, and have
> sql server log to that instead.

RAID 1 at the least. Don't use a single drive in this case.

> My question is, what happens if that secondary drive or array
> completely fails. Let's say it melts. Assuming the OS doesn't
> crash (Windows 2003 Server), what will SQL Server 2000 do when
> the drive stops working and it is trying to write its data
> logging to it? Will it continue to function and write alert
> events? Will it shutdown? If it shuts down, how do we alter its
> configuration to tell it to use another drive for the logs?

It will stop running. It can't write anything. Just the same as if you
lost your data drive.

At that point you pull out your disaster recovery plan and go from here.

We've had a few cases where either the log or data disks went off-line and
it was just a matter of bringing them back online through the RAID
controller interface. SQL 2000 picked up where it left off.

> Also, what kind of throughput would we need to be doing to see
> any kind of benefit to making this change? It is easier to
> justify the expense of another disk or RAID setup if it is
> actually going to matter. ;-)
> Thanks all!
> Thomas|||"Greg D. Moore \(Strider\)" <mooregr_deleteth1s@.greenms.com> wrote in message news:<kStvc.34031$j24.13232@.twister.nyroc.rr.com>...
> "Thomas" <thomas-ggl-02@.data.iatn.net> wrote in message
> news:a9081691.0406021521.54c0f399@.posting.google.c om...
> > My question is, what happens if that secondary drive or array
> > completely fails. Let's say it melts. Assuming the OS doesn't
> > crash (Windows 2003 Server), what will SQL Server 2000 do when
> > the drive stops working and it is trying to write its data
> > logging to it? Will it continue to function and write alert
> > events? Will it shutdown? If it shuts down, how do we alter its
> > configuration to tell it to use another drive for the logs?
> It will stop running. It can't write anything. Just the same as if you
> lost your data drive.
> At that point you pull out your disaster recovery plan and go from here.
> We've had a few cases where either the log or data disks went off-line and
> it was just a matter of bringing them back online through the RAID
> controller interface. SQL 2000 picked up where it left off.

Let's imagine that this new RAID 1 for the logging goes down hard,
controller malfunction or what have you, and it will take a few days
to be repaired. In the meantime our data drive is working fine, and
we want to move the logging back to that array. You mentioned that
SQL Server would "stop running." If it isn't running, how would we
be able to update its configuration to change the location of the
logfiles?

Thanks for your feedback and advice!

Regards,
Thomas|||"Thomas" <thomas-ggl-01@.data.iatn.net> wrote in message
news:4f2cac50.0406030702.4308cd27@.posting.google.c om...
> "Greg D. Moore \(Strider\)" <mooregr_deleteth1s@.greenms.com> wrote in
message news:<kStvc.34031$j24.13232@.twister.nyroc.rr.com>...
> > "Thomas" <thomas-ggl-02@.data.iatn.net> wrote in message
> > news:a9081691.0406021521.54c0f399@.posting.google.c om...
> > > My question is, what happens if that secondary drive or array
> > > completely fails. Let's say it melts. Assuming the OS doesn't
> > > crash (Windows 2003 Server), what will SQL Server 2000 do when
> > > the drive stops working and it is trying to write its data
> > > logging to it? Will it continue to function and write alert
> > > events? Will it shutdown? If it shuts down, how do we alter its
> > > configuration to tell it to use another drive for the logs?
> > It will stop running. It can't write anything. Just the same as if you
> > lost your data drive.
> > At that point you pull out your disaster recovery plan and go from here.
> > We've had a few cases where either the log or data disks went off-line
and
> > it was just a matter of bringing them back online through the RAID
> > controller interface. SQL 2000 picked up where it left off.
> Let's imagine that this new RAID 1 for the logging goes down hard,
> controller malfunction or what have you, and it will take a few days
> to be repaired. In the meantime our data drive is working fine, and
> we want to move the logging back to that array. You mentioned that
> SQL Server would "stop running." If it isn't running, how would we
> be able to update its configuration to change the location of the
> logfiles?

Well, first of all, if you lose your log device, you have to do a restore
from backup in any case. At that point simply restore the backup to a
different device using the MOVE option.

Now, if your master DB and other system DBs are on the failed device, you
need to startup SQL server manually and specify on the command line where
they are.

MS has multiple KB articles on this.

Turn the question around... what happens if the RAID device with your DATA
fails? (ironically in some ways this can be EASIER to recover from assuming
you have good backups.)

> Thanks for your feedback and advice!
> Regards,
> Thomas

Logging server errors

How or where does one get *meaningful* error logs from SQL Server/SQL Agent?
The logs generated on SQL Server are wholly inadequate, unless I am missing
something. A sample - trying to find out why my Integrity Checks job failed
last night:
DBCC CHECKDB (gIQInternetMaster, repair_fast) executed by NV\SQL_USR found 4
errors and repaired 0 errors.
So I look in the Application Event log for the machine:
SQL Server Scheduled Job 'Integrity Checks Job for DB Maintenance Plan 'DB
Maintenance Plan gIQInternetMaster'' (0x834A8604584AB24AB32FDA8DF8B39468) -
Status: Failed - Invoked on: 2004-09-30 00:00:01 - Message: The job failed.
The Job was invoked by Schedule 35 (Schedule 1). The last step to run was
step 1 (Step 1).
Is there something in that message I'm missing?
Specify an output file in the jobstep. Note that this is in the job *step*.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Ron Hinds" <__NoSpam@.__NoSpamramac.com> wrote in message
news:emJg3EwpEHA.3980@.TK2MSFTNGP12.phx.gbl...
> How or where does one get *meaningful* error logs from SQL Server/SQL Agent?
> The logs generated on SQL Server are wholly inadequate, unless I am missing
> something. A sample - trying to find out why my Integrity Checks job failed
> last night:
> DBCC CHECKDB (gIQInternetMaster, repair_fast) executed by NV\SQL_USR found 4
> errors and repaired 0 errors.
> So I look in the Application Event log for the machine:
> SQL Server Scheduled Job 'Integrity Checks Job for DB Maintenance Plan 'DB
> Maintenance Plan gIQInternetMaster'' (0x834A8604584AB24AB32FDA8DF8B39468) -
> Status: Failed - Invoked on: 2004-09-30 00:00:01 - Message: The job failed.
> The Job was invoked by Schedule 35 (Schedule 1). The last step to run was
> step 1 (Step 1).
> Is there something in that message I'm missing?
>
>
|||Thank you!
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:%23MEtBywpEHA.324@.TK2MSFTNGP11.phx.gbl...
> Specify an output file in the jobstep. Note that this is in the job
*step*.[vbcol=seagreen]
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Ron Hinds" <__NoSpam@.__NoSpamramac.com> wrote in message
> news:emJg3EwpEHA.3980@.TK2MSFTNGP12.phx.gbl...
Agent?[vbcol=seagreen]
missing[vbcol=seagreen]
failed[vbcol=seagreen]
found 4[vbcol=seagreen]
'DB[vbcol=seagreen]
(0x834A8604584AB24AB32FDA8DF8B39468) -[vbcol=seagreen]
failed.[vbcol=seagreen]
was
>

Logging server errors

How or where does one get *meaningful* error logs from SQL Server/SQL Agent?
The logs generated on SQL Server are wholly inadequate, unless I am missing
something. A sample - trying to find out why my Integrity Checks job failed
last night:
DBCC CHECKDB (gIQInternetMaster, repair_fast) executed by NV\SQL_USR found 4
errors and repaired 0 errors.
So I look in the Application Event log for the machine:
SQL Server Scheduled Job 'Integrity Checks Job for DB Maintenance Plan 'DB
Maintenance Plan gIQInternetMaster'' (0x834A8604584AB24AB32FDA8DF8B39468) -
Status: Failed - Invoked on: 2004-09-30 00:00:01 - Message: The job failed.
The Job was invoked by Schedule 35 (Schedule 1). The last step to run was
step 1 (Step 1).
Is there something in that message I'm missing?
Specify an output file in the jobstep. Note that this is in the job *step*.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Ron Hinds" <__NoSpam@.__NoSpamramac.com> wrote in message
news:emJg3EwpEHA.3980@.TK2MSFTNGP12.phx.gbl...
> How or where does one get *meaningful* error logs from SQL Server/SQL Agent?
> The logs generated on SQL Server are wholly inadequate, unless I am missing
> something. A sample - trying to find out why my Integrity Checks job failed
> last night:
> DBCC CHECKDB (gIQInternetMaster, repair_fast) executed by NV\SQL_USR found 4
> errors and repaired 0 errors.
> So I look in the Application Event log for the machine:
> SQL Server Scheduled Job 'Integrity Checks Job for DB Maintenance Plan 'DB
> Maintenance Plan gIQInternetMaster'' (0x834A8604584AB24AB32FDA8DF8B39468) -
> Status: Failed - Invoked on: 2004-09-30 00:00:01 - Message: The job failed.
> The Job was invoked by Schedule 35 (Schedule 1). The last step to run was
> step 1 (Step 1).
> Is there something in that message I'm missing?
>
>
|||Thank you!
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:%23MEtBywpEHA.324@.TK2MSFTNGP11.phx.gbl...
> Specify an output file in the jobstep. Note that this is in the job
*step*.[vbcol=seagreen]
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Ron Hinds" <__NoSpam@.__NoSpamramac.com> wrote in message
> news:emJg3EwpEHA.3980@.TK2MSFTNGP12.phx.gbl...
Agent?[vbcol=seagreen]
missing[vbcol=seagreen]
failed[vbcol=seagreen]
found 4[vbcol=seagreen]
'DB[vbcol=seagreen]
(0x834A8604584AB24AB32FDA8DF8B39468) -[vbcol=seagreen]
failed.[vbcol=seagreen]
was
>

Logging server errors

How or where does one get *meaningful* error logs from SQL Server/SQL Agent?
The logs generated on SQL Server are wholly inadequate, unless I am missing
something. A sample - trying to find out why my Integrity Checks job failed
last night:
DBCC CHECKDB (gIQInternetMaster, repair_fast) executed by NV\SQL_USR found 4
errors and repaired 0 errors.
So I look in the Application Event log for the machine:
SQL Server Scheduled Job 'Integrity Checks Job for DB Maintenance Plan 'DB
Maintenance Plan gIQInternetMaster'' (0x834A8604584AB24AB32FDA8DF8B39468) -
Status: Failed - Invoked on: 2004-09-30 00:00:01 - Message: The job failed.
The Job was invoked by Schedule 35 (Schedule 1). The last step to run was
step 1 (Step 1).
Is there something in that message I'm missing?Specify an output file in the jobstep. Note that this is in the job *step*.
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Ron Hinds" <__NoSpam@.__NoSpamramac.com> wrote in message
news:emJg3EwpEHA.3980@.TK2MSFTNGP12.phx.gbl...
> How or where does one get *meaningful* error logs from SQL Server/SQL Agent?
> The logs generated on SQL Server are wholly inadequate, unless I am missing
> something. A sample - trying to find out why my Integrity Checks job failed
> last night:
> DBCC CHECKDB (gIQInternetMaster, repair_fast) executed by NV\SQL_USR found 4
> errors and repaired 0 errors.
> So I look in the Application Event log for the machine:
> SQL Server Scheduled Job 'Integrity Checks Job for DB Maintenance Plan 'DB
> Maintenance Plan gIQInternetMaster'' (0x834A8604584AB24AB32FDA8DF8B39468) -
> Status: Failed - Invoked on: 2004-09-30 00:00:01 - Message: The job failed.
> The Job was invoked by Schedule 35 (Schedule 1). The last step to run was
> step 1 (Step 1).
> Is there something in that message I'm missing?
>
>|||Thank you!
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:%23MEtBywpEHA.324@.TK2MSFTNGP11.phx.gbl...
> Specify an output file in the jobstep. Note that this is in the job
*step*.
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
>
> "Ron Hinds" <__NoSpam@.__NoSpamramac.com> wrote in message
> news:emJg3EwpEHA.3980@.TK2MSFTNGP12.phx.gbl...
> > How or where does one get *meaningful* error logs from SQL Server/SQL
Agent?
> > The logs generated on SQL Server are wholly inadequate, unless I am
missing
> > something. A sample - trying to find out why my Integrity Checks job
failed
> > last night:
> >
> > DBCC CHECKDB (gIQInternetMaster, repair_fast) executed by NV\SQL_USR
found 4
> > errors and repaired 0 errors.
> >
> > So I look in the Application Event log for the machine:
> >
> > SQL Server Scheduled Job 'Integrity Checks Job for DB Maintenance Plan
'DB
> > Maintenance Plan gIQInternetMaster''
(0x834A8604584AB24AB32FDA8DF8B39468) -
> > Status: Failed - Invoked on: 2004-09-30 00:00:01 - Message: The job
failed.
> > The Job was invoked by Schedule 35 (Schedule 1). The last step to run
was
> > step 1 (Step 1).
> >
> > Is there something in that message I'm missing?
> >
> >
> >
>

Logging of logon success filling up logs.

How can I turn off the logging of succesfull user logon to the databases?
This is filling up both the SQL logs and the Application event logs.
Event Type: Information
Event Source: MSSQLSERVER
Event Category: (4)
Event ID: 17055
Date: 12/07/2003
Time: 2:14:14 PM
User: N/A
Computer: ***
Description:
18454 :
Login succeeded for user '*********'. Connection: Non-Trusted.
--
John Tolmachoff
MCSE, CSSA
Owner Consultant/Engineer
eServices For YouIn enterprise manager server properties ecurity set the audit level to
not log successful logons.
Nigel Rivett (SQL Server MVP)
www.nigelrivett.net
*** Sent via Developersdex http://www.developersdex.com ***
Don't just participate in USENET...get rewarded for it!