# Modbus TCP device connection issue (Couldn't parse ModbusAddress) **URL:** \ **Category:** Ignition\ **Tags:** ignition81\ **Created:** [March 14, 2023, 4:30pm UTC](https://forum.inductiveautomation.com/t/modbus-tcp-device-connection-issue-couldnt-parse-modbusaddress/71035 "2023-03-14T16:30:51Z")\ **Posts on this page:** 2\ **Page:** 1
**Author:** ![techwing](https://avatars.discourse-cdn.com/v4/letter/t/85f322/32.png) [@techwing](https://forum.inductiveautomation.com/u/techwing)\ **Post date:** [March 14, 2023, 4:30pm UTC](https://forum.inductiveautomation.com/t/modbus-tcp-device-connection-issue-couldnt-parse-modbusaddress/71035/1 "2023-03-14T16:30:51Z")
I just worked through an issue with a Modbus TCP device. Running Ignition 8.1.17. The Modbus TCP device would only return Uncertain Initial Value messages and not resolve the register values. Reviewing the Log, there was an error in the RequestSchedule Logger: > Rescheduling; error handling subscritpion change: java.lang.RuntimeException: Couldn't parse ModbusAddress from "40010". This was not the register I was attempting to read. Deleting and recreating the Modbus TCP device resulted in the same issue. I finally deleted the Modbus TCP device and recreated it using a new device name; that resolved the issue and I am actively reading the Modbus TCP holding register value. I did not restart the Modbus TCP module yet; I have several devices actively using it on this production gateway. Posting here in case this helps someone else. ---
**Author:** ![Thomas\_Magill](https://avatars.discourse-cdn.com/v4/letter/t/65b543/32.png) [@Thomas\_Magill](https://forum.inductiveautomation.com/u/Thomas_Magill)\ **Post date:** [July 30, 2024, 3:02pm UTC](https://forum.inductiveautomation.com/t/modbus-tcp-device-connection-issue-couldnt-parse-modbusaddress/71035/2 "2024-07-30T15:02:04Z")
Just wanted to note that I had this same exact issue and the resolution was the same. Deleting the device and adding it back with a _different_ name. Ignition version **8.1.27 (b2023042509)**