Hi Don,

dsmerror.log may contain further information. Are there
any messages in dsmerror.log that coincide with the time(s)
you attempted the registry backup? If you are not sure,
recreate the problem, then check dsmerror.log for any
messages with current timestamps.

If the error log shows a Win32 return code of "32", then
it could be that the registry backup files are being bound
to a management class with a copygroup serialization setting
of STATIC. Try changing the serialization to SHRSTATIC.

Another possibility might be APAR IC22283, which was fixed
in client version 3.1.0.6. Your message is not the same as
documented in the APAR, but it's at least worth checking
for the possibility. Look in the C:\WINDOWS directory for
a file called ADSMTEMP. The file would have the S, H, and
R attributes. If you use Windows Explorer to try to find
it, be sure the Windows Explorer options are configured to
show *all* files (including hidden and system files).

If you do find this file, it was probably left over from a
prior, aborted registry backup attempt. Turn off the
S, H, and R attributes, then retry the registry backup.
This should act as a work-around until you get the chance
to upgrade your client.

Best regards,

Andy

Andy Raibeck
IBM Storage Systems Division
ADSM Client Development
e-mail: storman AT us.ibm DOT com
"The only dumb question is the one that goes unasked."

My Windows 95 V3.R1.L0.5 clients keep running into ANS5166E Error Saving
Registry Key problems causing the backup process to fail.

What causes it and how do we get around it short of BACKUPREGISTRY NO in
the
dsm.opt file?

 -----------------------------------------------------------
   Don Coleman,
   Queen's University Information Technology Services
   Kingston, Ont. Canada  K7L 3N6
   Tel: (613) 533-2034  Fax: (613) 533-2168
   Email: Coleman AT Post.QueensU DOT CA