View Full Version : Installer runs when I try to start my App

10-26-2005, 01:12 PM
I've seen this behavior on some (not all) of my client's machines.

After install (ISE 11) when my client tries to run my app, from either a shortcut or the exe file, the Installer runs.

I've read through some threads on this board, but I really don't see any conclusive info about how to find out why this happens and stop it.

Can someone please give me some more detailed info?


10-26-2005, 04:17 PM
That's the behavior of Microsoft Windows Installer (MSI), which self-heals broken components of an installed MSI setup.

One quick way is to look at Event Viewer, under Application, and look for MsiInstaller under Source column.

To get a complete log, you should turn on machine policies (http://msdn.microsoft.com/library/default.asp?url=/library/en-us/msi/setup/machine_policies.asp).

For other discussions, please do a search on self repair and self heal in the forums.

11-02-2005, 03:43 PM
I had my client check their Event Logs and this is what they sent back.

It seems to me that these are all errors generated by installShield - so doesn't that mean it's a problem with ISE or MSI?

My client eventually uninstalled and re-installed which fixed the problem.
(Another indication that this is an ISE or MSI problem)

Here's the Event Log Info:
1) Detection of product '{E856A1F2-7397-4A5C-9F99-9B0ECC78D65A}', feature 'AlwaysInstall', component '{3B694B1F-4410-11D5-A54A-0090278A1BB8}' failed. The resource 'C:\gdiplus.dll' does not exist.
2) Detection of product '{E856A1F2-7397-4A5C-9F99-9B0ECC78D65A}', feature 'AlwaysInstall' failed during request for component '{22056900-C842-11D1-A0DD-00A0C9054277}'

3) Product: printLogic for Matrix v10.5 -- Error 1706.No valid source could be found for product printLogic for Matrix v10.5. The Windows Installer cannot continue.

4) Product: printLogic for Matrix v10.5 -- Configuration failed.

My app includes "gdiplus.dll" which is located in my <SystemFolder> and set to install on the target machine's [SystemFolder].

I get no errors when I build my installer.

So now what?

11-03-2005, 01:45 AM
There may be a problem, albeit not at build time, with your setup.

You will want to have the installation log, which will provide clues as to why the resource 'C:\gdiplus.dll' does not exist.

For 1706 error, you should look it up at Support (http://support.installshield.com/).

11-03-2005, 10:52 AM
Thanks for your help.

I found a potential fix that I'll try based on error 1706 - Set the "copy media to target machine" option to Yes.

BTW - I'm Purdue Alum - 1983...

11-03-2005, 10:47 PM
Class of 1999.

Boilers Up! :D

01-09-2006, 08:52 PM
This is exactly what is happening to me but I can't seem to fix the problem.

My EventViewer shows :

Detection of product '{9A04BDD5-7C60-442E-AAC9-CCFC4D9C1EE9}', feature 'Inpro', component '{303994BA-6487-47AE-AF1D-7AF6088EEBDB}' failed. The resource '' does not exist.
Detection of product '{9A04BDD5-7C60-442E-AAC9-CCFC4D9C1EE9}', feature 'Inpro' failed during request for component '{B86732C0-1BD2-4494-88D8-DC7BF4AE682B}'

I can't find the component "{303994BA-6487-47AE-AF1D-7AF6088EEBDB}" anywhere in my IS Direct Editor. And the '' resource does not exist doesn't help out much.

My verbose log does however contain the "303994BA-6487-47AE-AF1D-7AF6088EEBDB" component ID

I have attached the log hoping someone can help me !!!

BTW - if a user manually uninstall's the product and then installs the new release, it works. If the new release is installed fresh on a pc, it works. This only fails when a user performs a MAJOR upgrade.

What exactly is different between a major upgrade and a manual uninstall ???

01-10-2006, 07:10 AM
Does it happen every time the application is launched? If it happens the very first time the application is launched after the major upgrade, but not subsequent launches, it is most likely to be a problem of the order in which the older version is removed, and self-healing is able to fix the problem. If it happens every time the application is launched, the behavior can be caused by an entirely different, and perhaps more complex, problem.

According to the log, component GUID, 303994BA-6487-47AE-AF1D-7AF6088EEBDB, refers to MS XML files, which are typically included in a merge module. I don't believe you will be able to find any reference of the component GUID in Direct Editor (not applicable to Express Edition) in your ISM project, since merge modules are merged into the MSI file, but not the project file. You will, however, be able to find the reference when viewing MSI file. Also in the log, the assembly component installation is skipped "since the assembly already exits." I don't have the complete picture, but these information may point you in the right direction.

Alison, you may want to post your question in the forum designated for the product and project type used. I would rather not baffle Express Edition users with features, such as Direct Editor, not available in Express Edition.

01-10-2006, 09:36 AM
The only solution I have been able to find is to use the Windows Install Cleanup utility after installation. (@%#$@^%#@ !).

You can find out about it here:

Please note that I encountered this problem after switching from ISE 4 to ISE 11. (I also installed MSI 3.x as a windows update on my Win2K machine)

Prior to the change, this NEVER occurred (@%#$@^%#@ again !).

01-10-2006, 04:28 PM
The good news is by removing the MSXML Merge Module the installation works and when a user runs the specific program the install does not re-start. I will just find a different way to isntall MSXML.

Thankyou for your assistance. I will post any further queries in the appropriate MSI forum. Was just excited to find some useful info on the same problem albiet in a different product.