Sorry this is a bit late, but it might help someone some day. Instead of just having a command schedule defined as: "c:\lala\something.exe yatta yatta"
It can be very helpful to redirect the process's stdout and stderr a log file: "c:\lala\something.exe yatta yatta >c:\something.log 2>&1" This will nearly always give you the actual error message issued by the process, often saving you the effort of tracing or tracking down poorly reported return codes. In addition to TSM-related errors, it'll even report why Windows thought something.exe wasn't executable, e.g., it couldn't be found. ________________________________ Alex Paschal Storage Solutions Engineer MSI Systems Integrators (503) 943-6919 - Office ________________________________ Your Business. Better. -----Original Message----- From: ADSM: Dist Stor Manager [mailto:ads...@vm.marist.edu] On Behalf Of Del Hoobler Sent: Tuesday, July 14, 2009 8:12 AM To: ADSM-L@VM.MARIST.EDU Subject: Re: [ADSM-L] Scheduled Exc backup failing on -1073741819 I did not say a permissions problem on the DSM.OPT file. I was referring to the login permission for TDPEXCC to access the correct AD objects required for backup. Good idea to get the trace... especially since your other machines are working with the exact same setup. If you still have issues, you should place a call with IBM Service. Thanks, Del This message (including any attachments) is intended only for the use of the individual or entity to which it is addressed and may contain information that is non-public, proprietary, privileged, confidential, and exempt from disclosure under applicable law or may constitute as attorney work product. If you are not the intended recipient, you are hereby notified that any use, dissemination, distribution, or copying of this communication is strictly prohibited. If you have received this communication in error, notify us immediately by telephone and (i) destroy this message if a facsimile or (ii) delete this message immediately if this is an electronic communication. Thank you.
