I have two TSM servers Win2K at 4.1.5 and AIX 433 at 4.1.4.5 with clients at 4.1.3 across the board. I get this error for the Windows clients consistantly but not the AIX clients. I have reported this to Tivoli but their first line support person is insisting that there is a comms loss which will be relfected in the tsm error log (but isn't). This error occurs when doing the FIRST incremental or an archive and doesn't appear to occur in subsequent incrementals. If anyone has an apar or reference that I can pass back to the Tivoli support person, I would appreciate it.
George Lesho AFC Enterprises "Rushforth, Tim" <[EMAIL PROTECTED]>@VM.MARIST.EDU> on 01/09/2002 03:06:10 PM Please respond to "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> Sent by: "ADSM: Dist Stor Manager" <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] cc: (bcc: George Lesho/Partners/AFC) Fax to: Subject: Re: Return code=4 on scheduled backap When I tested the 4.2.1.15 client, the bug was fixed. Are you sure it is not a real failed schedule? Any error messages in dsmerror.log or previously in dsmsched.log? Tim Rushforth City of Winnipeg -----Original Message----- From: Guillaume Gilbert [mailto:[EMAIL PROTECTED]] Sent: Wednesday, January 09, 2002 3:00 PM To: [EMAIL PROTECTED] Subject: Return code=4 on scheduled backap Hello We just installed a 4.2.1.15 client on an NT box and now we get the bug in the event reporting : 2002-01-08 17:31:06 --- SCHEDULEREC STATUS END 2002-01-08 17:31:06 --- SCHEDULEREC OBJECT END FEN_QUOT 2002-01-08 17:00:00 2002-01-08 17:31:06 ANS1512E Scheduled event 'FEN_QUOT' failed. Return code = 4. which reports to the server that the schedule has failed. I searched adsm.org and this bug was supposed to be fixed in 4.2.1.15 but it clearly isn't. Is there a workaound to this bug or do I have to live with it until it is fixed? The server is at 4.1.3 on AIX 4.3.3 Thanks for the help Guillaume Gilbert Storage administrator CGI Group Montreal
