error 18456 when running job

sql2k sp3
Ive got a job that creates a folder both on the local box
and on the remote box. This job has run every nite
successfully for a few weeks now. Last nite it failed with
message: Login failed for user 'NT AUTHORITY\ANONYMOUS
LOGON'. [SQLSTATE 28000] (Error 18456). The step failed.
I havent changed anything security or services related.
The sql services for both boxes run in the same domain
admin account.
Any ideas?
Thanks, Chris.Try making the job owner sa. I've seen this and it ideespeared when I did that.
--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as ugroup=microsoft.public.sqlserver
"chris" <chrisr@.fingps.com> wrote in message news:034901c36693$a4ce8750$a501280a@.phx.gbl...
> sql2k sp3
> Ive got a job that creates a folder both on the local box
> and on the remote box. This job has run every nite
> successfully for a few weeks now. Last nite it failed with
> message: Login failed for user 'NT AUTHORITY\ANONYMOUS
> LOGON'. [SQLSTATE 28000] (Error 18456). The step failed.
> I havent changed anything security or services related.
> The sql services for both boxes run in the same domain
> admin account.
> Any ideas?
> Thanks, Chris.

Error 1222 Lock request

I received the Error 1222 lock request time out period
when trying to open SQL Server Current Activity folder
under the Management folder to display locks.
This was caused by several locks.
This made it very difficult to resolve the locks without
the GUI.
What would cause the SQL Server GUI to be unable to
display the locks?
Thank You,
Mickey Autry
mautry@.ev1.netThat's know to happen when you have a lot of locks. You can
use Query Analyzer to execute sql statments and system
stored procedures to view the same info you look at in the
Current Activity part of Enterprise Manager. Check books
online for more information on sp_lock, sp_who, sp_who2 and
the sysprocesses table.
-Sue
On Tue, 23 Sep 2003 15:41:17 -0700, "Mickey"
<mautry@.ev1.net> wrote:
>I received the Error 1222 lock request time out period
>when trying to open SQL Server Current Activity folder
>under the Management folder to display locks.
>This was caused by several locks.
>This made it very difficult to resolve the locks without
>the GUI.
>What would cause the SQL Server GUI to be unable to
>display the locks?
>Thank You,
>Mickey Autry
>mautry@.ev1.net
>

error

Hi

The company I currently work for backups its SQL databases by

dumping them into a shared folder on nearby sysem. Once in a blue moon

the following error appears on the screen of the SQL server:

Windows - Delayed Write Failed

Windows was unable to save all the data for the file

\Device\LanmanRedirector\10.100.20.7\backup\logs\DB backup 4 hour cycle to remotesrv

storage4_200608150615.txt. The data has been lost. This error may be caused by

a failure of your computer hardware or network connection. Please try to save

this file elsewhere.

There are other processes that talk to other shares (on the same drive

on the same remote system) and none of them gives me the above

error. What more both systems are on the same LAN and IP subnet that is

very lightly used. The network cables are all high grade CAT6

cable (machine cripmed). I'm not a windows/SQL

Administrator (Unix is my background), so if I'm asking the wrong

questions in the wrong forum please kindly redirect me to the right

forum.

Why does this error popup?

TIA

Paolo

One place you might try is to take a look at the Array Controller Read/Write Cache ratio on the target server. If the controller is set to 100% Read, this type of error could happen. You could also take a look at the array controller on the server initiating the backups. The controller should never be set to 100% Read, although even though it may be, it doesn't allow no Write caching. However, if there is too much data being written to the array and there isn't enough Write cache, you could experience the type of failures you are seeing. Also make sure there are no failed disks in the array. You may also want to make sure that all of the storage drivers are up to date as well.