I'm seeing this quite a bit on a very busy 4.2.2.13 server - and sometimes at about the same time we see ANS1301E on the client along with an ANE4987E with file from the \WINNT\system32\ directory.
My suspicion is that what's happening is that a file that is now considered a "system object" is also being processed by the client as a regular file system object. Just an uneducated guess, but anything is likely considering how big a mess this last change in handling system objects has been. -----Original Message----- From: Gill, Geoffrey L. [mailto:GEOFFREY.L.GILL@;SAIC.COM] Sent: Friday, November 01, 2002 2:53 PM To: [EMAIL PROTECTED] Subject: TSM 5.1.5.1 Failed Backups > -----Original Message----- > From: John Naylor [mailto:john.naylor@;SCOTTISH-SOUTHERN.CO.UK] > Sent: Thursday, October 31, 2002 9:14 AM > To: [EMAIL PROTECTED] > Subject: Re: TSM 5.1.5.1 backups last night > > There have been some problems with resource waiters and locks. > It might be worth upping your server Resource Timeout value to 100 Support asked me to change it again, from 60 to 90 this time, so I went ahead and made it 100. I'm still having problems with Failed backups reporting error ANR0918E. It's a random thing and although the clients are mostly 4.1, and they tell me they won't look at them, I lucked out, or NOT, and have it showing up on 5.1 clients too. 10/31/02 23:51:22 ANR0918E Inventory Query Backup for node XXXXXXX terminated - lock conflict. Geoff Gill TSM Administrator NT Systems Support Engineer SAIC E-Mail: [EMAIL PROTECTED] Phone: (858) 826-4062 Pager: (877) 905-7154
