After checking "self register" on a com dll in our application setup always hangs when trying to register this dll on 64-bit Windows 2008 systems (haven't yet tried on 2003, but 2008 is our main target platform). On 32-bit systems the installation succeeds. -The component housing the 64-bit version of the dll is marked as 64-bit - Related running processes at that time running under SYSTEM: msiexec.exe *32 "Windows(R) installer" msiexec.exe "Windows(R) installer" wac32E4.tmp "InstallShield (R) 64-bit Setup Engine" - Related running processes at that time running under logged in user: msiexec.exe *32 "Windows(R) installer" setup.exe *32 "Setup Launcher" ISBEW64.exe "InstallShield (R) 64-bit Setup Engine" - Killing msiexec.exe *32 (SYSTEM) makes the setup resume (as described in another thread regarding 64bit installations hanging) Here is a snippet of the verbose log file just before the hang (at 11:53:35) and continuing after I kill the msiexec.exe *32 process (at 12:01:06). Note the time stamp that is from before the hang, but written after it resumes. [CODE]MSI (s) (8C:84) [11:53:34:159]: Executing op: RegOpenKey(,Key=Component Categories,,BinaryType=0,,) MSI (s) (8C:84) [11:53:34:565]: Executing op: RegCreateKey() MSI (s) (8C:84) [11:53:34:596]: Executing op: RegOpenKey(,Key=Component Categories\{40FC6ED3-2438-11CF-A3DB-080036F12502},,BinaryType=0,,) MSI (s) (8C:84) [11:53:34:596]: Executing op: RegAddValue(Name=409,Value=Embeddable Objects,Attributes=2) MSI (s) (8C:84) [11:53:34:612]: Executing op: RegOpenKey(,Key=Component Categories\{40FC6ED4-2438-11CF-A3DB-080036F12502},,BinaryType=0,,) MSI (s) (8C:84) [11:53:34:612]: Executing op: RegAddValue(Name=409,Value=Controls,Attributes=2) MSI (s) (8C:84) [11:53:34:643]: Executing op: RegOpenKey(,Key=Component Categories\{40FC6ED5-2438-11CF-A3DB-080036F12502},,BinaryType=0,,) MSI (s) (8C:84) [11:53:34:643]: Executing op: RegAddValue(Name=409,Value=Automation Objects,Attributes=2) MSI (s) (8C:84) [11:53:34:659]: Executing op: RegOpenKey(,Key=Component Categories\{40FC6ED8-2438-11CF-A3DB-080036F12502},,BinaryType=0,,) MSI (s) (8C:84) [11:53:34:659]: Executing op: RegAddValue(Name=409,Value=Document Objects,Attributes=2) MSI (s) (8C:84) [11:53:34:675]: Executing op: RegOpenKey(,Key=Component Categories\{40FC6ED9-2438-11CF-A3DB-080036F12502},,BinaryType=0,,) MSI (s) (8C:84) [11:53:34:675]: Executing op: RegAddValue(Name=409,Value=_Printable Objects,Attributes=2) MSI (s) (8C:84) [11:53:34:690]: Executing op: ActionStart(Name=ISSelfRegisterFiles,,) MSI (s) (8C:84) [11:53:34:737]: Executing op: CustomActionSchedule(Action=ISSelfRegisterFiles,ActionType=3073,Source=BinaryData,Target=ISSelfRegisterFiles,CustomActionData=C:\Users\ADMINI~1\AppData\Local\Temp\~4A22.tmp) MSI (s) (8C:C0) [11:53:34:753]: Invoking remote custom action. DLL: C:\Windows\Installer\MSI791A.tmp, Entrypoint: ISSelfRegisterFiles InstallShield 11:53:34: Initializing Property Bag... InstallShield 11:53:34: Getting file count from property bag InstallShield 11:53:34: File Count : 1 InstallShield 11:53:34: Sorting Based On Order... InstallShield 11:53:35: ISBEW64.exe is successfully loaded for 64-bit registration MSI (s) (8C:84) [12:01:06:690]: Executing op: ActionStart(Name=RegisterProduct,Description=Registering product,Template=[1]) InstallShield 11:53:35: Registering file C:\Program Files\MyInstallDir\ComToRegister.dll (64-bit) MSI (s) (8C:84) [12:01:06:690]: Executing op: ChangeMedia(MediaVolumeLabel=DISK1,MediaPrompt=Please insert the disk: 1,MediaCabinet=Data1.cab,BytesPerTick=0,CopierType=2,ModuleFileName=C:\Windows\Installer\13b3a403.msi,,,,,IsFirstPhysicalMedia=1) MSI (s) (8C:84) [12:01:06:690]: Executing op: DatabaseCopy(DatabasePath=C:\Windows\Installer\13b3a403.msi,ProductCode={MyProductCode},,,) MSI (s) (8C:84) [12:01:06:690]: Note: 1: 1402 2: UNKNOWN\Products\MyProductCode\InstallProperties 3: 2 MSI (s) (8C:84) [12:01:06:706]: File will have security applied from OpCode.[/CODE] Please could someone at InstallShield/Flexera look at this. ... View more

I'd like to perform a pre-build step. Specifically creating a CAB-file which will be part of the installation package. Is there a way to add a pre-build script to be run by IS? ... View more

I've run into an issue, due to Marketing setting our major version number well beyond the supported 255 size-limit (as described here). To fix this issue, we'd like to reset the major version number down to something more reasonable at our next upgrade. So if our version right now is 2002.5.1.1 I'd like to force-upgrade that to something like 2.6.2.1. I've created a major upgrade that has the version span of 1.0.0.0 to 2002.5.9.9 (to be able to facilitate upgrade form any patches to the 2002-branch in the future). So far so good, the installer launches and does not give me the "A new version already exists" message, it does in fact act as if it is a fresh install (product code is different, so I guess that's OK). However during the file-operation section of the install I do get a message saying that a newer vesion already exists and the setup is aborted. Can I force the upgrade somehow? I'm thinking I could maybe hack the registry by changing the installed builds version number to "trick" the installer into performing the upgrade, but that's a pretty uggly work-around if it works at all. Another work-around would be to wholly separate the new version (by changing the upgrade code) and then asking the user to uninstall the old version... not a very nice solution. Any suggestions? ... View more

I am having issues performing a major upgrade on a 64-bit OS (Windows 2008) from my old version (created using InstallShield 8.2 Developer) which is mainly 32-bit to a 64-bit install (using InstallShield 2010 Premier). On 32bit systems I have no issue upgrading the IS8.2 build to the IS2010 build, but on 64-bit Windows the existing installation is not detected (Upgrade codes are the same, product code is different). I have read (here) that there are some issues with performing upgrades on 64-bit OS from previous IS versions so that is an issue in and of itself. However, since installations paths are different ("Program Files" vs. "Program Files (x86)") I believe the best thing to do is to install to a new folder as well. What's the best practice for migrating an application from 32-bit to 64-bit from an installer point-of-view? ... View more

I have a license of IS2010 and we will be migrating to it shortly. But our current software uses IS 8.2. Since there is no longer a forum section for this version I'm posting here in the hopes that I can get some help with this final hurdle before we move on to the current IS version. So the issue is that our installer package contains three different system-level drivers. A legacy version for win2000, a 32bit version for win2003/win2008 and a 64bit version for win2003/win2008. These three each have their own subfeature and component with conditions (eg. VersionNT64>0 AND VersionNT>= 502 for the 64bit version) that determine which one is installed. So far so good. On a fresh install the correct driver is installed, for the 32bit versions the Destination is set to "[SystemFolder]Drivers" and for the 64bit version Destination is set to "[System64Folder]Drivers", in both cases the drivers are installed to the System32\Drivers directory as expected. On upgrade of win2000 and 32 bit win2003/2008 the driver is upgraded correctly as well. However when performing an upgrade on a 64bit win2003/2008 the dll is instead installed to SysWow64\Drivers as if it was a 32bit binary! Install log says: [CODE]MSI (s) (8C:E0) [16:27:55:570]: Executing op: ComponentRegister(ComponentId={BFC90265-3ABE-4335-8479-08E49D2EB3F5},KeyPath=C:\Windows\SysWOW64\Drivers\QSFilter.sys,State=3,,Disk=1,SharedDllRefCount=0,BinaryType=1)[/CODE] - I've specifed "Favor Parent" for the Remote Installation for the sub-features and added them as Required Features to the parent feature. - I've specified the 64bit component as a 64-bit Component and set Reevaluate Condition to Yes. - I've set the Previous Package of the Release. - I've tried both making a hybrid product configuration, as well as a 64bit product configuration (with Template Summary set to x64;1033). Any additional suggestions would be much appreciated, I'm running out of ideas and things to search for! ... View more

I'm getting this error during "Preparing to Install..." when I try to install the 64bit release of our product. The File key refered to is for a 32bit component that isn't to be installed on the target system. I've tried both simply letting a Condition determine if it should be installed (in this case VersionNT < 600 and I'm installing on W2k8, i.e. VersionNT = 600) and I've also tried to explicitly exclude the component from the release by setting a release flag ("32bit") which is not used for this particular release. So somewhere there is still a reference said file key, any suggestions on where to look? ... View more

In order to avoid this issue, http://support.microsoft.com/default.aspx?scid=kb;en-us;Q325680 as has been reported for an earlier version of our installer (using InstallShield Developer 8.2) I attempted to add quotes around the service path (using LongPathToQuote) when installing using ServiceAddService, but the function seems to strip away the quotes. In the earlier version of our installer I used the windows API calls directly to install our services and those calls excepted the quotes around the file path. Is there a way to force ServiceAddService to leave the quotes in the path? As it is now, a service installed to C:\Program Files\AppName\Service.exe will not start if you create a file named C:\Program, if quotes are added around the path, i.e. "C:\Program Files\AppName\Service.exe" then the service will start. ... View more