Jump to content


This is a ready-only archive of the InstallSite Forum. You cannot post any new content here. / Dies ist ein Archiv des InstallSite Forums. Hier können keine neuen Beiträge veröffentlicht werden.
Photo

Incorrect InprocServer32 value(COM registration)


8 replies to this topic

VicJHR

VicJHR
  • Members
  • 6 posts

Posted 12 August 2004 - 14:55

Does anyone know why windows installer sometimes adds the value "InprocServer32" to the key "InprocServer32"
HKCR\CLSID\{...}\InprocServer32\InprocServer32
with the data of this value being a stupid set of charachters ?

What are the curcumstances for such effect to occur?

For example - the installation of ISWI 2.03 writes to key
HKEY_CLASSES_ROOT\CLSID\{00020420-0000-0000-C000-000000000046}\InprocServer32
a value with the same name "InprocServer32" having data like a piece of memory.
this causes known problems :
http://support.micro...om/?kbid=329134
http://support.micro...kb;en-us;298110

Otherwise the installation of DevStudio8 does not do such things !!!

Glytzhkof

Glytzhkof
  • Moderators
  • 1,447 posts

Posted 13 August 2004 - 09:32

Never seen this, but it could be errors in the self-registration code for that COM dll. If you have access to the ATL .rgs file you could take a look and see if you see anything suspicious.
Regards
-Stein Åsmul

Stefan Krueger

Stefan Krueger

    InstallSite.org

  • Administrators
  • 13,269 posts

Posted 13 August 2004 - 11:27

I believe this extra entry is used by Windows Installer to support advertisement and resiliency via COM activation.

VicJHR

VicJHR
  • Members
  • 6 posts

Posted 13 August 2004 - 11:34

Just look at
HKEY_CLASSES_ROOT\CLSID\{00020420-0000-0000-C000-000000000046}\InprocServer32
on Your computer
and check the existance of value "InprocServer32" there.

meny products create this value spoiled by a set of simbols\numbers

for example :
- InstallShiled for Windows Installer 2.03
- Tweak-XP


to Stefan Krueger: thank You for answer.

We have problems in our software related with this issue-the popup of windows installer repair procedure each time the disk configuration changes(our product is related to Backup), the problems disappear if one reregister one our dll file,or simply delete this "InprocServer32" value (the value but not a key - they have the same name) from corresponding to our dll CLSID section.

Edited by VicJHR, 13 August 2004 - 11:40.


Stefan Krueger

Stefan Krueger

    InstallSite.org

  • Administrators
  • 13,269 posts

Posted 13 August 2004 - 14:43

Removing this entry would prevent Windows Installer from perfoming the auto-repair when this COM server is activated. However that is probably only removing the sympton, not the real cause. Question is: what is causing Windows Installer to trigger auto-repair. Look at the Windows event log to diagnose.

VicJHR

VicJHR
  • Members
  • 6 posts

Posted 16 August 2004 - 11:12

There are two records in Aplication Event log:

first:
Detection of product '{65D29614-5C3C-4ED4-B9DF-F19B42CDFB64}', feature 'LiveBackupClient', component '{25398ADF-E7F4-4128-ACE4-14282D4D7985}' failed. The resource 'F:\' does not exist.

where component '{25398ADF-E7F4-4128-ACE4-14282D4D7985} is a standard merge module MDAC 2.6

second one:
Detection of product '{65D29614-5C3C-4ED4-B9DF-F19B42CDFB64}', feature 'ProgramFiles' failed during request for component '{8C2AF9B8-FB3A-11D3-956C-005004B2A19A}'
where component '{8C2AF9B8-FB3A-11D3-956C-005004B2A19A}' is our COM object dll.

The binary comparison shows that all our installation files are OK and consistent.

The problem arises then the unformated disk (partition) appears in the system, so the Drive number is assigned to it but in can't be opened or accessed (the "F:\" one in the log above).
Our installation and our product functionality deals nothing with this drive,nevertheless installer repairs the product ,asks for reboot and everything
repeats.

Any ideas?
May be installer in some way treats the data of "InprocServer32" value as a path and tryes to access for some reason this drives () and gets "unexpected error" (at least for windows installer)?

VicJHR

VicJHR
  • Members
  • 6 posts

Posted 16 August 2004 - 11:16

I tried to get installer's log using key:

[HKEY_LOCAL_MACHINE\SOFTWARE\Policies\Microsoft\Windows\Installer]
"Logging"="voicewarmup"
"Debug"=dword:00000007

but no log files were produced (though this usually method works fine for standard install/uninstall cases).




Stefan Krueger

Stefan Krueger

    InstallSite.org

  • Administrators
  • 13,269 posts

Posted 16 August 2004 - 19:50

Has any of these components a destination setting that might point to F:\ ? In this case you should change it to something that's guaranteed to be valid.

VicJHR

VicJHR
  • Members
  • 6 posts

Posted 17 August 2004 - 09:20

They have no deal with "F:\". Moreover drive letter "F:\" is not a constant one.The bug may occur on any other unformatted drive depending on what letter was assigned to it by Windows. In one case it was "F:\" , in other - "G:\" or etc.