This website uses cookies. By clicking Accept, you consent to the use of cookies. Click Here to learn more about how we use cookies.
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
sooraj_er
Level 4
- Revenera Community
- :
- About sooraj_er
Dec 06, 2019
03:05 AM
I have a requirement as described below: There are two features F1 and F2 in my msi. During a major upgrade, user should be able to select either F1 or F2 for upgrade. If he selects F1, F1 should upgrade and F2 should remain with old version. Is this possible? If so how can I achieve this? When I try using FeatureRequestState("F1")=3 during upgrade, F2 is getting deleted and vice versa. FeatureRequestState("F1")=-1 does not work, the code fails during upgrade at this step.
... View more
Labels
- Labels:
-
InstallShield Legacy Versions
Apr 04, 2017
06:52 AM
Thanks Chad, your second input helped me to remove the message box.
... View more
Dec 13, 2016
03:28 AM
Hi, When a setup.exe runs in minor upgrade, the first message box to be displayed is "This setup will perform an upgrade of . Do you want to continue?” . This text is not seen anywhere in the ism or msi. Is it possible to edit this text? Thanks, Sooraj
... View more
Labels
- Labels:
-
InstallShield 2014
Dec 07, 2016
04:45 AM
The issue was that few dynamic components were there in my 6.0 msi. In 6.1, the GUID of these components got changed. I had to edit the msi after building to update these component GUIDs back to 6.0 GUID's to make minor upgrade work. I used "C:\Program Files (x86)\Microsoft SDKs\Windows\v7.1A\Bin\MsiDb.exe" to update the msi after build.
... View more
Dec 07, 2016
04:42 AM
I fixed this by editing the msi using "C:\Program Files (x86)\Microsoft SDKs\Windows\v7.1A\Bin\MsiDb.exe" to add "NOT IS_MINOR_UPGRADE" condition to the .Commit, .Install and .Rollback custom actions to prevent .net installer class getting called during minor upgrade. This exe was called after building the msi in the build machine.
... View more
Dec 05, 2016
06:57 AM
Hi, Our basic MSI project has two merge modules. We are developing the new version (6.1) which supports the below upgrades: 4.0 to 6.1, 5.0 to 6.1 (Major upgrades) 6.0 to 6.1 (Minor upgrade) The major upgrades to 6.1 are working perfectly fine but one of the merge module is not getting upgraded during the minor upgrade. There are no components removed or renamed from 6.0 to 6.1. Changes are there only in the file versions (6.0.xxx.0 to 6.1.0.0). The log file doesn't give any hint. For all the components in the merge module (which does not upgrade), the minor upgrade log file says Installed: Local; Request: Null; Action: Null. How can we find the reason why the components in this merge module alone is not getting installed during minor upgrade? Thanks, Sooraj
... View more
Labels
- Labels:
-
InstallShield 2014
Nov 28, 2016
03:42 AM
HI, We are registering our windows services using the .Net installer class arguments in the component settings. We do not want the service to be registered during a minor upgrade. I tried setting the component condition to "NOT IS_MINOR_UPGRADE". Even then, the installer is trying to register the services with the .Net installer class arguments supplied and gives error message. From the install log file, it says "Action 0:04:44: _B3B87854DA1D1A89D2DD93DB4ABEE65B.install. ". Which custom action is getting called during this action? How can I prevent this from running during a minor upgrade? Thanks, Sooraj
... View more
Labels
- Labels:
-
InstallShield 2014
Jun 12, 2014
01:14 AM
Thanks for the reply. I tried removing the system restore. But the delay is still there. On further analysis I found that the delay is there when I use a signed msi. Unsigned msi installs without delay. Signed msi installtion introduces a delay between the below two steps (From the log file): MSI (s) (04:60) [02:35:29:667]: File will have security applied from OpCode. MSI (s) (04:60) [02:35:30:527]: SOFTWARE RESTRICTION POLICY: Verifying package --> 'C:\Users\administrator.POC1\Desktop\09-Jun-2014\DevDebug 6.0.1244.1\Installation\RapidcommWeb\x64\RAPIDCommWeb.msi' against software restriction policy MSI (s) (04:60) [02:35:30:527]: SOFTWARE RESTRICTION POLICY: C:\Users\administrator.POC1\Desktop\09-Jun-2014\DevDebug 6.0.1244.1\Installation\RapidcommWeb\x64\RAPIDCommWeb.msi has a digital signature MSI (s) (04:60) [02:36:01:028]: SOFTWARE RESTRICTION POLICY: C:\Users\administrator.POC1\Desktop\09-Jun-2014\DevDebug 6.0.1244.1\Installation\RapidcommWeb\x64\RAPIDCommWeb.msi is permitted to run at the 'unrestricted' authorization level. Is the software restriction policy check mandatory? Is there anyway I can skip this and make the installation faster? Thanks, Sooraj
... View more
Jun 11, 2014
04:53 AM
The installer is getting stuck for about 30 seconds at 0% progress in Setup Progress dialog (After clicking Install button in Ready to Install dialog). The Log file captures the below entries during this delay in Windows Server 2008 and 2012: MSI (s) (04:60) [02:35:29:652]: Machine policy value 'DisableUserInstalls' is 0 MSI (s) (04:60) [02:35:29:652]: Note: 1: 2203 2: C:\Windows\Installer\inprogressinstallinfo.ipi 3: -2147287038 MSI (s) (04:60) [02:35:29:667]: Machine policy value 'LimitSystemRestoreCheckpointing' is 0 MSI (s) (04:60) [02:35:29:667]: Note: 1: 1715 2: RAPIDComm Web Server MSI (s) (04:60) [02:35:29:667]: Calling SRSetRestorePoint API. dwRestorePtType: 0, dwEventType: 102, llSequenceNumber: 0, szDescription: "Installed RAPIDComm Web Server.". MSI (s) (04:60) [02:35:29:667]: The call to SRSetRestorePoint API failed. Returned status: 0. GetLastError() returned: 127 MSI (s) (04:60) [02:35:29:667]: File will have security applied from OpCode. MSI (s) (04:60) [02:35:30:527]: SOFTWARE RESTRICTION POLICY: Verifying package --> 'C:\Users\administrator.POC1\Desktop\09-Jun-2014\DevDebug 6.0.1244.1\Installation\RapidcommWeb\x64\RAPIDCommWeb.msi' against software restriction policy MSI (s) (04:60) [02:35:30:527]: SOFTWARE RESTRICTION POLICY: C:\Users\administrator.POC1\Desktop\09-Jun-2014\DevDebug 6.0.1244.1\Installation\RapidcommWeb\x64\RAPIDCommWeb.msi has a digital signature MSI (s) (04:60) [02:36:01:028]: SOFTWARE RESTRICTION POLICY: C:\Users\administrator.POC1\Desktop\09-Jun-2014\DevDebug 6.0.1244.1\Installation\RapidcommWeb\x64\RAPIDCommWeb.msi is permitted to run at the 'unrestricted' authorization level. In Windows 7 the delay is between different tasks as per the log file!: SI (s) (DC:9C) [15:16:38:989]: Machine policy value 'DisableUserInstalls' is 0 MSI (s) (DC:9C) [15:16:39:004]: Machine policy value 'LimitSystemRestoreCheckpointing' is 0 MSI (s) (DC:9C) [15:16:39:004]: Note: 1: 1715 2: RAPIDComm Web Server MSI (s) (DC:9C) [15:16:39:004]: Calling SRSetRestorePoint API. dwRestorePtType: 0, dwEventType: 102, llSequenceNumber: 0, szDescription: "Installed RAPIDComm Web Server.". MSI (s) (DC:9C) [15:17:10:329]: The call to SRSetRestorePoint API succeeded. Returned status: 0, llSequenceNumber: 254. MSI (s) (DC:9C) [15:17:10:345]: File will have security applied from OpCode. MSI (s) (DC:9C) [15:17:11:234]: SOFTWARE RESTRICTION POLICY: Verifying package --> 'C:\Users\IC016524\Desktop\RapidcommWeb\x64\RAPIDCommWeb.msi' against software restriction policy MSI (s) (DC:9C) [15:17:11:234]: SOFTWARE RESTRICTION POLICY: C:\Users\IC016524\Desktop\RapidcommWeb\x64\RAPIDCommWeb.msi has a digital signature MSI (s) (DC:9C) [15:17:11:328]: SOFTWARE RESTRICTION POLICY: C:\Users\IC016524\Desktop\RapidcommWeb\x64\RAPIDCommWeb.msi is permitted to run at the 'unrestricted' authorization level. How can I remove this delay from the installer? Thanks, Sooraj
... View more
Labels
- Labels:
-
InstallShield 2013
Feb 19, 2014
03:22 AM
The below condition should work: (VersionNT > 501) OR (VersionNT = 501 AND ServicePackLevel = 3) Regards, Sooraj
... View more
Dec 18, 2013
05:28 AM
After further analysis, I found that three components with ".Net installer class" set to "Yes" is causing this error. If I set them to "No" and take a build, it works fine. So the issue seems to be this: setting ".Net installer class" set to "Yes" is making the standalone exe to access C:\WINDOWS\Microsoft.NET\Framework64\v4.0.3031964\InstallUtilLib.dll which doesnt exist. Instead it should access C:\WINDOWS\Microsoft.NET\Framework64\v4.0.30319\InstallUtilLib.dll as I specify this path using -t argument to IsCmdBld.exe. I am confused how to proceed further as I cant take a build with ".Net installer class" set to "No" for these components as they hold .Net exe's which should be registered during installation.
... View more
Dec 17, 2013
10:53 PM
Hi Lee, Thanks for the reply. I am getting the same error after setting merge modules path in registry. Infact the merge modules are getting added without error. The error occurs while adding custom actions. Below is the sequence from the build log file: ........... ........... Building scanned MsiAssemblyName records Adding Installer namespace CustomActions for .NET assemblies ISDEV : error -6243: InstallUtilLib.dll cannot be located on your system. This file is required for Installer custom actions. You can set the path to InstallUtilLib.dll using Tools | Options and/or specify the path with the -t command line build option. The file is part of the Microsoft .NET Framework redistributable. C:\WINDOWS\Microsoft.NET\Framework64\v4.0.3031964\ ISDEV : error -6241: Internal build error Validating Custom Action sequencing Validating architecture for custom actions. .......... ......... Thanks, Sooraj
... View more
Dec 17, 2013
01:08 AM
InstallShield 2013 standalone build is giving the below error after migrating the ism to 2013: ISDEV : error -6243: InstallUtilLib.dll cannot be located on your system. This file is required for Installer custom actions. You can set the path to InstallUtilLib.dll using Tools | Options and/or specify the path with the -t command line build option. The file is part of the Microsoft .NET Framework redistributable. c:\Windows\Microsoft.NET\Framework\v4.0.3031964\ We are using the below command for the build. Same command works fine with 2010 standalone build and 2010 ism. "C:\Program Files (x86)\InstallShield\2013\System\IsCmdBld.exe" -p "D:\Projects\RAPIDComm_tfs\Nimrod\Install\src\Setup\Rapidcomm 6.0 Server Debug 64.ism" -a "NotDistributed" -r "CDWinx64" -o "D:\Projects\RAPIDComm_tfs\Nimrod\Install\src\Setup" -b "C:\TestBuilds" -t "C:\WINDOWS\Microsoft.NET\Framework64\v4.0.30319" >> "C:\Setup_server_x64_debug.log"
... View more
Labels
- Labels:
-
InstallShield 2013
Jul 11, 2013
01:12 AM
Can we purchase installshield 2013 license and install installshield 2010 using it? Also, is it possible to use installshield 2010 stand alone build exe to build an installshield 2013 ism?
... View more
Labels
- Labels:
-
InstallShield 2013
Jul 31, 2012
04:27 AM
Thanks a lot for your reply. I am exploring DTF so that I can use it in my MSI.
... View more
Latest posts by sooraj_er
Subject | Views | Posted |
---|---|---|
884 | Dec 06, 2019 03:05 AM | |
1472 | Apr 04, 2017 06:52 AM | |
2687 | Dec 13, 2016 03:28 AM | |
948 | Dec 07, 2016 04:45 AM | |
977 | Dec 07, 2016 04:42 AM | |
1659 | Dec 05, 2016 06:57 AM | |
1729 | Nov 28, 2016 03:42 AM | |
2182 | Jun 12, 2014 01:14 AM | |
3874 | Jun 11, 2014 04:53 AM | |
989 | Feb 19, 2014 03:22 AM |
Activity Feed
- Posted Can we upgrade features selectively? on InstallShield Forum. Dec 06, 2019 03:05 AM
- Posted Re: Minor upgrade initial message box text change on InstallShield Forum. Apr 04, 2017 06:52 AM
- Posted Minor upgrade initial message box text change on InstallShield Forum. Dec 13, 2016 03:28 AM
- Posted Re: Merge module not getting upgraded (Minor upgrade) on InstallShield Forum. Dec 07, 2016 04:45 AM
- Posted Re: How to prevent .Net installer class getting called during minor upgrade? on InstallShield Forum. Dec 07, 2016 04:42 AM
- Posted Merge module not getting upgraded (Minor upgrade) on InstallShield Forum. Dec 05, 2016 06:57 AM
- Posted How to prevent .Net installer class getting called during minor upgrade? on InstallShield Forum. Nov 28, 2016 03:42 AM
- Posted Re: Setup progress stuck at 0% progress for some time on InstallShield Forum. Jun 12, 2014 01:14 AM
- Posted Setup progress stuck at 0% progress for some time on InstallShield Forum. Jun 11, 2014 04:53 AM
- Posted Re: Install Condition Greather Or Equal Win XP Sp3 on InstallShield Forum. Feb 19, 2014 03:22 AM
- Posted Re: Standalone build error (ISDEV : error -6243: InstallUtilLib.dll cannot be located) on InstallShield Forum. Dec 18, 2013 05:28 AM
- Posted Re: Standalone build error (ISDEV : error -6243: InstallUtilLib.dll cannot be located) on InstallShield Forum. Dec 17, 2013 10:53 PM
- Posted Standalone build error (ISDEV : error -6243: InstallUtilLib.dll cannot be located) on InstallShield Forum. Dec 17, 2013 01:08 AM
- Posted Installshield 2013 license on InstallShield Forum. Jul 11, 2013 01:12 AM
- Posted Re: Writing to MSI log from c# exe on InstallShield Forum. Jul 31, 2012 04:27 AM
- Posted Writing to MSI log from c# exe on InstallShield Forum. Jul 27, 2012 04:21 AM
Contact Me
Online Status |
Offline
|
Date Last Visited |
Dec 06, 2019
11:11 AM
|