Thank you for reminding me. I work on sooooo many different systems and
platforms, that sometimes I loose track !

If there was some kind of "problem" with the system, I would have thought
the problem would occur frequently/regularly, not once in a blue-moon ?





Richard Sims <rbs AT BU DOT EDU>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
02/24/2005 05:36 PM
Please respond to
"ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>


To
ADSM-L AT VM.MARIST DOT EDU
cc

Subject
Re: Windows Backup abort #237






Zoltan -

When Andy advised you on this error condition when you encountered it
last June, you had some rather imposing associated errors in the server
Activity Log. Perhaps there is new info there now which could help. I
believe you'll have to contact TSM Support for resolution. It may be
that you have "foreign matter" or corruption within that system object
area. (Maybe chkdsk or the like could help? I'm no Windows expert.)

BTW, the context of the ANS0343E message is explained in the TSM
3.7&4.1 Technical Guide redbook. (Search on "leader".)

    Richard Sims

On Feb 24, 2005, at 12:06 PM, Zoltan Forray/AC/VCU wrote:

> I hve search IBM.COM but have not found an APAR addressing this error:
>
> 02/23/2005 20:12:50 findAbortState: Unknown abort #237 from the server
> 02/23/2005 20:12:50 ANS1228E Sending of object
> '\\covecsys\c$\WINDOWS\repair\Backup\ServiceState\EventLogs\AppEvent.Ev
> t'
> failed
> 02/23/2005 20:12:50 ANS0343E An invalid operation was attempted on a
> group
> leader or group member.
>
> This is a 2K3 box with 5.2.3.4 TSM client.
>
> My first inclincation is to upgrade the client to 5.3.0 but I would
> like
> to know that the problem is addressed in this upgrade.
>
> Anyone else seen this or can tell me for sure the 5.3 client will
> fix/address this hickup ?
>
> Any suggestions on what the "abort #237" means ?