1 reply to this topic

[markheth]

I am trying to track down a problem where calling one of our COM objects through VBA inside an excel macro triggers the auto-repair script which runs for about 3-4 minutes, then completes. This happens again as soon as I call the COM object.

I have turned on the verbose logging for MSI, but can't seem to find any specifics on what might be out of date.

The COM object in question seems to be registered fine, although it looks like the ComponentID for this object belongs to a large group of 50 or so files. I guess the resiliency check will check everything in this group?

I'm sort of stuck now on what to check next. Any help would be greatly appreciated.

[Stefan Krueger]

Maybe this article will help:
http://www.msifaq.com/a/1037.htm