Apache OpenOffice (AOO) Bugzilla – Issue 96218
Invalid path to DLL in registry upon fresh installation
Last modified: 2009-01-26 11:12:01 UTC
I encounter this bug from CCleaner's (version 2.13.720) registry scan and it reported an ActiveX/COM Issue regarding the registry value at HKEY_CLASSES_ROOT\CLSID\{7BC0E710-5703-45BE-A29D-5D46D8B39262}\InprocServer32 being improperly set to "C:\\Program Files\\OpenOffice.org 3\\program\\ooofiltproxy.dll" (without quotes). This path to ooofiltproxy.dll is incorrect and should be "C:\\Program Files\\OpenOffice.org 3\\Basis\\program\\ooofiltproxy.dll" Below are the export of the incorrect registry key/value and also the DIR log of the actual location of ooofiltproxy.dll: ===== Windows Registry Editor Version 5.00 [HKEY_CLASSES_ROOT\CLSID\{7BC0E710-5703-45BE-A29D-5D46D8B39262}\InprocServer32] @="C:\\Program Files\\OpenOffice.org 3\\program\\ooofiltproxy.dll" "ThreadingModel"="Apartment" ===== C:\Program Files\OpenOffice.org 3>dir /s ooofiltproxy.dll Volume in drive C has no label. Volume Serial Number is 18A2-B075 Directory of C:\Program Files\OpenOffice.org 3\Basis\program 28/08/2008 01:54 PM 88,576 ooofiltproxy.dll 1 File(s) 88,576 bytes Total Files Listed: 1 File(s) 88,576 bytes 0 Dir(s) 18,754,977,792 bytes free =====
@ is: Can we correct this registry key in 3.0.1 time frame?
IS: Fixed in cws native209.
IS -> OF: Please verify in cws native209.
OF: Registry entry corrected in cws native209.
Hi! I found other registry value with the same problem. In HKCR\CLSID\{43887C67-4D5D-4127-BAAC-87A288494C7C}, the path in InProcServer32\ is: C:\Arquivos de programas\BrOffice.org 3\program\xmergesync.dll But xmergesync.dll is found here: C:\Arquivos de programas\BrOffice.org 3\Basis\program I use Windows XP SP3. Thanks!
Can we get a fix for the mentioned 'xmergesync.dll' too?
Reassigned
Fixed four Windows registry items to xmergesync.dll in scp2. Fixed in cws native209.
is -> of: please verify in cws native209.
OF: Looks good in cws native209.
OF: Ok in OOO300_m15.
*** Issue 98472 has been marked as a duplicate of this issue. ***