# Problems with Contrologix Communications

**URL:** <https://forum.inductiveautomation.com/t/problems-with-contrologix-communications/3980>\
**Category:** Ignition\
**Created:** [February 11, 2012, 12:57am UTC](https://forum.inductiveautomation.com/t/problems-with-contrologix-communications/3980 "2012-02-11T00:57:29Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Curlyandshemp](https://avatars.discourse-cdn.com/v4/letter/c/bcef8e/32.png) [@Curlyandshemp](https://forum.inductiveautomation.com/u/Curlyandshemp)\
**Post date:** [February 11, 2012, 12:57am UTC](https://forum.inductiveautomation.com/t/problems-with-contrologix-communications/3980/1 "2012-02-11T00:57:29Z")

</div>

![](https://us1.discourse-cdn.com/inductiveautomation/original/1X/1dd9c7697fd6776388658fdfbc8e5a2ef242ebad.jpg)  
We have an install on the other side of the country that we can only support via LogMeIn on an Ignition Client with a 4G USB stick. This install was October/November of 2011

There have been a few randon occurances of transactions groups hanging over the past 3 months requiring a Gateway reboot to resolve.

The only thing we can see is a flurry of consistent error messages and communication timeouts showing up, in particular the attached.

What exactly is this error in the console?

---

<div class="post-metadata">

**Author:** ![Travis.Cox](https://avatars.discourse-cdn.com/v4/letter/t/b9bd4f/32.png) [@Travis.Cox](https://forum.inductiveautomation.com/u/Travis.Cox)\
**Post date:** [February 11, 2012, 1:52am UTC](https://forum.inductiveautomation.com/t/problems-with-contrologix-communications/3980/2 "2012-02-11T01:52:40Z")

</div>

What version of Ignition do you have?

---

<div class="post-metadata">

**Author:** ![Curlyandshemp](https://avatars.discourse-cdn.com/v4/letter/c/bcef8e/32.png) [@Curlyandshemp](https://forum.inductiveautomation.com/u/Curlyandshemp)\
**Post date:** [February 11, 2012, 2:49pm UTC](https://forum.inductiveautomation.com/t/problems-with-contrologix-communications/3980/3 "2012-02-11T14:49:01Z")

</div>

V73.1

 ![](https://us1.discourse-cdn.com/inductiveautomation/original/1X/ea1519c8a82c500897feb931dee6a4f632b822a8.jpg)

---

<div class="post-metadata">

**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\
**Post date:** [February 11, 2012, 4:39pm UTC](https://forum.inductiveautomation.com/t/problems-with-contrologix-communications/3980/4 "2012-02-11T16:39:24Z")

</div>

I can almost guarantee that the log messages regarding CLX timeouts/key not found are unrelated to the “group hanging” symptoms you are seeing. The CLX thing is a known annoyance/bug.

---

<div class="post-metadata">

**Author:** ![Curlyandshemp](https://avatars.discourse-cdn.com/v4/letter/c/bcef8e/32.png) [@Curlyandshemp](https://forum.inductiveautomation.com/u/Curlyandshemp)\
**Post date:** [February 11, 2012, 5:18pm UTC](https://forum.inductiveautomation.com/t/problems-with-contrologix-communications/3980/5 "2012-02-11T17:18:27Z")

</div>

Thanks,

that is what I am trying to convince my programmer of.