# OPC-UA Error - "Bad\_EncodingLimitsExceeded

**URL:** <https://forum.inductiveautomation.com/t/opc-ua-error-bad-encodinglimitsexceeded/110719>\
**Category:** Ignition\
**Tags:** ignition81\
**Created:** [September 17, 2025, 3:04pm UTC](https://forum.inductiveautomation.com/t/opc-ua-error-bad-encodinglimitsexceeded/110719 "2025-09-17T15:04:04Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Andre\_Hennecke](https://avatars.discourse-cdn.com/v4/letter/a/e95f7d/32.png) [@Andre\_Hennecke](https://forum.inductiveautomation.com/u/Andre_Hennecke)\
**Post date:** [September 17, 2025, 3:04pm UTC](https://forum.inductiveautomation.com/t/opc-ua-error-bad-encodinglimitsexceeded/110719/1 "2025-09-17T15:04:04Z")

</div>

Hi,

this error appeard in the quick-client on Ignition 8.1 - Edge.

Anybody aware of this OPC-UA Error: "Bad\_EncodingLimitsExceeded: The message encoding/decoding limits imposed by the stack have been exceeded."

Anybody aware of this issue and how to fix it? The server is self-developed. Reading the node is no issue with Prosys Client or UA-Expert

---

<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:** [September 17, 2025, 3:07pm UTC](https://forum.inductiveautomation.com/t/opc-ua-error-bad-encodinglimitsexceeded/110719/2 "2025-09-17T15:07:49Z")

</div>

Usually happens when one side or the other tries to encode a message that is too large.

Sometimes happens when a message is encoded incorrectly and the length field ends up containing a bogus value.

Will probably need Wireshark capture to see.

---

<div class="post-metadata">

**Author:** ![Andre\_Hennecke](https://avatars.discourse-cdn.com/v4/letter/a/e95f7d/32.png) [@Andre\_Hennecke](https://forum.inductiveautomation.com/u/Andre_Hennecke)\
**Post date:** [September 17, 2025, 3:20pm UTC](https://forum.inductiveautomation.com/t/opc-ua-error-bad-encodinglimitsexceeded/110719/3 "2025-09-17T15:20:32Z")

</div>

Thank you for your quick reply,

- I will ask to check this and hopefully get a feedback end of next week, with a wireshark capture.
- We will also test it with 8.3.
- Just wondering why it works with other clients.

---

<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:** [September 17, 2025, 3:22pm UTC](https://forum.inductiveautomation.com/t/opc-ua-error-bad-encodinglimitsexceeded/110719/4 "2025-09-17T15:22:48Z")

</div>

> [@Andre\_Hennecke](#):
>
> Just wondering why it works with other clients.

Couldn't answer this without a capture to see what limits each client negotiates, what service or operation fails or doesn't fail, etc...

---

<div class="post-metadata">

**Author:** ![Andre\_Hennecke](https://avatars.discourse-cdn.com/v4/letter/a/e95f7d/32.png) [@Andre\_Hennecke](https://forum.inductiveautomation.com/u/Andre_Hennecke)\
**Post date:** [September 26, 2025, 11:35am UTC](https://forum.inductiveautomation.com/t/opc-ua-error-bad-encodinglimitsexceeded/110719/5 "2025-09-26T11:35:44Z")

</div>

I sent you two pcaps / wireshark captures with the error when using Igntion and without when using another client.

Would be great to understand where we have the issue.