ANS5280E Object enumeration from a file set or file list failed

[cfhoffmann]

After upgrading to version 5.5.0.0 on Windows 2003 I'm getting ANS5280E errors during scheduled incremental backups and then the backup fails. Any ideas ? It doesn't seem to happen when I manually perform an incremental backup using dsmc.

06-12-2007 20:06:11 ANS5280E Object enumeration from a file set or file list failed.
06-12-2007 20:06:11 --- SCHEDULEREC STATUS BEGIN
06-12-2007 20:06:11 Total number of objects inspected: 9,075
06-12-2007 20:06:11 Total number of objects backed up: 5
06-12-2007 20:06:11 Total number of objects updated: 0
06-12-2007 20:06:11 Total number of objects rebound: 0
06-12-2007 20:06:11 Total number of objects deleted: 0
06-12-2007 20:06:11 Total number of objects expired: 2
06-12-2007 20:06:11 Total number of objects failed: 0
06-12-2007 20:06:11 Total number of subfile objects: 0
06-12-2007 20:06:11 Total number of bytes transferred: 20.80 KB

 

[hogmaster]

Can this be ASR related?
Try to exclude ASR from your scheduled backup. If this works then the account that the scheduled backup is running as is lacking the right privilieges.

When you do a manual backup do you backup the ASR (do dsmc inc)?

/regards Daniel

 

[Tyke]

We have a PMR open with IBM on what sounds a very similar problem. Do you get any other errors immediately prior to the error in the DSMERROR.LOG?
eg:

07-12-2007 14:04:58 ANS5279E Error processing '\\**********\c$\WINDOWS\Repair\Backup\BootableSystemState\Registry\default': file not found.
07-12-2007 14:04:58 ANS1999E Incremental processing of '**********\SystemState\NULL\System State\SystemState' stopped.
07-12-2007 14:05:03 ANS5280E Object enumeration from a file set or file list failed.

 

[cfhoffmann]

It doesn't appear to be ASR related, Hogmaster; it fails with/without ASR. IBM tells me there are a few similar PMRs, Tyke, and yes we get similar errors although not always SystemState.

 

[cfhoffmann]

I think the problem may be the snapshot provider. After the upgrade to version 5.5 open file support was disabled even though before the upgrade the version 5.4 had open file support enabled using LVSA. I added:

SNAPSHOTPROVIDERFS VSS
SNAPSHOTPROVIDERIMAGE VSS

to dsm.opt and scheduled backups are working again.

 

[Tyke]

Yes - that sorted it for me too. It seems that IBM recommends using VSS for OFS (instead of LVSA) with 5.5 on all Windows platforms except XP.

Tyke.

 

[Rigido]

Did someone sorted this out?
I tried both with SNAPSHOTPROVIDERFS VSS and SNAPSHOTPROVIDERFS NONE (and for SNAPSHOTPROVIDERIMAGE too), but didn't solve.
It is really strange because the systemstate backup worked 'til Saturday and nothing changed on the system.

 

[spidermila]

We have this problem also. Any additional information appreciated.

 

[johansen]

there are some w2003 sp1+sp2 servers in our environment where we face the same problems, but only when backing up the systemstate.

excluding systemstate (f.e. 'DOMAIN C: -SYSTEMSTATE') will let the backup end successfully. I also had a case opened at TSM support but this never led to a satisfying situation.

also tried to use latest client vers (5.5.1.10) with openfile support etc but also no luck.

 

[thirudan]

Re install the TSM client

i do have a same problem .

Re-instal the TSM client and i fixed the issue .

Regards
Thirudan

there are some w2003 sp1+sp2 servers in our environment where we face the same problems, but only when backing up the systemstate.

excluding systemstate (f.e. 'DOMAIN C: -SYSTEMSTATE') will let the backup end successfully. I also had a case opened at TSM support but this never led to a satisfying situation.

also tried to use latest client vers (5.5.1.10) with openfile support etc but also no luck.

 

[surreytj]

I did this to fix it

[FONT=Calibri,Calibri][FONT=Calibri,Calibri]http://support.microsoft.com/kb/940184[/FONT][/FONT]​