Hi,

ENV
Client 5.3.0.8 on win2003, journaling enabled;
Server 5.2.4.1 on win2000.

Situation:
After starting a imm. Client action for a node which failed the schedule
for tonight has been started. Output of q event

Scheduled Start              Actual Start                 Schedule Name
Node Name     Status  
--------------------             --------------------
-------------                  -------------         ---------
29-06-2005 10:07:37      29-06-2005 10:08:15      @284
FS033               Failed
29-06-2005 23:00:00      29-06-2005 10:21:44      2300_PROFILE-
FS033               Started  


 
With this client the last couple of weeks this has happend over and over
again. The regular schedule will fail, an imm. client action is defined
which in turn fails and the schedule of that evening will be started.  
 
Has this anything to do with the failing journal back-up or is this a
bug? If it is a bug, what is the way to work around this? If it is the
journaling, how do we solve the:
 
06/28/2005 23:48:19 JnlQueryResponseThread(tid 5624): Error Reading
query response, jnlRead(): rc=-1.
06/28/2005 23:48:19 BaJournaled(): jnlNextQueryResp(): returned journal
read error.
06/28/2005 23:48:19 ANS1999E Incremental processing of
'\\nuwcluster03\h$' stopped.
 
problems.
 
Regards,
 
Karel