Absolutely, this cleared the problem.
Alberto
-Mensaje original-
De: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED] En nombre de Nancy
Anthracite
Enviado el: Domingo, 29 de Mayo de 2005 10:10 a.m.
Para: hardhats-members@lists.sourceforge.net
Asunto: Re: [Hardhats-members] Run Node
I sent
Ok. Is that all there is to it? I thought that there
had to be synchronization between the VOL specified on
the tasks, and the VOL of the taskman site parameters,
and also synch with a few other places. Glad that its
not such a mess as I thought.
Kevin
--- Nancy Anthracite <[EMAIL PROTECTED]>
I sent out a response to this yesterday, and I hope it got there. It is to
change the Mode of Taskman to General Processor under Taskman Site
Parameters.
On Sunday 29 May 2005 12:00 pm, Kevin Toppenberg wrote:
> Aarrrgg. Not this problem again!
>
> This has caused so many new users (including m
Aarrrgg. Not this problem again!
This has caused so many new users (including myself)
such endless hassle, that I had really hoped this
would be fixed with future releases of our packaged
VistA.
I fixed it by clearing everything out and starting
from scratch with my scripting installation. So I
You need to change the MODE of TASKMAN in the Taskman Site Parameters to
General Processor.
On Saturday 28 May 2005 11:51 am, Alberto Odor Morales wrote:
> I found en error while monitoring Taskman in my Caché installation.
>
>
> Checking Taskman. Cur
