Hmmmm.... Try doing the following:
1) Delete the existing c:\adsm.sys directory structure. 2) Add the following to the client options: exclude.dir c:\adsm.sys 3) Retry the system object backup. Regards, Andy Andy Raibeck IBM Software Group Tivoli Storage Manager Client Development Internal Notes e-mail: Andrew Raibeck/Tucson/[EMAIL PROTECTED] Internet e-mail: [EMAIL PROTECTED] IBM Tivoli Storage Manager support web page: http://www-306.ibm.com/software/sysmgmt/products/support/IBMTivoliStorageManager.html The only dumb question is the one that goes unasked. The command line is your friend. "Good enough" is the enemy of excellence. "ADSM: Dist Stor Manager" <ADSM-L@VM.MARIST.EDU> wrote on 2005-11-29 07:09:04: > Hi *SMers, > > Client - TSM 5.2.4.4 on a W2K SP4 server. > Server - TSM 5.2.4.5 on a W2K SP4 server. > > I'm experiencing a regular backup failure of the system objects and the > information returned to me from TSM is not really directing me towards a > cause. > > Dsmerror.log contains: > 11/29/2005 13:34:08 ANS1487E Backing up WMI repository failed. No files > will be backed up. > 11/29/2005 13:34:14 Return code 3029 unknown > 11/29/2005 13:34:14 Unknown system error > Please check the TSM Error Log for any additional information > > Dsmsched.log has less.. > > Is there any documentation anywhere which brings some kind of meaning to > "Return code 3029 unknown". > > Any assistance greatly appreciated. > > Regards > Matthew > > TSM Consultant > ADMIN ITI > Rabobank International > 1 Queenhithe, London > EC4V 3RL > > > _____________________________________________________________ > > This email (including any attachments to it) is confidential, > legally privileged, subject to copyright and is sent for the > personal attention of the intended recipient only. If you have > received this email in error, please advise us immediately and > delete it. You are notified that disclosing, copying, distributing > or taking any action in reliance on the contents of this information > is strictly prohibited. Although we have taken reasonable > precautions to ensure no viruses are present in this email, we > cannot accept responsibility for any loss or damage arising from the > viruses in this email or attachments. We exclude any liability for > the content of this email, or for the consequences of any actions > taken on the basis of the information provided in this email or its > attachments, unless that information is subsequently confirmed in > writing. If this email contains an offer, that should be considered > as an invitation to treat. > _____________________________________________________________