1 reply to this topic

[LrngToFly]

Hello-
I have an application that is installed with Installshield 12 basic MSI. It utilizes c:\windows\system\MSCOMCTL.OCX and it is installed via Microsoft's merge module Microsoft Windows Common Controls (6.0) mscomctl.msm. I got the latest set of these merge modules from:
http://www.microsoft...&displaylang=en.
My application runs an Excel macro. We're deploying against Office 2003. My application loads the sheet, reads and writes some cells, but when it runs a macro that's a part of the excel sheet, the Windows Installer repair starts.
I get this in the Applications section of the Event Log:
Detection of product '{646EC6EA-5494-4E51-8597-1894D235300C}', feature 'ScicloneICP' failed during request for component '{22056900-C842-11D1-A0DD-00A0C9054277}'
When I run the .vbs utility here:
http://www.installsi...ifaq/a/1037.htm
I find out that component {22056900-C842-11D1-A0DD-00A0C9054277} is MSCOMCTL.OCX and that Office 2003 has two entries against it and that my software has one entry.
{22056900-C842-11D1-A0DD-00A0C9054277} is used by:
Microsoft Office Professional Edition 2003 {90110409-6000-11D3-8CFE-0150048383C9} at C:\WINDOWS\system32\MSCOMCTL.OCX
Microsoft Office Professional Edition 2003 {00000000-0000-0000-0000-000000000000} at C:\WINDOWS\system32\mscomctl.ocx
Caliper Life Sciences Maestro Workstation Software {646EC6EA-5494-4E51-8597-1894D235300C} at C:\WINDOWS\system32\mscomctl.ocx
It appears to me that the component is always present and registered- so for the life of me, I have no idea why the windows installer repair is popping up. Can anyone help with ideas for:
-why is this happening
-if I can't figure out and fix the root cause, is there a way for me to configure my installshield project to not include mscomctl.msm. Installshield doesn't allow me to unselect it- apparently it knows that components in my install use it. I'd be happy to get the component on the machine another way if that's what it takes.
Thanks much! Andy

[Stefan Krueger]

I guess you can't unselect it because some other module in your project specified it as requirement (module dependency).

It might be a problem with registry entries - HKCR mapping to HKLM and HKCU.