Tim,

I haven't heard back from Level 2.  I don't even know what APAR it is given.
The scheduler fails to start the first time after we installed the 5.1.1
client on a Windows 2000 server (not Professional).  The event number in the
event log is
7031  The TSM scheduler service terminated unexpectedly

After the machine reboots, the scheduler doesn't start even though it is set
to auto.  The event number is
7022  The TSM scheduler service hung on starting

Starting it manually then after works.

We can recreate it every time the machine boots.  This is a new Windows box
with a new w2k server installed on it.

Eliza

>
> Hi Eliza:
>
> Do you have any details on this?  My problem is still open, they are asking
> for a bunch of traces.
>
> If you have details, I was wondering if my problem is the same.
>
> Thanks,
>
> Tim Rushforth
> City of Winnipeg
>
> -----Original Message-----
> From: Eliza Lau [mailto:lau AT VTCAT.CC.VT DOT EDU]
> Sent: August 14, 2002 9:57 AM
> To: ADSM-L AT VM.MARIST DOT EDU
> Subject: Re: 5.1.1 Windows 2000 scheduler won't start
>
> Just heard from Level 2 support.  It is a bug since 4.2.  An APAR will be
> assigned to the problem.  4.2 has been out for a while.  Why Tivoli didn't
> know about this?  It is so obvious.  The  scheduler didn't start the first
> time we installed it.
>
> Eliza
>