https://issues.apache.org/ooo/show_bug.cgi?id=123640
--- Comment #6 from Steve Yin <[email protected]> --- (In reply to V Stuart Foote from comment #4) > Jamie, Steve > > (In reply to James Teh from comment #3) > > > If you suspect this might be the case, I'd recommend you install the old > > > build, regsvr32 /u UAccCOM.dll, then reinstall the new build. > > Correction: uninstall the new build, install the old build, regsvr32 /u > > UaccCOM.dll, uninstall the old build, install the new build. > > I can not get this to resolve. Getting no IAccessible2 response on two > different Windows 7 sp1 64bit systems. > > When AOO ia2 r1538508 is open, I am only getting MSAA details for the Window > frame nothing from the AOO components. > > Just to be sure, with r1538508 still installed, I first searched the registry > > Only UAccCOM.dll was: > [HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserD > ata\S-1-5-18\Components\0ABC43CE8D1C1E270D11495A5463AF98] > "51B671DF629B09A4991526437BFBBBE1"="C:\\Program Files (x86)\\OpenOffice > 4\\program\\UAccCOM.dll" > > None the less, uninstalled (using Revo). Reinstalled the r1536988 build, and > had a slew of UAccCOM.dll registry entries. But Accprobe showed > IAccessibile2 events firing, and NVDA fully rendered all AOO componnets. > > Then ran regsvr32 /u against the UAccCOM.DLL. > Then full uninstall (using Revo with Advanced scan). > > Reinstalled r1538508 build. Check the registry again and only the installer > component entry as above. > > Before first use, clear per-user configuration from %APPDATA% for my account > and Administrator account. So starting as clean as I can--NVDA 2013.2 > active. Run first time as Administrator. Tools --> Options --> > Accessibility and check "Support Assistive Technology tools". OK and File > --> Exit. Launch again verify check box had checked. CLose. Launch > Accprobe.exe. Launch AOO as Administrator, Accprobe only shows MSAA detail > for the Windows frame. NVDA announces only frame buttons--internal > components all are "unknown". > > Same results if run with user account with "Support Assistive Technology > tools" checked. > > Something is just not right. Hi Stuart, I doubt that the oleacc.dll is not registered correctly on your systems. This issue shold be caused by the old UAccCOM.dll. Solution: enter the system folder such as "C:\windows\system32\" from console and type "regsvr32 oleacc.dll". -- You are receiving this mail because: You are on the CC list for the bug. You are the assignee for the bug. You are watching all bug changes.
