Issue 96218 - Invalid path to DLL in registry upon fresh installation
Summary: Invalid path to DLL in registry upon fresh installation
Status: CLOSED FIXED
Alias: None
Product: Installation
Classification: Application
Component: code (show other issues)
Version: OOo 3.0
Hardware: PC Windows XP
: P3 Trivial (vote)
Target Milestone: OOo 3.0.1
Assignee: Olaf Felka
QA Contact: issues@installation
URL:
Keywords:
: 98472 (view as issue list)
Depends on:
Blocks:
 
Reported: 2008-11-14 18:59 UTC by ansonn
Modified: 2009-01-26 11:12 UTC (History)
2 users (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---


Attachments

Note You need to log in before you can comment on or make changes to this issue.
Description ansonn 2008-11-14 18:59:52 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
=====
Comment 1 Olaf Felka 2008-11-15 10:22:40 UTC
@ is: Can we correct this registry key in 3.0.1 time frame?
Comment 2 ingo.schmidt-rosbiegal 2008-11-17 11:52:32 UTC
IS: Fixed in cws native209.
Comment 3 ingo.schmidt-rosbiegal 2008-11-25 15:01:30 UTC
IS -> OF: Please verify in cws native209.
Comment 4 Olaf Felka 2008-11-26 13:45:17 UTC
OF: Registry entry corrected in cws native209.
Comment 5 gbpacheco 2008-12-01 01:24:14 UTC
 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!
Comment 6 Olaf Felka 2008-12-01 07:33:28 UTC
Can we get a fix for the mentioned 'xmergesync.dll' too?
Comment 7 Olaf Felka 2008-12-01 07:34:01 UTC
Reassigned
Comment 8 ingo.schmidt-rosbiegal 2008-12-01 14:29:00 UTC
Fixed four Windows registry items to xmergesync.dll in scp2.
Fixed in cws native209.
Comment 9 ingo.schmidt-rosbiegal 2008-12-02 12:20:57 UTC
is -> of: please verify in cws native209.
Comment 10 Olaf Felka 2008-12-02 15:34:54 UTC
OF: Looks good in cws native209.
Comment 11 Olaf Felka 2009-01-13 10:20:54 UTC
OF: Ok in OOO300_m15.
Comment 12 Olaf Felka 2009-01-26 11:12:01 UTC
*** Issue 98472 has been marked as a duplicate of this issue. ***