# Component name 'null' is invalid

**URL:** <https://forum.inductiveautomation.com/t/component-name-null-is-invalid/64092>\
**Category:** Ignition\
**Tags:** ignition81, vision\
**Created:** [September 15, 2022, 5:02am UTC](https://forum.inductiveautomation.com/t/component-name-null-is-invalid/64092 "2022-09-15T05:02:46Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [September 15, 2022, 11:29am UTC](https://forum.inductiveautomation.com/t/component-name-null-is-invalid/64092/2 "2022-09-15T11:29:39Z")

</div>

Long-standing impedence mismatch between java and RDP-based remote access solutions. There's a work-around, IIRC.....

Yes:

> [@\[IGN-4671\]Random Component Name Error in Vision Client](https://forum.inductiveautomation.com/t/ign-4671-random-component-name-error-in-vision-client/23521/39):
>
> Can anyone experiencing this issue try putting the following code into a client startup script and reporting back? from javax.swing import UIManager UIManager.getLookAndFeelDefaults().put("Synth.doNotSetTextAA", True)

---

_[View the full topic](https://forum.inductiveautomation.com/t/component-name-null-is-invalid/64092)._