Registry backup errors on NT file server

TSMers,

I recently upgraded a Windows NT 4.0 SP6 file server from TSM client 4.1.0
to 4.1.3.  After the upgrade I began receiving these messages in the
dsmerror.log.  It appears the registry is backing up fine, but these errors
appear on every scheduled backup.  Has anyone seen these errors before?  Is
this something to be concerned about?  Any help would be greatly
appreciated.


04/01/2002 00:08:45 getFileShareInfo(): connectRegistry() for machine x
failed, rc=5. Registry will not be backed up. Error is ignored.
04/01/2002 00:08:50 getFileShareInfo(): connectRegistry() for machine x
failed, rc=5. Registry will not be backed up. Error is ignored.
04/01/2002 00:08:51 getFileShareInfo(): connectRegistry() for machine x
failed, rc=5. Registry will not be backed up. Error is ignored.
04/01/2002 00:08:57 getFileShareInfo(): connectRegistry() for machine x
failed, rc=5. Registry will not be backed up. Error is ignored.
04/01/2002 00:13:24 getFileShareInfo(): connectRegistry() for machine x
failed, rc=5. Registry will not be backed up. Error is ignored.
04/01/2002 00:15:32 getFileShareInfo(): connectRegistry() for machine x
failed, rc=5. Registry will not be backed up. Error is ignored.
04/01/2002 00:16:15 getFileShareInfo(): connectRegistry() for machine x
failed, rc=5. Registry will not be backed up. Error is ignored.
04/01/2002 00:17:29 getFileShareInfo(): connectRegistry() for machine x
failed, rc=5. Registry will not be backed up. Error is ignored.
04/01/2002 01:32:12 ANS1485E Schedule log pruning failed.
04/01/2002 01:32:12 ANS1485E Schedule log pruning failed.

Thanks

Todd M. Pucky
The Timken Company
Global Information Systems
Programmer/Analyst
330.471.4583
puckyt AT timken DOT com



**********************************************************************
This message and any attachments are intended for the
individual or entity named above. If you are not the intended
recipient, please do not forward, copy, print, use or disclose this
communication to others; also please notify the sender by
replying to this message, and then delete it from your system.

The Timken Company
**********************************************************************