-
Description
On one workstation QESSO detects only a handful of web applications, but not others.
Manual uninstallation and reinstallation didn’t change anything. The SSO engine GUI does show all applications listed in there, so not a cache issue.
The problem isn’t linked to a specific user (reproduced if the engine is started as someone else). Traces attached show the engine detecting a first application (Infinity, thick client), then failing to detect another (ADP, web based in IE8). -
Resolution
The Microsoft API accessibility is not functioning on the system.
Run the regsvr32 in a cmd window with administrator mode enabled.Steps:1. Click the Start Button, then in the "Start Search" box type CMD but DO NOT press Enter yet.2. In the list above, under "Programs" right-click on CMD that appears above and choose "Run as Administrator" and click "Continue".On 32-bit systems:Launch the following commands:C:\Windows\System32\regsvr32 C:\Windows\System32\oleacc.dllC:\Windows\System32\regsvr32 C:\Windows\System32\IAccessible2Proxy.dllOn 64-bit systems:Launch the two following commands:C:\Windows\System32\regsvr32 C:\Windows\System32\oleacc.dllC:\Windows\System32\regsvr32 C:\Windows\System32\IAccessible2Proxy.dlland:C:\Windows\SysWOW64\regsvr32 C:\Windows\SysWOW64\oleacc.dllC:\Windows\SysWOW64\regsvr32 C:\Windows\SysWOW64\IAccessible2Proxy.dllThereafter re-launch SSOWatch.
Note this is not an QSSO problem but Internet Explorer accessibility.
Comments
0 comments
Please sign in to leave a comment.