This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- Re: Extracting COM results in start of Windows Installer
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jul 03, 2009
10:08 AM
Extracting COM results in start of Windows Installer
Hello,
when I start the creation of a release, I get a box of the Windows Installer at the moment when "Extracting COM data from .." is running.
The WI is not successfull.
It seam to have to do something with IsRegSpy.
A remove and a new installation of IS2010 does not solve the problem.
Thanks in advance!
Johannes
when I start the creation of a release, I get a box of the Windows Installer at the moment when "Extracting COM data from .." is running.
The WI is not successfull.
It seam to have to do something with IsRegSpy.
A remove and a new installation of IS2010 does not solve the problem.
Thanks in advance!
Johannes
(12) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jul 06, 2009
09:47 PM
What are you trying to extract COM information from when you see the message?
Can you also make sure the following filess are in your InstallShield Installation directory...
[INSTALLDIR]System\ISRegSpy.exe
[INSTALLDIR]System\ISRegSpy64.exe
[INSTALLDIR]System\ISRegInj.dll
[INSTALLDIR]System\ISRegInj64.dll
Thanks,
Mike
Can you also make sure the following filess are in your InstallShield Installation directory...
[INSTALLDIR]System\ISRegSpy.exe
[INSTALLDIR]System\ISRegSpy64.exe
[INSTALLDIR]System\ISRegInj.dll
[INSTALLDIR]System\ISRegInj64.dll
Thanks,
Mike
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jul 07, 2009
02:37 AM
Thanks Mike,
but unfortunately these files exist in this directory.
Both 32-bit files have fileversion 16.0.0.328.
Johannes
P.S. After first installation of IS2010 I have uninstalled IS2009 and AdminStudio.
but unfortunately these files exist in this directory.
Both 32-bit files have fileversion 16.0.0.328.
Johannes
P.S. After first installation of IS2010 I have uninstalled IS2009 and AdminStudio.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jul 07, 2009
06:43 AM
Can you check the fle date of
C:\Program Files\Common Files\InstallShield\Shared\IsmAuto.tlb
it should be 6/10/2009
If that is correct, it may not be registered correctly. Try running the attached utility to re-register all of our shared libraries.
C:\Program Files\Common Files\InstallShield\Shared\IsmAuto.tlb
it should be 6/10/2009
If that is correct, it may not be registered correctly. Try running the attached utility to re-register all of our shared libraries.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jul 07, 2009
10:19 AM
That actually may be OK. Did you re-try runnning the build?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jul 08, 2009
03:09 AM
Thanks, but the retry wasn't successful. The problem still occures.
Johannes
Johannes
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jul 08, 2009
10:13 AM
Can you look in the Windows Event viewer and post the details of the Windows Installer error that is getting triggered during COM Extraction?
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jul 08, 2009
10:29 AM
Yes. Can you post the properties of the event? I am curious what is getting triggered.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jul 08, 2009
11:30 AM
The message is:
Ereignistyp: Warnung
Ereignisquelle: MsiInstaller
Ereigniskategorie: Keine
Ereigniskennung: 1004
Datum: 08.07.2009
Zeit: 17:01:25
Benutzer: jn
Computer: my computer
Beschreibung:
Erkennung von Produkt "{AF4D3109-66BB-451F-8068-7301EB97E8E7}", Funktion "Basis.System.UDS" und Komponente "{B71D71B1-5217-4992-A6A4-F47AF06D6476}" fehlgeschlagen. Die Ressource "C:\SKYLINE\admin\appls\ALL\" ist nicht vorhanden.
Weitere Informationen über die Hilfe- und Supportdienste erhalten Sie unter http://go.microsoft.com/fwlink/events.asp.
The builder seams to look for a component of the mainsetup, where this MSM is part of.
The mainsetup is not clean uninstalled, especially parts of the selfregistered files.
I'm clearing now manually the registry.
Then I will try the build the MSM again.
Johannes
Ereignistyp: Warnung
Ereignisquelle: MsiInstaller
Ereigniskategorie: Keine
Ereigniskennung: 1004
Datum: 08.07.2009
Zeit: 17:01:25
Benutzer: jn
Computer: my computer
Beschreibung:
Erkennung von Produkt "{AF4D3109-66BB-451F-8068-7301EB97E8E7}", Funktion "Basis.System.UDS" und Komponente "{B71D71B1-5217-4992-A6A4-F47AF06D6476}" fehlgeschlagen. Die Ressource "C:\SKYLINE\admin\appls\ALL\" ist nicht vorhanden.
Weitere Informationen über die Hilfe- und Supportdienste erhalten Sie unter http://go.microsoft.com/fwlink/events.asp.
The builder seams to look for a component of the mainsetup, where this MSM is part of.
The mainsetup is not clean uninstalled, especially parts of the selfregistered files.
I'm clearing now manually the registry.
Then I will try the build the MSM again.
Johannes
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jul 08, 2009
04:39 PM
Looks like the DLL/OCX/EXE you are trying to COM extract is triggering an MSI Repair when we try to load it for COM extraction.
What file are you trying to COM extract? Can you try to self register it on the machine in questions and see if that kicks off auto repair as well?
I would try to reinstall the product the file originally came from.
What file are you trying to COM extract? Can you try to self register it on the machine in questions and see if that kicks off auto repair as well?
I would try to reinstall the product the file originally came from.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Jul 09, 2009
03:31 AM
Thank you Mike,
the breaking hint was the look at the event viewer.
The problem was the accidental installation or uninstallation of the product, where this MSM was part of.
I agree in your opinion that the COM extract is triggering an MSI Repair, which got no success.
When clearing the registry from this informations, finally with MSIZAP, I've now got a running IS2010.
The manual registration of the Dll, I havn't tried now.
Thank you very much, Mike, for your effort!!!
Johannes
the breaking hint was the look at the event viewer.
The problem was the accidental installation or uninstallation of the product, where this MSM was part of.
I agree in your opinion that the COM extract is triggering an MSI Repair, which got no success.
When clearing the registry from this informations, finally with MSIZAP, I've now got a running IS2010.
The manual registration of the Dll, I havn't tried now.
Thank you very much, Mike, for your effort!!!
Johannes
![](/skins/images/8CE4FAD0DE6F3A6F9D0567434D2D2DAE/responsive_peak/images/icon_anonymous_message.png)