About rune_paulsen

rune_paulsen · ‎Mar 26, 2012

You also need to install the service packs.

rune_paulsen · ‎Mar 19, 2012

I have used SuiteCalc as template Calling a Function in a DLL from a Wizard Page or Window in a Suite Installation, http://blogs.flexerasoftware.com/installtalk/2012/03/validating-user-input-in-a-suite-project.html Added # using "d:\mycode\Mydll.dll int Number=myClass:myMethod::("Input"); I can compile SuiteCalc without error. I have updated the SuiteCalculator.issuite. Added Mydll.dll to support files and packaged files. Compiled SuiteCalculator.issuite without error. But, when i run setup.exe for SuiteCalculator i get this error: [Window Title] Setup Suite Launcher Unicode [Main Instruction] Setup Suite Launcher Unicode has stopped working [Content] A problem caused the program to stop working correctly. Please close the program. [Close the program] [Debug the program] When i debug i get: Could not file or assembly Mydll.dll. The system cannot find the file specified. I have checked the temp folder, MyDll.dll is location in the same folder as SuiteCalc.dll. What do i need to get this working? I have used MyDll in another MSI installer I have CA, call a public method in a managed assembly. This is working without any problem.

rune_paulsen · ‎Mar 18, 2012

If you had open the cmd before you started the installation, this windows will not included your new settings. You need to start a new cmd windows to get your new settings. Regards, Rune

rune_paulsen · ‎Mar 08, 2012

This new exit code is causing problem with our buildsystem. With basic msi, this running fine. An installation have exit code=0 With Suite, and exit code=1, our build system think the installation have failed. Why have you chosen 1 as exit number, and is there something we can do to change this?

rune_paulsen · ‎Mar 08, 2012

Simon, I have the same problem, See thread: http://community.flexerasoftware.com/showthread.php?t=200166 Seems to be something wrong with the suite. Rune

rune_paulsen · ‎Mar 07, 2012

Thanks. This worked. 🙂

rune_paulsen · ‎Mar 01, 2012

When we use an msi installer, the user is not able to start an installation if there is not enough free disk space. But, the Suite dos not seem to have this check enabled. If you install to a disk which don’t have enough space, the installation run, but end with the message, this wizard was interrupted. How can we add disk space check in a suite installer?

rune_paulsen · ‎Feb 29, 2012

To be able to use transaction processing, the user need Windows Installer 4.5. Installed. With an msi installer, we can add these using Prerequisites, for example for Vista x64, Installshield will add Windows6.0-KB958655-v2-x64.msu. The Suite, don’t have Prerequisites, we need to add these as a normal package. But, how do you add a msu as to the Suite?

rune_paulsen · ‎Feb 28, 2012

I have a installation problem with a user, the installation have started to rollback. What does this error number 80070643 tell us? From Installshield log: 2-28-2012[02:53:42 PM]: Engine: property 'ISParcelProgress' value now '66' 2-28-2012[02:53:42 PM]: Engine: property 'ISParcelProgress' value now '67' 2-28-2012[02:53:43 PM]: MSI parcel launch result: 80070643 2-28-2012[02:53:43 PM]: Engine: property 'ISInstallProgress' value now '0' 2-28-2012[02:53:43 PM]: Engine: property 'ISParcelProgress' value now '67'

rune_paulsen · ‎Feb 28, 2012

Thanks for quick answer. The problem was Windows installer version, only 4.0 were installed. But, version 4.5 is needed when i am using transaction installation. After installing Windows6.0-KB958655-v2-x64, i was able to install successfully.

rune_paulsen · ‎Feb 28, 2012

I have a installation problem with a user, the installation have started to rollback. What does this error number 8007007f tell us? From Installshield log: 2-28-2012[09:01:52 AM]: Transaction: parcels installing: no, need elevation: no, any 64-bit: no 2-28-2012[09:01:52 AM]: Transaction: parcels installing: yes, need elevation: no, any 64-bit: yes 2-28-2012[09:01:52 AM]: Engine: request for proxy handler, 0, 0 2-28-2012[09:01:52 AM]: Running with out-proc transaction, starting transaction (if supported) 2-28-2012[09:01:52 AM]: Engine: error 8007007f while running parcel operations 2-28-2012[09:01:52 AM]: Engine: parcel operations completed, sending completed event to UI 2-28-2012[09:01:52 AM]: Engine: property 'ISInstallStatus' value now 'IDS_SUITE_INTERRUPTED' 2-28-2012[09:01:52 AM]: UI DLL: Get: Property=ISInstallStatus Value=IDS_SUITE_INTERRUPTED Return Code=0 Do Installshield have a list of Suite errors, and explanation?

rune_paulsen · ‎Feb 24, 2012

I have removed the package code from Eligibility Condition, and added a new Detection condition. All->MSI Pacakge->Prodduct Code. Now i can. Run the Suite installer, which included V1 of ProgA.msi Run Proga.msi V2 installer, which will do a minor upgrade. Remove the Suite Installer, and the Prog.msi V2 is removed. Is there any disadvantages of doing this change to detect condition?

rune_paulsen · ‎Feb 14, 2012

To be able to remove a MSI installation from commandline, we can use this command. MsiExec.exe /x {C5E3A1D6-1E8A-4BC3-A03E-CBBC4720FCDS} When i try to use the same command for an installed Suite, using the Suite GUID number, i get. [Window Title] Windows Installer [Main Instruction] This action is only valid for products that are currently installed. [OK] How can i uninstall a suite from command line, when i don’t have access to the Suitesetup.exe?

rune_paulsen · ‎Feb 08, 2012

But, i thought the Detection Condition is only used at installation time. But, the problem can be related. Since the new Version2 of the msi installer have a new product code. I tried to add the new product code to the detect condition, the log showed a little progress, but the Suite decided to not uninstall The InstallShield log show(when i remove the suite): Before updating detect condition: (my msi is not detected at all) Evaluating operations for parcel {85E027D8-23A5-46A5-A1AC-E55014DF988E}, parcel is eligible: false, detected state: 0 Final action state for parcel {85E027D8-23A5-46A5-A1AC-E55014DF988E}: 5 Action 5 = No action will be performed for the package After updating detect condition: Evaluating operations for parcel {85E027D8-23A5-46A5-A1AC-E55014DF988E}, parcel is eligible: false, detected state: 1 Final action state for parcel {85E027D8-23A5-46A5-A1AC-E55014DF988E}: 5 Even if detected state is 1 now, the Suite decide not to uninstall = it seems we cannot use an msi to upgrade and msi installed by a Suite. Can InstallShield shed some light on how they have thought we should do upgrades with suites? There is no documentation about this.

rune_paulsen · ‎Feb 06, 2012

Hi I have this installer problem. I have a Suite installer with one MSI packages included I have a new version, version 2, of this MSI installer. First run the Suite installer. Then I run my MSI installer, which will upgrade my MSI product to version 2 Then I go to add/remove and uninstall my Suite. But, this is only removing the Suite entry in add/remove. My msi program is still installed. How do i configure my MSI installer version 2, to get the installed Suite to remove my upgraded MSI program.

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

Re: Cannot open an .ism

Suite: FilenotfoundException when using "#using" in C++: Calling a Function in a DLL

Re: Environment variable not effective after installation.

Installshield.log

Re: Suite: Could not uninstall a feature

Re: Suite and Windows installer 4.5

Suite installer and Track Disk Space

Suite and Windows installer 4.5

Suite installer error 80070643

Problem was windows installer version

Suite installer error 8007007f

Re: How to upgrade an msi include in a Suit installer

How to remove Suite installation from command line