About Ken_Alverson

Ken_Alverson · ‎Sep 28, 2017

Ken Alverson wrote: I need to append a folder to a custom destination path returned by the dialog DestinationFolder. Is there an easy way to do this in the IDE? The resulting path would be: custom_path/my_appended_folder/my_product_install_folder/ I figured out how to do this, but was surprised to find out via the log file that there were many internal properties containing the install path I did not know about that also had to be modified. When my first install failed to install everything in the appended folder, I found in the install log many other paths being setup to what looked like feature or component named properties. Once I added code to modify all the ones in the log file, the next install worked as expected.

Ken_Alverson · ‎Sep 22, 2017

I need to append a folder to a custom destination path returned by the dialog DestinationFolder. Is there an easy way to do this in the IDE? The resulting path would be: custom_path/my_appended_folder/my_product_install_folder/

Ken_Alverson · ‎Aug 18, 2017

Just a note of warning about updating InstallShield 2015 IDE. A couple of days ago, I updated my InstallShield 2015 premier IDE with service pack 2. It turns out when you do that you also have to update any build machines with the standalone install for service pack 2 as well. Our build engineer looked into an issue that popped up on our Jenkins build server; he compared two MSI project files, one that worked for digital signing and the newer one that did not. He found that after updating the IDE to service pack 2, a new parameter "?auto" is appended to the path to the certificate to use for signing. After updating the Jenkins build server with the standalone service pack 2, the standalone build started working again on the project file with the newly added parameter.

Ken_Alverson · ‎Aug 16, 2017

I found the issue and it is my fault. I had a custom action unzipping a file which overwrote the installed file with an older file contained inside the zip file. Ops, I removed the custom action since I've since went to using a wrapped version of launch4j instead of using the zip file to contain the objects.

Ken_Alverson · ‎Aug 16, 2017

My project is building and installing an older messages_en_US.properties file even though the IDE shows the file with the correct modification date/time. The contents and date modification values match an older file that is under source control, but was replaced with a newer one. I don't know how the project is still being built with the older file when only the newer file is available on the hard drive and shows up correctly in the IDE. I've deleted all the intermediate files before building. And the uninstall does not leave the old file out there either. How can it still be in a new build? All the other files in the same folder are being built correctly. Can someone suggest what might be wrong here?

Ken_Alverson · ‎Apr 11, 2017

chad.petersen wrote: Yes, if I log into the Flexera Product and License center and go to any of the listed Stand-alone build versions and click on "Licenses" next to any of them then I can see all of our SAB licenses, the MAC address they are assigned to and I can "Return" them. I am an admin on our account so I can return licenses that were generated by anyone in our company. I hope that helps Chad Thanks, I found the help PDF on the subject and returned our license yesterday. I should check the help first I guess rather than post. I am currently waiting on our service desk to provide a permanent IP and MAC for the new VM so it won't change on us. 🙂

Ken_Alverson · ‎Apr 10, 2017

This might not be a good place to post this, but our service department upgraded the hardware on our build machine (new VM), but this also broke our standalone build license in the process. They tell us it is dangerous to make the new VM report the same NIC card address to make the old license work again. I have already used 4 out of the 5 licenses I have. I hate to burn up the last one because of this upgrade of the hardware. Is there anyway to "deactivate" the dead license so I can recreate a new one without burning up the last license slot?

Ken_Alverson · ‎Apr 07, 2017

chad.petersen wrote: What I'd try is to go into each of those Components and find the entry called ".NET Scan at Build" and change those to "None" and rebuild and try again, if you haven't tried that yet. The default is "Dependencies and Properties" which can cause the resulting MSI to include extra things beyond what you know you authored. It's one thing to try, at least. That would be my top suspect sort of loosely based on what you are describing. Chad Thank you Chad, this resolved our issue with the random error messages. I installed and uninstall several times on a machine that always displayed errors before and now it is clean. No more errors. Thank you for your fast and accurate resolution to our issue.

Ken_Alverson · ‎Apr 06, 2017

I created a very small installer for installing three dll's to global assembly cache. For some reason we are seeing errors on a totally unrelated module. The error is Error 1905. Module C:\WINODWS\SysWOW64\cwbunapi.dll failed to unregister. HRESULT -2147220472. Contact your support personnel. Nowhere in our msi project file is this dll referenced at all. It is a bit of a mystery to me why this error is displayed on uninstall. The error does not affect the results of the install or uninstall, but it is a bit annoying to see any strange error at all. Is there a way to fix this issue?

Ken_Alverson · ‎Nov 17, 2016

hidenori wrote: Make sure that you use the key name of your feature in the conditional statement, instead of the display name. [ATTACH=CONFIG]11242[/ATTACH] Thanks, this worked for me. The action is now being called or not called based on the selection.:)

Ken_Alverson · ‎Nov 16, 2016

After much searching on the internet I found someone said this would work &featurename=3 Or (!featurename=3 And Not &featurename=2 AND NOT REMOVE="ALL" ) I put the following on my condition line, but it does not run. I am using an execute custom action in deferred system context. I don't get any install errors, but the custom action does not appear to run. ID_STRING3 is the string name of my feature - should be specified some other way? &ID_STRING3=3 Or (!ID_STRING3=3 And Not &ID_STRING3=2 AND NOT REMOVE="ALL" ) How should I be setting up the condition to get a custom executable to run if a feature is selected on install?

Ken_Alverson · ‎Nov 15, 2016

It's really annoying to have to change it for 300 components after they have been added. The warning message I am getting is this one: ISDEV : warning -7143: Component utf8_and_euc_jp.dll installs to a 64-bit folder but is not marked as a 64-bit component. This may result in an incorrect installation path for this component's files.

Ken_Alverson · ‎Aug 24, 2016

Thank you for your reply. This worked well to control the selection radio buttons.

Ken_Alverson · ‎Aug 24, 2016

My solution to this was to add a yes/no confirmation dialog on the cancel button for the custom action explaining the situation. i.e. the install can not continue... if you answer yes, the install will be canceled and a rollback will occur... a 1722 error will be displayed next, click ok. The text wasn't exactly like this but you get the idea.

Ken_Alverson · ‎Aug 24, 2016

Hysteresis wrote: I was faced with a similar scenario during one of my product upgrade sequences where we had a particularly stubborn service to shut down. In the end I had to author custom actions to stop the service with various timeouts and ultimately even kill the service process in a 'dirty' shutdown if the stop timeouts were triggered. I don't know of any other method - sorry. I was able to use DirectEditor to add a record to table ServiceControl that resolved my uninstall issues. The two services involved had built in dependencies, so I only had to stop one of them to get them both stopped. I defined the record name in field s72, the service name in field s255, the stop service during uninstall event value of decimal 32 in field i2, the wait an additional 30 seconds (value 1) in field I2, and finally the component name in field s72 (the executable for the service). The uninstall did not require a reboot after that and all the files got removed on an uninstall (clean uninstall). Well the product folder was left behind, but everything else is gone which is probably as good as it is going to get.:)

Online Status	Offline
Date Last Visited	‎Mar 18, 2019 12:10 PM

Re: appending a folder to DestinationFolder

appending a folder to DestinationFolder

Another note of warning for service pack 2 - error on digital signing

Re: After updating to 2015 SP2 - having a file issue

After updating to 2015 SP2 - having a file issue

license center

build machine hardware changed on us - license no longer good

Re: Basic MSI installing or uninstall to Gobal Assembly Cach

Basic MSI installing or uninstall to Gobal Assembly Cach

Re: How to condition a custom action to run if a feature is selected for install

How to condition a custom action to run if a feature is selected for install

Anyway to set the default on components to x64-Bit Component

Re: How to disable install button when all feature checkboxes are unchecked by user?

explaining the 1722 error via confirmation dialog before the 1722 error

DirectEditor - added an entry to ServiceControl - solved my problem