This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
- Revenera Community
- :
- InstallShield
- :
- InstallShield Forum
- :
- MS Office apps invoke my MSI
Subscribe
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Subscribe
- Mute
- Printer Friendly Page
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 13, 2010
01:52 PM
MS Office apps invoke my MSI
I've recently had several users report that, after installing our product, when they try to run Microsooft Word (sometimes other Office apps), they get an error that the msi for our app cannot be found. Our msi is usually cached here:
C:\Documents and Settings\userid\Local Settings\Application Data\Downloaded Installations
The problem occurs when our msi can't be found or accessed in that folder. There've ben several reasons for this and I've been able to work with users to work-around the problem.
My real question is:
"Why are MS Office apps looking for the msi for my app?"
Our iinstallation is Basic MSI and distributed as a "setup.exe". Has anyone else seen this and what's the best way to avoid this?
Thanks!
C:\Documents and Settings\userid\Local Settings\Application Data\Downloaded Installations
The problem occurs when our msi can't be found or accessed in that folder. There've ben several reasons for this and I've been able to work with users to work-around the problem.
My real question is:
"Why are MS Office apps looking for the msi for my app?"
Our iinstallation is Basic MSI and distributed as a "setup.exe". Has anyone else seen this and what's the best way to avoid this?
Thanks!
(3) Replies
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 14, 2010
08:17 AM
The cached .msi may be accessed when Windows Installer thinks something needs to be repaired. Maybe the Office application and your application share a redistributable? To troubleshoot this, you would want to have one of your end users check the Event Viewer in Administrative Tools. The MsiInstaller entries there would probably indicate the component that Windows Installer is trying to repair. Once you know that, you can try to figure out why the issue is occurring.
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 17, 2010
09:39 PM
There is a related post: http://blogs.msdn.com/astebner/archive/2004/08/24/219764.aspx
- Mark as New
- Subscribe
- Mute
- Permalink
- Report Inappropriate Content
‎May 19, 2010
08:47 AM
Thank you DebbieL and HenryL.
The information and the link have proved very useful!
The information and the link have proved very useful!
![](/skins/images/8CE4FAD0DE6F3A6F9D0567434D2D2DAE/responsive_peak/images/icon_anonymous_message.png)