cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
paul388
Level 2

Failure on Windows7 64-bit, component deregistered twice

I'm facing the problem that one of my components marked for selfregistration is called twice. Consequently the second call fails with error 1905. While during installation each component is called, as expected, an extra call is generated for deinstallation.

Any idea why this happens?

The logfile shows during deinstalltion:

InstallShield 17:42:45: ISBEW64.exe is successfully loaded for 64-bit registration
InstallShield 17:42:45: Unregistering file D:\Program Files\B\n 2.3\Win32\Source.ax (32-bit)
InstallShield 17:42:45: Unregistering file D:\Program Files\B\n 2.3\x64\Source.ax (64-bit)
InstallShield 17:42:45: Unregistering file D:\Program Files\B\n 2.3\Win32\CSC.ax (32-bit)
InstallShield 17:42:45: Unregistering file D:\Program Files\B\n 2.3\x64\CSC.ax (64-bit)
InstallShield 17:42:45: Unregistering file D:\Program Files\B\n 2.3\x64\Source.ax (64-bit)


The corresponding part of the installation log-file shows:
InstallShield 17:42:18: Initializing Property Bag...
InstallShield 17:42:18: Getting file count from property bag
InstallShield 17:42:18: File Count : 5
InstallShield 17:42:18: Sorting Based On Order...
InstallShield 17:42:18: ISBEW64.exe is successfully loaded for 64-bit registration
InstallShield 17:42:18: Registering file D:\Program Files\B\n 2.3\x64\CSC.ax (64-bit)
InstallShield 17:42:18: Registering file D:\Program Files\B\n 2.3\Win32\CSC.ax (32-bit)
InstallShield 17:42:18: Registering file D:\Program Files\B\n 2.3\x64\Source.ax (64-bit)
InstallShield 17:42:18: Registering file D:\Program Files\B\n 2.3\Win32\Source.ax (32-bit)
InstallShield 17:42:18: Begin Comitting Property Bag
InstallShield 17:42:18: Write KeyList count
InstallShield 17:42:18: Finished Comitting Property Bag

Note that the fifth component, a dll with type library, is not shown in log.
Labels (1)
0 Kudos
(3) Replies
nmsams
Level 7

I have the same issue. Did you ever find a way around it?
0 Kudos
paul388
Level 2

Didn't find a solution in InstallShield.
Had to prepare code for an extra call.
0 Kudos
nmsams
Level 7

Well, my file is an .exe file. How would I go about coding around that?

I tried changing the file to not be a self registering file. But still when I install the major upgrade (that no longer contains that file), I still get the message. So just changing the registration settings didn't help.

Is there a way to just suppress the message box maybe?
0 Kudos