We were getting similiar result due to a problem with reclaimations and
corrupted data in the database for some clients.  This situation and
utilities to deal with it are documented in the install READMEs for ADSM.
You may want to run an 'AUDIT RECLAIM' command to find out if this is your
case.  If it is, you will know very quickly, and if it is not, at least
you've eliminated that as a problem source.

> -----Original Message-----
> From: Lisa Galindo [SMTP:ldgalindo AT DSTSYSTEMS DOT COM]
> Sent: Wednesday, May 12, 1999 2:27 PM
> To:   ADSM-L AT VM.MARIST DOT EDU
> Subject:      Error 0xc0000005 on the Windows NT ADSM Client
>
> ADSM'ers,
>      We are receiving a very general error , 0xc0000005 at 0x61626174 in
> dsmc.exe, when attempting to restore a Windows NT server.   It  usually
> occurs
> at about 8.3M into the restore.  We don't find any clues in the DSMERROR
> log nor
> the Activity log.   I have supplied all of the information to IBM and
> haven't
> heard back, yet.    We can reproduce the error anytime.   We don't receive
> this
> error on every server.  It happens only on a few, but can be reproduced on
> those
> servers.  Any clues?
>      Lisa