We've seen in the past after pushing O/S updates or patches to Runtime Resources, customers may encounter issues with AA Mode such as the following:
- System Exception - (xxxxxx) not found when trying to highlight AA spied elements.
- BP may crash while trying to spy in AA mode.
- Already spied AA element cannot be highlighted.
- Re-spying with AA mode may not work.
- There are times when you close and reopen BP, AA elements will work for a short period and then break again.
Sometimes this issue can be easily fixed by re-registering the OLEACC.DLL file (usually located here: 'C:\Windows\System32' directory).
However, if re-registering doesn't help to fix the issue, then your next option is to delete some registry keys.
Important: Deleting registry keys should only be done by your IT team and it's always advisable to backup the registry before making any such changes.
The following registry key has to be deleted because after the upgrade, the Accessibility COM object is sometimes unable to pick the right Bit-ness version (i.e. 64- or 32-bit) to work with, hence the AA spy issue:
[HKEY_CLASSES_ROOT\WOW6432Node\Interface\{618736E0-3C3D-11CF-810C-00AA00389B71}]
Remember to reboot machine after deleting the key.
