Task agent stops v6 pro10

Yahoo Archive
1
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.

--- 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
>
2
FYI -

MS has released KB925876 through Windows Updates - this is a new version of
Remote Desktop Connection. Killed one customers ability to connect through
a VPN to work. It can be uninstalled via add/remove programs.

MS has also released Windows Media Player V11 via automatic updates. This
causes a conflict with Sonic Digital Media V7. It can also be uninstalled
via add/remove programs.

And for the perfect trifecta - Internet Explorer V7 which seems to be
causing issues with just about everything.

Does anyone else out there think Vista is going to be mess?

Based on MS's recommendations and a bit of cynicism I'm specing new systems
with Intel Core 2 Duo 2.0 ghz processors, 2 gig of RAM, and a high end video
card ... Just to run Vista with "normal" day to day programs. I'll install
them using Win-XP-Pro-SP2 and try and postpone the actual upgrade to Vista
for as long as possible. Vista-SP5 should be stable?

What does it take if you're trying to use Vista with V8? Has anyone run any
benchmarks yet?

Todd Anderson
3
Todd,
I have run V8 on different iterations of Vista since even before the
"public" beta release.
Basically, I agree with your hardware assesment. 2gb RAM is a minimum.

The biggest issue I have seen aside from that is that the video card must be
really capable. Lots of people have said that the integrated video on
systems they have bought just do not really operate well with vista systems,
and my experience has proved to be the same.
I think V8 clients on Vista will run acceptably, but just not on machines
companies will look to UPGRADE to Vista.


>From: "Todd Anderson" <todd.anderson@...>
>Reply-To: vantage@yahoogroups.com
>To: "'Vantage @ YahooGroups. Com'" <vantage@yahoogroups.com>
>Subject: [Vantage] MS Updates
>Date: Wed, 13 Dec 2006 06:55:00 -0600
>
>FYI -
>
>MS has released KB925876 through Windows Updates - this is a new version of
>Remote Desktop Connection. Killed one customers ability to connect through
>a VPN to work. It can be uninstalled via add/remove programs.
>
>MS has also released Windows Media Player V11 via automatic updates. This
>causes a conflict with Sonic Digital Media V7. It can also be uninstalled
>via add/remove programs.
>
>And for the perfect trifecta - Internet Explorer V7 which seems to be
>causing issues with just about everything.
>
>Does anyone else out there think Vista is going to be mess?
>
>Based on MS's recommendations and a bit of cynicism I'm specing new systems
>with Intel Core 2 Duo 2.0 ghz processors, 2 gig of RAM, and a high end
>video
>card ... Just to run Vista with "normal" day to day programs. I'll install
>them using Win-XP-Pro-SP2 and try and postpone the actual upgrade to Vista
>for as long as possible. Vista-SP5 should be stable?
>
>What does it take if you're trying to use Vista with V8? Has anyone run
>any
>benchmarks yet?
>
>Todd Anderson
>
>
>
>

_________________________________________________________________
View Athlete�s Collections with Live Search
http://sportmaps.live.com/index.html?source=hmemailtaglinenov06&FORM=MGAC01
4
> Todd,
> I have run V8 on different iterations of Vista since even before the
> "public" beta release.
> Basically, I agree with your hardware assesment. 2gb RAM is a minimum.

My XP recommendation is 1GB MINIMUM and 2GB preferred.

> The biggest issue I have seen aside from that is that the video card must be
> really capable. Lots of people have said that the integrated video on
> systems they have bought just do not really operate well with vista systems,
> and my experience has proved to be the same.

I keep reading in the popular geek press that the main performance hit comes
from using the new display model - Aero or Aero Glass. I found this posting
that shows how to improve performance on Vista capable machines:

http://www.windows-now.com/blogs/kmkenney/archive/2006/12/06/tuning-windows-ae
ro-performance-on-low-end-video-cards.aspx
or
http://tinyurl.com/ye9s9r

I think a bigger issue is some have reported issues running .Net 1.1 apps on
Vista out of the box. By default, it installs .Net 2.0 and I don't believe
that Epicor officially supports .Net 2.0 yet although I believe there are
people on this list who do run the Vantage client on .Net 2.0 already.

Should be interesting...

BTW, at the Michigan User's Group meeting our CAM mentioned that the names
Vantage and Vista will disappear and the product will be called Epicor 9. That
should make the confusion about which Vista you're running a bit easier for
the support team.

Mark W.
5
Regarding the .net framework....
I have not ever gotten v8 (not yet on 803) to run on .net 2.
Client says .net 1.1 not installed. I was forced to install version 1.1
Carey


>From: "Mark Wonsil" <mark_wonsil@...>
>Reply-To: vantage@yahoogroups.com
>To: <vantage@yahoogroups.com>
>Subject: RE: [Vantage] MS Updates
>Date: Wed, 13 Dec 2006 14:02:58 -0500
>
> > Todd,
> > I have run V8 on different iterations of Vista since even before the
> > "public" beta release.
> > Basically, I agree with your hardware assesment. 2gb RAM is a minimum.
>
>My XP recommendation is 1GB MINIMUM and 2GB preferred.
>
> > The biggest issue I have seen aside from that is that the video card
>must be
> > really capable. Lots of people have said that the integrated video on
> > systems they have bought just do not really operate well with vista
>systems,
> > and my experience has proved to be the same.
>
>I keep reading in the popular geek press that the main performance hit
>comes
>from using the new display model - Aero or Aero Glass. I found this posting
>that shows how to improve performance on Vista capable machines:
>
>http://www.windows-now.com/blogs/kmkenney/archive/2006/12/06/tuning-windows-ae
>ro-performance-on-low-end-video-cards.aspx
>or
>http://tinyurl.com/ye9s9r
>
>I think a bigger issue is some have reported issues running .Net 1.1 apps
>on
>Vista out of the box. By default, it installs .Net 2.0 and I don't believe
>that Epicor officially supports .Net 2.0 yet although I believe there are
>people on this list who do run the Vantage client on .Net 2.0 already.
>
>Should be interesting...
>
>BTW, at the Michigan User's Group meeting our CAM mentioned that the names
>Vantage and Vista will disappear and the product will be called Epicor 9.
>That
>should make the confusion about which Vista you're running a bit easier for
>the support team.
>
>Mark W.
>
>

_________________________________________________________________
Stay up-to-date with your friends through the Windows Live Spaces friends
list.
http://clk.atdmt.com/MSN/go/msnnkwsp0070000001msn/direct/01/?href=http://spaces.live.com/spacesapi.aspx?wx_action=create&wx_url=/friends.aspx&mk
6
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