About GarrettDyer

Domnitch · ‎Feb 11, 2020

IS 2019 R3 - the same problem Unspecified error ISWiAutomation.ISWiRelease.BuildInternal ISWiAutomation.ISWiRelease.Build Code: 800A4005 Source: ISWiAuto25

MSIYER · ‎Jul 19, 2011

Its not about what IDE you use to package the MSI. Its about how the Windows Installer Engine reacts to situations. If it detects keyfile missing from a component, it will repair and replace the keyfile. We can tweak the registry if we understand the various schemes that Installer Engine employs to obscure install data from users(COMPONENT GUIDs and their storage mechanism etc...). But can we be ever sure of what all we might be breaking?

deecole · ‎Feb 10, 2011

I'm seeing the same behavior with IS 2011, that TempFolder ends with \2 in immediate execution, and without the \2 in deferred execution. David

GarrettDyer · ‎Nov 30, 2010

Thanks for the reply Bob. In my research, I found this site which details what needs to be done to enable IIS 6 Compatibility on Windows Server 2008. To install IIS 7.0 features for Metabase via ServerManagerCmd.exe, use the following command line: ServerManagerCmd -install Web-Server ServerManagerCmd -install Web-Metabase ServerManagerCmd -install Web-WMI ServerManagerCmd -install Web-Lgcy-Scripting ServerManagerCmd -install Web-Lgcy-Mgmt-Console This should allow my old IIS 6 vbscripts to continue to work, although I've got a bit of testing to work through now.

GarrettDyer · ‎Nov 17, 2010

hidenori wrote: Try consuming the event from the ISWiRelease object and see if you are getting any status message from the build. I didn't go this far, but I used your VB code to write a build routine for vbscript and it works as expected. So that tells me the COM object is alive and well. (EDIT: If you want to walk me through how to construct the VB executable, I'm all ears...I have no experience with it.) Additional info: I tested my Perl build using a 2010 project, and it built correctly (reporting 2 warnings). I then added code to make it fail and it correctly reported 1 failure and 2 warnings. I then upgraded the project to 2011 and the build didn't work (and didn't report build errors and warnings). This just doesn't make sense.

Srini1975 · ‎Jul 28, 2010

I was trying to do the same thing today (getting a com+ application to show up, without actually installing it on the machine). Is there a workaround by which we can do this. I am using Installshield 2010.. Thanks Srini

Online Status	Offline
Date Last Visited	‎Oct 31, 2019 01:39 PM

IS 2019 R3 - the same problem

Re: Manually replace a key file laid down by MSI

Re: TEMP env variable wrong in IS2011

Re: Enabling IIS 6 Management Compatibility

Re: Automation Interface: Build method isn't building project

Re: Adding a COM+ Application to a Basic MSI project

Re: general automation question

Re: Automation Interface - Your Opinion??

Re: adding files programmatically, possible?

Re: How to upgrade using Basic MSI Project

Re: Replacement for PackageFortheWeb Tool

Re: Control file for ISCmdBld.exe (automatic build)

Manually replace a key file laid down by MSI

TEMP env variable wrong in IS2011

Re: How do I get the SQL Server Name

Re: Building InstallShield 2011 projects with previous InstallShield versions