# RegisterServer TCPClientChannel Connection Lost

**URL:** <https://forum.inductiveautomation.com/t/registerserver-tcpclientchannel-connection-lost/5779>\
**Category:** Ignition\
**Created:** [January 31, 2013, 11:01pm UTC](https://forum.inductiveautomation.com/t/registerserver-tcpclientchannel-connection-lost/5779 "2013-01-31T23:01:17Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![kpollock](https://avatars.discourse-cdn.com/v4/letter/k/df788c/32.png) [@kpollock](https://forum.inductiveautomation.com/u/kpollock)\
**Post date:** [January 31, 2013, 11:01pm UTC](https://forum.inductiveautomation.com/t/registerserver-tcpclientchannel-connection-lost/5779/1 "2013-01-31T23:01:17Z")

</div>

Ignition 7.5.4 on Windows Server Enterprise 2007 on VM Server with 4 GB Ram

Running a ton of SQL Queries to populate data displays and reports but no significant CPU usage. SQL DB on both the local machine and the SQL Plant DB on a remote machine. Memory is utilized close to 4 GB. OS and Memory upgrade scheduled later this spring.

All IO comes from OPC DA from KepWare 5.5 on the local machine. 0% Problems with KepWare.

Ignition running well for 1.5 years but occasional performance problems.

I am studying the console to find issues and errors. I am getting a repeating warning every 10 minutes: “RegisterServer TCPClientChannel Connection Lost”

Screen Shot attached. What is this warning and how do I correct it?

Thanks Ken P.

 ![](https://us1.discourse-cdn.com/inductiveautomation/original/2X/6/674cdd40a859f1999ef0d4d0f92a9453ede7bec2.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 1, 2013, 12:18am UTC](https://forum.inductiveautomation.com/t/registerserver-tcpclientchannel-connection-lost/5779/2 "2013-02-01T00:18:04Z")

</div>

Go to the UA settings and set the discovery registration frequency to 0 and disable the discovery server.
