Antwort: Re: Scheduler fails on Windows 2000 and 2003 without a message

2004-04-28 12:38:45
Subject: Antwort: Re: Scheduler fails on Windows 2000 and 2003 without a message
From: Karin Dambacher <karin.dambacher AT EMPRISE DOT DE>
Date: Wed, 28 Apr 2004 18:11:02 +0200
Hi Andy,

the scheduler service seems to be started (in the service window there is
"started"), but it hangs and has to be restarted. After restarting the next
backup will run fine, but the second or third after restarting hangs in the
way described. Some time it is not possible to restart the scheduler
service, while the journal service is running. So we have to stop
journaling and then restarting the scheduler and restart the journal.

Best regards, Karin

|         |           Andrew Raibeck   |
|         |           <storman AT US DOT IBM.C|
|         |           OM>              |
|         |           Gesendet von:    |
|         |           "ADSM: Dist Stor |
|         |           Manager"         |
|         |           <[email protected]|
|         |           .EDU>            |
|         |                            |
|         |                            |
|         |           28.04.2004 15:03 |
|         |           Bitte antworten  |
|         |           an "ADSM: Dist   |
|         |           Stor Manager"    |
  |       An:       ADSM-L AT VM.MARIST DOT EDU                                 
  |       Kopie:    (Blindkopie: Karin Dambacher/Emprise)                       
  |       Thema:    Re: Scheduler fails on Windows 2000 and 2003 without a 
message                                                              |

Hello Karin,

Is the scheduler "failing" or being "missed"? There is a difference:
"Failed" means that the scheduled event began, but encountered an error
condition that prevented it from completing successfully. "Missed" means
that the scheduled event never began. For example, if the scheduler is not
running on the client, then of course it can not execute its scheduled
events; nor can it report that it did not run.

>From your description, it may be that a "missed" schedule is what needs to
be investigated. On the client machines that missed their scheduled,
verify that the scheduler service is started. Check the dsmsched.log and
dsmerror.log to verify that the scheduler was able to successfully contact
the server and query its next scheduled event. For that matter, make sure
that you can perform manual client operations as well, just to verify
basic functionality.

Also check out the TSM problem determination guide at
There is a link called "Scheduling" that might have some useful



Andy Raibeck
IBM Software Group
Tivoli Storage Manager Client Development
Internal Notes e-mail: Andrew Raibeck/Tucson/[email protected]
Internet e-mail: storman AT DOT com

The only dumb question is the one that goes unasked.
The command line is your friend.
"Good enough" is the enemy of excellence.

Karin Dambacher <karin.dambacher AT EMPRISE DOT DE>
Sent by: "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU>
04/28/2004 04:58
Please respond to
"ADSM: Dist Stor Manager"


Scheduler fails on Windows 2000 and 2003 without a message


on some Windows NT, 2000 and Windows 2003 server the TSM scheduler fails
without a message in the eventlog. In the morning, I see the
of the client schedule. That is all.
Other servers with the same configuration run well.

TSM Server 5.2.2 on AIX 5.1
Windows: TSM Client 5.1.5.x and TSM 5.1.6.x with newest patch

Best regards, Karin

Diese e-Mail einschließlich ihrer Anhänge ist vertraulich. Wir bitten,
fehlgeleitete e-Mail
unverzüglich vollständig zu löschen und uns eine Nachricht zukommen zu
lassen. Wir haben die
e-Mail beim Ausgang auf Viren geprüft; wir raten jedoch wegen der Gefahr
auf den Übertragungswegen
zu einer Eingangskontrolle. Eine Haftung für Virenfreiheit schließen wir

This e-mail and any attachments are confidential. If you are not the
intended recipient of this e-mail,
please immediately delete its contents and notify us. This e-mail was
checked for virus contamination
before being sent. Nevertheless, it is advisable to check for any
contamination occurring during transmission.
We cannot accept any liability for virus contamination.