I am having what seems to be the same issue with a little used DB. It
seems like the task agent stops after about 30 minutes and when the
next time someone log into the db and wants to print something it
doesnt print. Stopping the process server and restarting it restarts
the taskagent and the queued reports print.
Can anyone shed some light on how to keep the taskagent active?
Thanks,
Bernie.
seems like the task agent stops after about 30 minutes and when the
next time someone log into the db and wants to print something it
doesnt print. Stopping the process server and restarting it restarts
the taskagent and the queued reports print.
Can anyone shed some light on how to keep the taskagent active?
Thanks,
Bernie.
--- In vantage@yahoogroups.com, "Carey S" <rotary1@...> wrote:
>
> Everyone,
> I copied my live database to pilot database for some prototyping.
> I then had to go into task agent maint and change the app server
ports to
> map those listed in the brokers on progress explorer. This worked
fine and I
> am able to start the task agent.
> However, it seems like every half hour or so, the task agent just
stops and
> the printing, mrp, and other functions remain scheduled.
>
> I have to manually stop all 3 brokers for the pilot database (main,
process,
> and task agent) and restart them in order to get these functions to
> run...but 30 minutes or so later...happens again.
> I have a call into support for suggestions, but still unsure.
>
> Anyone have any ideas?
> Thanks
> Carey
>
> _________________________________________________________________
> Get free, personalized commercial-free online radio with MSN Radio
powered
> by Pandora http://radio.msn.com/?icid=T002MSN03A07001
>