This issue affects applications using RSLogix 500 version 7.1, 7.2, or 7.3.
The issue was corrected in version 7.3.1 of RSLogix.