5 replies to this topic

[igodunov]

I know that someone previously installed the product, than tried to uninstall it, met some troubles, finally used installer cleanup utility. Now installation breakes down due to some files (components), required for custom actions, doesn't installed (all of them have System32 as target directory).

What problem can cause such behaviour? Sample message from installer log here:

Component: C__45A3CF1ADB77146F86C248FFBB641A3B;
Installed: Absent; Request: Local; Action: Null

Component has no install condition.

[Stefan Krueger]

Look for SELMGR errors in the log.

[igodunov]

Thank You for advise. But I didn't find any SELMGR errors in the log. Maybe, '/l*v' command line parameter is insufficient (for logging this error type)?

Edited by igodunov, 29 June 2006 - 07:48.

[Stefan Krueger]

Then I guess there's another cause for the problem. What's the state (installed/request/action) of the associated feature? What is the overwrite information (version comparison result) in the log for the key file of that component?

[VBScab]

The /l*v logging switch provides the most information you're going to get from logging.

In this situation, I'd probably run FileMon and RegMon (freeware from www.sysinternals.com) to see what WI is "seeing" when it's trying to install your package. My guess would be that some component GUIDs have got screwed.

Remember to use the 'Include' and 'Exclude' features in FileMon/RegMon to exclude processes you're not interested in - these tools trap EVERYTHING. 'Include' MSIEXEC.EXE (the WI process) and 'Exclude' stuff like Explorer.EXE, your a/v EXEs, svchost.EXE, etc, etc.

[igodunov]