The exchange redbook page 50 has what may be the answer, I quote:
08/05/1998 00:18:05 ANR0406I Session 7283 started for node PTLEXM01
>(WinNT) (Tcp/Ip 10.1.3.196(3404)).
>
>08/05/1998 00:18:07 ANR0406I Session 7284 started for node PTLEXM01
>(WinNTDB) (Tcp/Ip 10.1.3.196(3406)).
>
>08/05/1998 00:33:20 ANR0482W Session 7283 for node PTLEXM01 (WinNT)
>terminated - idle for more than 15 minutes.
>
>08/05/1998 01:05:01 ANR2578I Schedule EXCHG_DAILY in domain EXCHANGE
>for node PTLEXM01 has missed its scheduled start up window.
>
>08/05/1998 01:21:37 ANR0406I Session 7307 started for node PTLEXM01
>(WinNT) (Tcp/Ip 10.1.3.196(4080)).
>
>08/05/1998 01:21:38 ANR2576W An attempt was made to update an event
>record for a scheduled operation which has already been executed -
>multiple client schedulers may be active for node PTLEXM01.
>08/05/1998 01:21:38 ANR0403I Session 7307 ended for node PTLEXM01
>(WinNT).
>
>08/05/1998 01:21:38 ANR0406I Session 7308 started for node PTLEXM01
>(WinNT) (Tcp/Ip 10.1.3.196(4081)).
>
>08/05/1998 01:21:38 ANR0403I Session 7308 ended for node PTLEXM01
>(WinNT).
>
>08/05/1998 01:21:51 ANR0403I Session 7284 ended for node PTLEXM01
Figure 37. Scheduler Client Session Timeout
In this case, message ANR2576W is related to IC21388, TCPFLUSH error 10054
is
due to the fact that the scheduler client session timed out (message
ANR0482W)
while it was waiting for the Exchange Agent to complete the backup.
Similarly,
message ANR2578I indicates that the scheduled event was missed because the
scheduler client session had timed out. You can avoid these messages by
changing the command file used to launch the Exchange Agent to START
EXCDSMC rather than invoking it directly. This change causes the command
file
to return to the scheduler after launching the command rather than waiting
for it
to complete. In this case, you would see the scheduler session complete (and
indicate successful completion) very quickly after start of the event, but
the
Exchange Agent session would continue to run as normal. Be aware though that
the successful completion of the scheduled event simply means that the agent
was started. You still have to check the agent log file to confirm success
of the
Exchange Agent backup.
----- Original Message -----
From: "Marita Gonsalves" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Thursday, October 19, 2000 10:29 AM
Subject: Re: Apparently succesfull schedule return "failed"
Hi Stephanie,
I'm having a similar problem with my TDP for Exchange clients. The sched
log shows a similar error as the one you describe below. Check the act log
for approx the same time on the server and you may see the following error
code: ANR2576W An attempt was made to update an event record for a scheduled
operation which has already been executed - multiple client schedulers may
be active for node <nodename>. I don't have multiple schedulers running and
I called Tivoli tech support. They told me they are aware of this problem
but don't have an apar at this time. They suggested increasing the backup
window - tried that, didn't work for me...q event still comes back failed
for that client.
Marita
-----Original Message-----
From: Stephanie canon [mailto:[EMAIL PROTECTED]]
Sent: Tuesday, October 03, 2000 8:25 AM
To: [EMAIL PROTECTED]
Subject: Apparently succesfull schedule return "failed"
Hi,
I'm running scheduled command on two Notes server. The command stops the
Notes server, runs an incremental backup of the server, and then reboot.
The return code of the command, in the dsmsched.log is 0, but in the
events' list on the server, it is marked as failed.
Apparently, the scheduled command was successful, but the result returned
to the server is "failed".
Can someone tell me why the event is 'failed'?
Thanks for your help.
Here is the dsmsched.log of the node :
----------------------------------------------------------------------------
------------
10/02/2000 21:02:05
ExZcution de la commande du syst^me d'exploitation ou du script :
d:\outils\ntdown.cmd > d:\outils\ntdown.log
10/03/2000 05:15:12 Commande exZcutZe. Code retour :
0
10/03/2000 05:15:12 ExZcution de l'ZvZnement planifiZ 'NOTESPARIS'
terminZe.
10/03/2000 05:15:12 RZsultat de l'ZvZnement planifiZ 'NOTESPARIS' en cours
de transmission.
10/03/2000 05:15:13 Session Ztablie avec le serveur ADSM : MVS
10/03/2000 05:15:14 Version serveur 3, Zdition 1, niveau 2.40
10/03/2000 05:15:14 Date/heure serveur : 10/03/2000 05:15:02 Dernier
acc^s : 10/02/2000 21:02:32
10/03/2000 05:15:14 RZsultat de l'ZvZnement planifiZ 'NOTESPARIS' envoyZ au
serveur.
10/03/2000 05:15:14 ANS1483I Elagage du journal des opZrations planifiZes
lancZ.
10/03/2000 05:15:14 Elagage du journal des op'ration10/03/2000 05:15:14
ANS1483I Elagage du journal des op'rations planifi'es lanc'.
2923 lignes trait'es. 279 lignes 'lagu'es.
10/03/2000 05:15:14 ANS1484I Elagage du journal des op'rations planifi'es
ex'cut'.
10/03/2000 05:15:14 Demande des prochains 'v'nements planifi's au serveur.
10/03/2000 05:15:14 Nom de poste : MAG01
----------------------------------------------------------------------------
-----------------------------
---------------------------------------------------------------
Stiphanie Canon
[EMAIL PROTECTED]
Tel : 02 38 74 59 41
