I used to have a similar problem with a Merge Module we were consuming
from a third party, when we would call the COM object on some systems
this would always trigger a repair.
Eventually we traced it back to some .NET conditions included in the
module (we weren't using the wrappers, only native code) causing
problems in specific circumstances. Initially we figured out that it
would never happen for customers with .NET3.5 installed, and
eventually tracked it back to the unused assemblies in the the 3rd
party MSM - after removing the unused assemblies from the modules
manually the problem went away :)
In summary, take a look at any conditions surrounding and components
that the COM object depends on, or that depend on the COM object -
also a verbose log should help debug.
Sascha
On Tue, May 11, 2010 at 6:57 PM, Igor Paniushkin <ipaniush...@sdl.com> wrote:
> Hi All,
>
>
>
> We have a problem in our installer, that sometimes when specific COM
> object is called, installer starts silence repair. And I see next error
> messages in event log:
>
> Detection of product '{955F9F12-0EF2-483F-A50A-12A8C6C9AD8C}', feature
> 'MyFeature' failed during request for component
> '{81AD12A8-5FB1-4A7D-8709-E45C7376AADE}'
>
>
>
> Detection of product '{955F9F12-0EF2-483F-A50A-12A8C6C9AD8C}', feature
> 'MyFeature', component '{ED20D88B-80C5-488D-9036-BE455B66D0FD}' failed.
> The resource '' does not exist.
>
>
>
> I tried to find out what is wrong with these components, but it seems to
> me everything ok. All features in installer marked as non advertisement.
> {ED20D88B-80C5-488D-9036-BE455B66D0FD} component contains some class and
> progid elements in it, but Wix transform them into registry keys, so I
> should not expect that these keys will registered as advertised. Also I
> found strange that resource is empty in second warning message, I saw on
> internet similar messages, but resource was not empty there.
>
> I found some similar topics about it (like,
> http://blogs.msdn.com/astebner/archive/2005/01/13/352649.aspx), but
> Aaron was talking about self registration and it is not a case for my
> installer.
>
>
>
> Did anybody have the similar issue? Maybe somebody can point me into
> right direction, where to look?
>
>
>
> Best Regards,
>
> Igor
>
> </pre>
> <BR style="font-size:4px;">
> <a href = "http://www.sdl.com";><img src="http://www.sdl.com/images/email
> logo_150dpi-01.png" alt="www.sdl.com" border="0"/></a>
> <BR>
> <font face="arial" size="2" "><a href = "http://www.sdl.com";
> style="color:005740; font-weight: bold">www.sdl.com</a>
> <BR>
> <BR>
> <font face="arial" size="1" color="#736F6E">
> <b>SDL PLC confidential, all rights reserved.</b>
> If you are not the intended recipient of this mail SDL requests and requires
> that you delete it without acting upon or copying any of its contents, and we
> further request that you advise us.<BR>
> SDL PLC is a public limited company registered in England and Wales.
> Registered number: 02675207.<BR>
> Registered address: Globe House, Clivemont Road, Maidenhead, Berkshire SL6
> 7DY, UK.
> </font>
>
> ------------------------------------------------------------------------------
>
> _______________________________________________
> WiX-users mailing list
> WiX-users@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wix-users
>
------------------------------------------------------------------------------
_______________________________________________
WiX-users mailing list
WiX-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wix-users
