well, the installer did actually write successfully to the registry. I just need to get rid of the dialog, and I don't understand why it pops up. any clues? ... View more

Here's a little more detail from the log. I XXX'd everything that was company specific. MSI (s) (2C:D0) [15:26:09:194]: Executing op: ProductRegister(UpgradeCodeXXX,VersionString=XXX,HelpLink=XXX,HelpTelephone=XXX,InstallLocation=XXX,InstallSource=XXX\Local\Downloaded Installations\XXX\,Publisher=XXX,URLInfoAbout=XXX,URLUpdateInfo=XXX,,NoModify=1,,,,,Readme=0,,,EstimatedSize=132325,,,,) MSI (s) (2C:D0) [15:26:09:215]: Note: 1: 1406 2: VersionMajor 3: Products\XXX\InstallProperties MSI (s) (2C:D0) [15:26:09:215]: Product: XXX-- Error 1406.Could not write value VersionMajor to key \Products\XXX\InstallProperties. System error . Verify that you have sufficient access to that key, or contact your support personnel. both administrator and system have full control. this project requires administrator. I do not understand why I'm getting this all of a sudden. UAC on/off does not seem to play a role. I turned off virus scanner to test. please help! ... View more

Our company believes that the certificate store is more secure and you can control the exportation of the credentials. You should really consider adding the feature instead of force installshield users to overwrite this exe. I think that'll make support issues more complicated when you send out an update. ... View more

well, that is what I suspected. I guess I can resort to the following: - run the product configurations on different tfs build agents - run as different users, so that they use a different temp directory - set the temp directory prior to running each instance %temp%\config1, %temp%config2,.... thanks, ... View more

I usually use iscmdbld.exe when generating releases. one execution for each product configuration defined in the releases. where I have 4 on some branches, each takes 10 min, so I'd like to execute them in parallel so that all 4 will be done in 10 minutes instead of the usual 40 minutes. ... View more

All x32 programs go into c:\program files (x86). Don't think you want to mix x32 in the x64 directory. ... View more

We determined that the compiler change from 2008 to 2010 caused the error to show up. There was no code change. So we reverted back to 2008, since that was the simplest solution. Still Installshield should be smart enough to know that if cannot get past "Try again the files that have failed." on the same file, there's no point to try it forever. ... View more

I stopped using reg files for that reason. I just add the registry entry in the component's registry and set things like InstallLocation=[INSTALLDIR] ... View more

All I did was convert the project from 2012 to 2013 and that was one of the differences. ... View more

well, 2013 takes less than 2 minutes and 2012 takes over an hour to complete. Good reason to switch. ... View more