Skip to main content

In recent days we have had problems with the A360 tool trying to identify elements with technology type MS_ACTIVE_ACCESSIBILITY (e.g. Excel, Outlook, Notepad, etc.), this has not allowed us to execute previously identified elements (Throwing exceptions related to not finding the elements), in addition to not allowing us to identify new elements.

 

We have tried to identify elements with the same bot user but on different VM and it works fine, so we believe the issue is at the VM level

 

Has anyone experienced a similar problem?

 

@Daniel Grimaldo​ :

 

Please follow the below steps

 

  1. Open the Start Menu and search for Command Prompt.
  2. Right-click it and choose to Run as administrator
  3. Type regsvr32.exe oleacc.dll  and hit Enter.

....................................................................................................................................................................

  1. Open File Explorer and type %windir%\SysWoW64 in the address bar. The 32-bit Command Prompt executable is located in this folder.
  2. Right-click on the cmd.exe file and choose to Run as administrator. A 32-bit elevated Command Prompt instance is opened.
  3. Execute the regsvr32.exe oleacc.dll command as explained above. The file is now registered and a confirmation dialog is displayed
  4. Restart the machine once the above step is performed.

 

if you are still facing an issue then please create a support case

 

How to create a support case :

https://apeople.automationanywhere.com/s/article/How-to-create-a-support-case-in-service-cloud

 

if you don't have access to the above link, email the AA Support team "apeopleopsteam@automationanywhere.com" to get access.


Hi @Daniel Grimaldo ,

 

I have the same problem and the fix that Automation Anywhere Team posted helped but not for a long time. It helped with Chrome HTML objects but now it doesen’t work again and also SAP objects are not recognised. Are there another posslible fixes available?


@mblaskovic 

Cause

In the client’s machine registry entries might not be in the proper state. Due to this, scripting is not really enabled and technology type was displayed as MS_ACTIVE_ACCESSIBILITY not SAP.

Resolution/Workaround

Reset the accessibility settings from Control Panel by the following steps.

1. Open the control panel, then navigate to SAP application like below.

(1).png


2. Enable the scripting and click on apply, again disable the scripting and click on apply, and then again enable the scripting and apply like below.
(2).png


@rbkadiyam Unfortunately, disabling and enabling scripting does not help. SAP just suddenly stopped working on new and existing objects, same as as Chrome.

 

The fix with regsvr32.exe oleacc.dll  helped but it was only temporary.


Reply