# EAM agent failure to register with controller

**URL:** <https://forum.inductiveautomation.com/t/eam-agent-failure-to-register-with-controller/109156>\
**Category:** Ignition\
**Tags:** ignition81\
**Created:** [July 30, 2025, 4:12pm UTC](https://forum.inductiveautomation.com/t/eam-agent-failure-to-register-with-controller/109156 "2025-07-30T16:12:29Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![James\_Caudle](https://avatars.discourse-cdn.com/v4/letter/j/5f9b8f/32.png) [@James\_Caudle](https://forum.inductiveautomation.com/u/James_Caudle)\
**Post date:** [July 30, 2025, 4:12pm UTC](https://forum.inductiveautomation.com/t/eam-agent-failure-to-register-with-controller/109156/1 "2025-07-30T16:12:29Z")

</div>

Hello. When attempting to add another agent to our EAM controller I got this error in the log. It successfully connected via the Gateway Network but failed to register as an EAM Agent.  
I tried redoing from scratch to the same result.

Gateway versions are both 8.1.42

```
Exception thrown when attempting to register agent on the controller

```

> com.inductiveautomation.metro.api.ex.TimeoutExpiredException: TimeoutExpiredException[queueId=service\_StatusEventService, targetIntent=_services.invoke_|2, msgData=com.inductiveautomation.eam.gateway.services.StatusEventService#reportSystemInfo([class com.inductiveautomation.eam.gateway.module.controller.agentstatus.AgentSystemInfo])]
> 
> at com.inductiveautomation.metro.impl.queues.StandardQueue.processTimeouts(StandardQueue.java:231)
> 
> at com.inductiveautomation.metro.impl.queues.StandardQueue.lambda$maybeScheduleTimeoutChecker$1(StandardQueue.java:213)
> 
> at java.base/java.util.concurrent.Executors$RunnableAdapter.call(Unknown Source)
> 
> at java.base/java.util.concurrent.FutureTask.run(Unknown Source)
> 
> at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(Unknown Source)
> 
> at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(Unknown Source)
> 
> at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)
> 
> at java.base/java.lang.Thread.run(Unknown Source)

---

<div class="post-metadata">

**Author:** ![James\_Caudle](https://avatars.discourse-cdn.com/v4/letter/j/5f9b8f/32.png) [@James\_Caudle](https://forum.inductiveautomation.com/u/James_Caudle)\
**Post date:** [July 31, 2025, 1:18pm UTC](https://forum.inductiveautomation.com/t/eam-agent-failure-to-register-with-controller/109156/2 "2025-07-31T13:18:56Z")

</div>

Had to restart the gateway service. (After waiting for a downtime window). Really hoping 8.3 can make EAM better.

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [July 31, 2025, 1:20pm UTC](https://forum.inductiveautomation.com/t/eam-agent-failure-to-register-with-controller/109156/3 "2025-07-31T13:20:26Z")

</div>

Well, it isn't going to reduce the need for gateway restarts. Many config changes in v8.1 that could be done "live" will now require a restart.