E10 Orphaned Task Agent

Yahoo Archive
1
Thanks!  I removed the line refering to the orphaned agent and now everything is A-Okay.

 
2

I did a virgin install of E10, and was unhappy with one of the Application instances (from the Epicor Admin Console, Server Mngmnt -> <severname> <application instance> ), so I uninstalled it and created a new Application instance, including a new Task Agent.


But now the Task Agent Service Configuration window (the one you get after clicking the Task Agent Config button when viewing the App Instance) shows two Task Agents running.  The first is the Task Agent from the first Apps install, and the second from the new App install.


Both of these show for DEMO App and the newly created app.


I tried stopping the first one so I could delete it, but I get: 


Could not connect to the application server using the supplied info.

Received error: The message coul not be dispatched because the 

service at the endpoint address

'net.tcp:// <servername>/<appname>/Ice/Lib/SessionMod.svc'

is unavailable for the protocol of the address.


Any Ideas as to how to get rid of this orphaned Task Agent?


Calvin


3

Look in here at the config file

 

 

C:\ProgramData\Epicor Software Corporation\ICE TaskAgent Service\3.1.400.0

 

Rob Bucek

Production Control Manager

D&S Manufacturing

301 E. Main St.

Black River Falls, WI 54615

715-284-5376 Ext. 311

Mobile: 715-896-3119

rbucek@...

Visit our newly redesigned Website at www.dsmfg.com

 

From: vantage@yahoogroups.com [mailto:vantage@yahoogroups.com]
Sent: Wednesday, July 6, 2016 8:27 AM
To: vantage@yahoogroups.com
Subject: [Vantage] E10 Orphaned Task Agent

 

 

I did a virgin install of E10, and was unhappy with one of the Application instances (from the Epicor Admin Console, Server Mngmnt -> <severname> <application instance> ), so I uninstalled it and created a new Application instance, including a new Task Agent.

 

But now the Task Agent Service Configuration window (the one you get after clicking the Task Agent Config button when viewing the App Instance) shows two Task Agents running.  The first is the Task Agent from the first Apps install, and the second from the new App install.

 

Both of these show for DEMO App and the newly created app.

 

I tried stopping the first one so I could delete it, but I get: 

 

Could not connect to the application server using the supplied info.

Received error: The message coul not be dispatched because the 

service at the endpoint address

'net.tcp:// <servername>/<appname>/Ice/Lib/SessionMod.svc'

is unavailable for the protocol of the address.

 

Any Ideas as to how to get rid of this orphaned Task Agent?

 

Calvin