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
- :
- some dependent file missing?
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
‎Feb 18, 2010
03:49 AM
Not able to extract class com information
I am using IS2009 basic MSI.
I am not able to extract the class related com information in one particular build machine.
Where as in other test machine, for the same dll, the Class related com information is successfully extracted.
The build log says successfully extracted the com information. But class id is missing for the component.
I faced this problem earlier also and later worked with manul registration.
But this is happening for the second time so decided to get deeper into this.
Please suggest me as to what can be going wrong with the com extract.
The Dll has the valid com related information and successfully registers with regsvr32.
Thanks in advance.
Regards,
Sarfaraz
I am not able to extract the class related com information in one particular build machine.
Where as in other test machine, for the same dll, the Class related com information is successfully extracted.
The build log says successfully extracted the com information. But class id is missing for the component.
I faced this problem earlier also and later worked with manul registration.
But this is happening for the second time so decided to get deeper into this.
Please suggest me as to what can be going wrong with the com extract.
The Dll has the valid com related information and successfully registers with regsvr32.
Thanks in advance.
Regards,
Sarfaraz
(2) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Mar 31, 2010
07:28 AM
Maybe there is a dependent file missing on the special machine so that the COM extraction could not take place completely. Did you use the tool RegSpyUI to see the COM extraction on all build machines? You can also use the tool depends to check for missing files.
Barbara
Barbara
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎Apr 05, 2010
01:49 AM
Better u can take help of dependency walker(DW) and try to open the dll or ocx in DW and find out the missing dependency dll's.