Our build numbers change with every build (XX.XX.YYDAYOFYEAR.DailyReleaseNumber-Incremented). We build using TFS and issue an InstallShield command line to build the installer through a post-build script (powershell). We use Basic MSI for our installer project. I'm currently manually updating the Upgrade Item for ISPreventDowngrade so that the minimum version is in the ball-park of what the version will be when we release. Since we may not know exactly what the version will be until build time, is there a way to set the Minimum Version in the IsPreventDowngrade upgrade item to be the new build number instead of manually editing it every time we run a build (or predicting a number that will be used in the future). ... View more

I'm doing a Basic MSI project in InstallShield 2013 Professional. The installer is meant to deliver a handful of files to specific locations, register a couple of windows services and start them. Stepping through the install sequence, when I get to the "ExecuteAction", which occurs right after the "SetupProgress" window, I get the following error: "Error 1719. Windows Installer service could not be accessed. Contact your support personnel to verify that it is properly registered and enabled." My installed version of msiexec is Windows ® Installer. V 5.0.7601.17514. I can run the installer manually (without debugging) and it makes it to the end just fine. It's only when I try to get past that step in the MSI debugger. The sequence I ran is as follows: ... (initialization stuff).... InstallWelcome (Not Installed) ReadyToInstall SetupProgress ExecuteAction <<------ It breaks running this (InstallExecuteSequence starts) ... do stuff to install ... ... View more