Wendy, thanks your suggestion worked.  In this case  I was lucky that the
user did not mind his backup/archive get deleted from the server but the
solution to this problem should not come to deleting users backup/archive
from server.  I hope ADSM developers are aware of this problem and are doing
something about it.

Abi
University of California

At 04:00 PM 2/26/97 EST, you wrote:
>Abi Admassu <Abi.Admassu AT UCOP DOT EDU> reports:
>>error log:
>>
>>02/25/1997 22:26:07  ANS6604S NULL character found in the name of
folder/file ?
>------ clip -----
>>02/25/1997 22:26:39 Retry # 1  Expiring-->                 70 Thwaites's
>>place:Communications:Anarchie-150:  ** Unsuccessful **
>>02/25/1997 22:26:40 ANS4228E Sending of object 'Thwaites's
>>place:Communications:Anarchie-150:' failed
>>02/25/1997 22:26:40 Active object not found
>
>We ran into precisely this problem in November 1995 in ADSM 2.1.0.1. The
>failing file has somehow gotten a null character in its name (see the
>message in the error log file: the question mark indicates where the null
>character is). ADSM 2.1.0.2 and higher detect the null character and put
>the question mark in the error log; earlier versions tell you nothing.
>
>There is no way to delete just the affected object from the ADSM database.
>
>To get backups working, log on to an ADSM *administrator* client (if you
>do filespace deletion from a backup client you delete all *archived*
>files as well as the backups), delete the filespace, and back the whole
>system up again.
>
>Wendy Alberg                      Phone:  607/255-2672
>Network & Computer Systems        Fax:    607/255-6523
>Cornell Information Technologies  E-mail: wa10 AT cornell DOT edu
>Cornell University, Ithaca, NY    WWW:    http://dwrgi.cit.cornell.edu/
>
>