ADSM-L

Re: 5.1.1 Windows 2000 scheduler won't start

2002-08-15 09:22:48
Subject: Re: 5.1.1 Windows 2000 scheduler won't start
From: "Adams, Matt (US - Hermitage)" <maadams AT DELOITTE DOT COM>
To: ADSM-L AT VM.MARIST DOT EDU
Date: Thu, 15 Aug 2002 07:53:33 -0500
Thanks Eliza.  I am in the same boat as Tab, I have experienced it
intermittently, but haven't reported it because we rarely boot our W2K
servers.

If you have the time, and think about it, let us know the APAR number
assigned.

Thanks,

Matt Adams
Tivoli Storage Manager Team
Hermitage Site Tech
Deloitte & Touche USA LLP



-----Original Message-----
From: Eliza Lau [mailto:lau AT VTCAT.CC.VT DOT EDU]
Sent: Wednesday, 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

>
> Eliza,
>
> Just for the record, I'm seeing the same behavior in the TSM 4.2.2 client
> on Windows 2000 Server.
>
> I haven't done anything about it yet because the service does start
> eventually, and we almost never reboot servers.
>
> Tab Trepagnier
> TSM Administrator
> Laitram Corporation
>
>
>
>
>
>
>                     Eliza Lau
>                     <lau AT VTCAT DOT CC.       To:     ADSM-L AT VM.MARIST 
> DOT EDU
>                     VT.EDU>              cc:
>                     Sent by:             Subject:     Re: 5.1.1 Windows
2000 scheduler won't
>                     "ADSM: Dist           start
>                     Stor Manager"
>                     <ADSM-L AT VM DOT MAR
>                     IST.EDU>
>
>
>                     08/09/2002
>                     01:58 PM
>                     Please respond
>                     to "ADSM: Dist
>                     Stor Manager"
>
>
>
>
>
>
> Ours is also a brand new W2K server with no previous version of TSM client
> installed.
>
> Eliza
>
> >
> > In our case, the servers that are failing are brand new servers, never
> had
> > an older client installed.
> >
> > As a bypass, we've set the recovery option on the service to restart on
> the
> > first failure - seems to work so far.
> >
> > Tim
> > -----Original Message-----
> > From: Halvorsen Geirr Gulbrand [mailto:gehal AT WMDATA DOT COM]
> > Sent: August 9, 2002 1:32 AM
> > To: ADSM-L AT VM.MARIST DOT EDU
> > Subject: Re: 5.1.1 Windows 2000 scheduler won't start
> >
> > Hello,
> > I've seen this when upgrading from one level to another, (in my case
from
> > 4.1.x to 4.2.x).
> > I used DSMCUTIL to remove the service, then started the client, and from
> > utilities, installed scheduler service again, importing same opt-file,
> and
> > it worked fine.
> > I don't know if this is the case for v. 5.1.x, but it's worth a
> try...maybe?
> >
> > Rgds.
> > Geirr G. Halvorsen
> >
> > -----Original Message-----
> > From: Boireau, Eric (MED) [mailto:eric.boireau AT MED.GE DOT COM]
> > Sent: 9. august 2002 07:35
> > To: ADSM-L AT VM.MARIST DOT EDU
> > Subject: Re: 5.1.1 Windows 2000 scheduler won't start
> >
> >
> > I have the same kind of issue on my Laptop with Win2K Pro and TSM
5.1.0.1
> > Client. It sayd that the service hangs at startup. But the service is
> > started and run well
> >
> > Regards,
> > Eric
> > -----Original Message-----
> > From: Rushforth, Tim [mailto:TRushfor AT CITY.WINNIPEG.MB DOT CA]
> > Sent: Friday, August 09, 2002 3:27 AM
> > To: ADSM-L AT VM.MARIST DOT EDU
> > Subject: Re: 5.1.1 Windows 2000 scheduler won't start
> >
> >
> > Hi Eliza:
> >
> > We are experiencing this on SOME of our Windows 2000 Servers.  On these
> > servers the Schedule service fails SOMETIMES on reboot. On other 2000
> > servers we have never had a problem.  I've opened a problem with Tivoli
> on
> > this (PMR 40368).  The only similarity for machines that are failing
that
> I
> > can see (so far!) is that they are all multi-processor.
> >
> > We are running 5.11 clients, server is windows 2000 4.2.0.  (We've just
> > started to roll out the 5.11 client - all looked good in testing!)
> >
> > Tim Rushforth
> > City of Winnipeg
> >
> > -----Original Message-----
> > From: Eliza Lau [mailto:lau AT VTCAT.CC.VT DOT EDU]
> > Sent: August 8, 2002 11:39 AM
> > To: ADSM-L AT VM.MARIST DOT EDU
> > Subject: 5.1.1 Windows 2000 scheduler won't start
> >
> > We are experiencing problems with the TSM scheduler not starting on
> Windows
> > 2000 servers.
> >
> > A user installed TSM client 5.1.1 on a Windows 2000 server with SP2 and
> all
> > hotfoxes.  After the scheduler is installed, the user got the following
> > message:
> >   An error occurred while starting the service
> >
> > He then pressed OK and a message box said
> >   Scheduler successfully installed
> >
> > When he looked at the Scheduler service, it was installed but not
> started.
> > He started it manually and things worked fine from then on. The error in
> the
> > event log:  event 7031
> >         The TSM scheduler service terminated unexpectedly
> >
> > After the machine reboots, the schedule doesn't start even though it is
> set
> > to automatic.  In the event log:  event 7022
> >         The TSM scheduler service hung on starting
> >
> > After a manual start, the scheduler works again.  He can reproduce it
> > everytime.  This only happens on our Windows 2000 server machines.  We
> have
> > other Windows 2000 Professional machines that have no problems.
> >
> > server: AIX 4.3.3, TSM 4.2.1.15
> > client: Windows 2000 server with SP2 and all hotfixes
> >         TSM client 5.1.1
> >
> > Eliza Lau
> > Virginia Tech Computing Center
> > 1700 Pratt Drive
> > Blacksburg, VA 24060
> > lau AT vt DOT edu
> >
>
- This message (including any attachments) contains confidential information
intended for a specific individual and purpose, and is protected by law.  -
If you are not the intended recipient, you should delete this message and
are hereby notified that any disclosure, copying, or distribution of this
message, or the taking of any action based on it, is strictly prohibited.