# TCPServerChannel Errors after upgrade to 7.9.6

**URL:** <https://forum.inductiveautomation.com/t/tcpserverchannel-errors-after-upgrade-to-7-9-6/17314>\
**Category:** Ignition\
**Tags:** ignition79\
**Created:** [March 10, 2018, 8:15pm UTC](https://forum.inductiveautomation.com/t/tcpserverchannel-errors-after-upgrade-to-7-9-6/17314 "2018-03-10T20:15:17Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![MMaynard](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/mmaynard/32/3366_2.png) [@MMaynard](https://forum.inductiveautomation.com/u/MMaynard)\
**Post date:** [March 10, 2018, 8:15pm UTC](https://forum.inductiveautomation.com/t/tcpserverchannel-errors-after-upgrade-to-7-9-6/17314/1 "2018-03-10T20:15:17Z")

</div>

We just completed an upgrade to 7.9.6 and Java to update 161 (8.0.1610.12)  
The server appears to functioning fine but every 15 seconds there is an error in the log

> TcpServerChannel Time:  
> 10Mar2018 14:13:40  
> Message:  
> Received renew but currentChannel==null; closing.

I have regenerated all certificates, restarted the gateway, deleted an old Kepware connection.  
But the error keeps coming up every 15 seconds.

---

<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:** [March 10, 2018, 8:49pm UTC](https://forum.inductiveautomation.com/t/tcpserverchannel-errors-after-upgrade-to-7-9-6/17314/2 "2018-03-10T20:49:40Z")

</div>

You’ve got some other client, probably an Ignition, connecting to this server. If you edit/save or reset it somehow it should stop.

---

<div class="post-metadata">

**Author:** ![MMaynard](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/mmaynard/32/3366_2.png) [@MMaynard](https://forum.inductiveautomation.com/u/MMaynard)\
**Post date:** [March 10, 2018, 9:32pm UTC](https://forum.inductiveautomation.com/t/tcpserverchannel-errors-after-upgrade-to-7-9-6/17314/3 "2018-03-10T21:32:18Z")

</div>

This machine is part of a gateway network, that is the only other thing connected to it.  
If I go in and change the endpoint to the default of localhost, the errors go away but then the gateway network faults.  
I then change it back to the servers IP address, the gateway networks reconnect, but the above TCP errors start again.

---

<div class="post-metadata">

**Author:** ![MMaynard](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/mmaynard/32/3366_2.png) [@MMaynard](https://forum.inductiveautomation.com/u/MMaynard)\
**Post date:** [March 10, 2018, 9:38pm UTC](https://forum.inductiveautomation.com/t/tcpserverchannel-errors-after-upgrade-to-7-9-6/17314/4 "2018-03-10T21:38:10Z")

</div>

I had to go on the central server and put a host over ride address in for this server now for some reason.  
Did that, reset all the connections, and the world is happy again…