Nov 07, 2017
06:20 PM
Thanks for everything, Dan. I have been working on implementing Custom Action approach but it went no where. Your guidance helped me a lot. I have a full working POC. I'll be testing the upgrade with my actual solution tomorrow. Will update you. And, I would like to bring something else to your notice. It's been more than a week that I've created a post regarding setting Using Installer Class set to true but found no help. I would really appreciate if you could guide me on this too. Below is my original post, Hi, Long story short, I have used InstallShield 2015 Professional to manage my solution's(windows service) installation. Now, I've got a requirement to do some logic before Uninstall. So, I've overridden onBeforeUninstall() event handler of Projectinstaller to do necessary logic for me. I've tested this functionality using InstallUtil uninstall command and everything worked fine. But, when I used my Installshield to uninstall, I'm not even getting control into my onBeforeUnsintall(). After browsing for some time, I came to know that I need to set User Installer Class to true to achieve what I need. But, after changing the value to true, I'm getting Error 1001 right when I'm installing my setup file. I would be really thankful if someone could help me out with this. Thanks. I really need to make InstallShield use InstallUtil.exe to uninstall my service. Could you please help me with this. I can share my logs as well. Looking forward. Thanks. Regards, Koushik Maddali
... View more
Nov 07, 2017
04:38 PM
SOLVED!!! No worries, Dan. I've gone through few posts regarding the same issue. I've created STRING registries instead of DWORD and changed the property values from int to #int. It worked. Thanks.
... View more
Nov 07, 2017
03:25 PM
DLee65 wrote: The registry value is the name of the data you are trying to preserve. Let's say you have a .REG file with the following: [HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\.NETFramework\Performance] "Close"="CloseCtrs" Registry Value should be 'Close' to get the string data type "CloseCtrs". If you leave 'Registry Value' empty, then you will get the default value. My guess is that the default value for TSAgent is empty, that is why your test failed. Look at the registry key for TSAgent, what is the specific Registry Value data you are trying to preserve? That is the value you need for the 'Registry Value' entry in System Search. Got into something weird, Dan. I have a DWORD registry with value 10. My AppSearch resulted this, AppSearch: Property: RECONNECTINTERVAL, Signature: NewSignature112 MSI (c) (44:A0) [13:16:46:003]: Note: 1: 2262 2: Signature 3: -2147287038 MSI (c) (44:A0) [13:16:46:003]: PROPERTY CHANGE: Modifying RECONNECTINTERVAL property. Its current value is '10'. Its new value: '#10'. And when the value of the RECONNECTINTERVAL property is set to the new DWORD registry, it converted as a STRING registry with value #10. Do you know what's going on here?
... View more
Nov 07, 2017
02:30 PM
I've edited my previous reply instead of creating a new one. My bad!! It worked, Dan. When you asked me to check my config, I've tried giving the key name into the registry value field. It worked. Thank you so much man. I really appreciate for helping me out.
... View more
Nov 07, 2017
01:33 PM
Your'e my savior, Dan. The way I have configured my key is indeed the issue here. Registry Root: HKEY_LOCAL_MACHINE Registry Key: SYSTEM\CurrentControlSet\Services\TSAgent\APP_NAME Registry Value: I have changed the above config to Registry Root: HKEY_LOCAL_MACHINE Registry Key: SYSTEM\CurrentControlSet\Services\TSAgent Registry Value: APP_NAME It worked!!! I need to finish testing the entire parent registry on Major upgrade changing the product codes. Hope I don't encounter any other hiccups. Thanks a lot, Dan. I really appreciate you're concern. Regards, Koushik Maddali
... View more
Nov 07, 2017
12:22 PM
Thanks a lot for taking time to help me out Dan. I tried following the instructions provided, but no luck. I understood that there are 2 phases in this. First one is to search for an existing registry and save it's value to a property. Second phase is to use this property value as the default value for the new registry that I have created with the installation. To achieve this, I have created a property "APPNAME" and then created a system search and selected APPNAME as the destination to store the value of the registry. Then, I tried to use [APPNAME] as the default value for my new registry. Is this the right way to load a property value as a default registry value? Below are the msi logs that came out with my try. Please take a look, Mentioning Line numbers to give an idea of the sequence. Line No: 118 Action start 10:10:27: AppSearch. AppSearch: Property: APPNAME, Signature: NewSignature1 MSI (c) (88:F4) [10:10:27:801]: Note: 1: 2262 2: Signature 3: -2147287038 MSI (c) (88:F4) [10:10:27:801]: Note: 1: 1402 2: HKEY_LOCAL_MACHINE32\SYSTEM\CurrentControlSet\Services\TSAgent\APP_NAME 3: 2 Action ended 10:10:27: AppSearch. Return value 1. Line No: 1027 WriteRegistryValues: Key: \SYSTEM\CurrentControlSet\Services\TSAgent, Name: APP_NAME, Value: 0 MSI (s) (64:F4) [10:10:32:942]: Executing op: RegAddValue(Name=CONFIG_SAVED_ON,,) Line No: 1212 Property(S): APPNAME = 0 Line No: 1412 Property(C): APPNAME = 0 Is there any problem with saving registry value to property or is it a sequence issue?
... View more
Nov 07, 2017
08:55 AM
Thanks for the response Dan. I'm new to InstallShield. I'll checkout the App-search. Is there any documentation that could help me with this procedure?
... View more
Nov 06, 2017
05:18 PM
Hi, I'm trying to build a Major Upgrade for my solution. I understand that a Major upgrade means, uninstalling all the components of the previous version and then installing new components. My only aim is to retain the registry values of the previous version. I came to know that there is no direct way of doing this. So, I've tried to implement two custom actions to do the job for me. I have written an executable that writes registry values of the previous version into a file and also reads registry values from the file and load them into registries based on the respective argument. My only problem is the sequence that I have to set to achieve my requirement. When I run a Major upgrade setup file, I want the "writing to a file" custom action to happen even before the uninstallation of the previous version and I want the "loading from file" custom action to happen after new registries are created for the newer version. I'm not able to get this done. I would really appreciate if someone can help me out with this. Thank in advance. Regards, Koushik Maddali
... View more
Labels
- Labels:
-
InstallShield 2015
Nov 01, 2017
03:31 PM
Thanks a lot for responding. This is the Error 1001 portion of the logs that I'm getting while installing with "Using Installer Class" set to true. Could you help me understand the reason for the issue. Thanks. InstallServices: Service: MSI (s) (3C:84) [13:26:08:023]: Executing op: ActionStart(Name=_767BAAE8E80C032CE0926C2D2711391A.commit,,) Action 13:26:08: _767BAAE8E80C032CE0926C2D2711391A.commit. MSI (s) (3C:84) [13:26:08:023]: Executing op: CustomActionSchedule(Action=_767BAAE8E80C032CE0926C2D2711391A.commit,ActionType=3585,Source=BinaryData,Target=ManagedInstall,CustomActionData=/installtype=notransaction /action=commit /LogFile= "C:\Program Files (x86)\Cisco\TSAgentPOC\ServiceCallPOC_x64.exe" "C:\Users\ADMINI~1\AppData\Local\Temp\2\{A3436B1E-573E-4D62-8074-F1264A82BE75}\_isconfig.xml") MSI (s) (3C:84) [13:26:08:023]: Executing op: ActionStart(Name=_767BAAE8E80C032CE0926C2D2711391A.rollback,,) Action 13:26:08: _767BAAE8E80C032CE0926C2D2711391A.rollback. MSI (s) (3C:84) [13:26:08:023]: Executing op: CustomActionSchedule(Action=_767BAAE8E80C032CE0926C2D2711391A.rollback,ActionType=3329,Source=BinaryData,Target=ManagedInstall,CustomActionData=/installtype=notransaction /action=rollback /LogFile= "C:\Program Files (x86)\Cisco\TSAgentPOC\ServiceCallPOC_x64.exe" "C:\Users\ADMINI~1\AppData\Local\Temp\2\{A3436B1E-573E-4D62-8074-F1264A82BE75}\_isconfig.xml") MSI (s) (3C:84) [13:26:08:023]: Executing op: ActionStart(Name=_767BAAE8E80C032CE0926C2D2711391A.install,,) Action 13:26:08: _767BAAE8E80C032CE0926C2D2711391A.install. MSI (s) (3C:84) [13:26:08:023]: Executing op: CustomActionSchedule(Action=_767BAAE8E80C032CE0926C2D2711391A.install,ActionType=3073,Source=BinaryData,Target=ManagedInstall,CustomActionData=/installtype=notransaction /action=install /LogFile= "C:\Program Files (x86)\Cisco\TSAgentPOC\ServiceCallPOC_x64.exe" "C:\Users\ADMINI~1\AppData\Local\Temp\2\{A3436B1E-573E-4D62-8074-F1264A82BE75}\_isconfig.xml") MSI (s) (3C:98) [13:26:08:023]: Invoking remote custom action. DLL: C:\Windows\Installer\MSI3124.tmp, Entrypoint: ManagedInstall MSI (s) (3C:F0) [13:26:08:023]: Generating random cookie. MSI (s) (3C:F0) [13:26:08:023]: Created Custom Action Server with PID 1416 (0x588). MSI (s) (3C:8C) [13:26:08:038]: Running as a service. MSI (s) (3C:8C) [13:26:08:038]: Hello, I'm your 32bit Elevated custom action server. Error 1001. MSI (s) (3C!E4) [13:26:10:070]: MSI (s) (3C:98) [13:26:10:070]: Leaked MSIHANDLE (8) of type 790531 for thread 1508 MSI (s) (3C:98) [13:26:10:070]: Note: 1: 2769 2: _767BAAE8E80C032CE0926C2D2711391A.install 3: 1 Info 2769. Custom Action _767BAAE8E80C032CE0926C2D2711391A.install did not close 1 MSIHANDLEs. CustomAction _767BAAE8E80C032CE0926C2D2711391A.install returned actual error code 1603 (note this may not be 100% accurate if translation happened inside sandbox) Action ended 13:26:10: InstallFinalize. Return value 3. MSI (s) (3C:84) [13:26:10:070]: Note: 1: 2265 2: 3: -2147287035 MSI (s) (3C:84) [13:26:10:070]: User policy value 'DisableRollback' is 0 MSI (s) (3C:84) [13:26:10:070]: Machine policy value 'DisableRollback' is 0 MSI (s) (3C:84) [13:26:10:070]: Executing op: Header(Signature=1397708873,Version=500,Timestamp=1264675652,LangId=1033,Platform=589824,ScriptType=2,ScriptMajorVersion=21,ScriptMinorVersion=4,ScriptAttributes=1) MSI (s) (3C:84) [13:26:10:070]: Executing op: DialogInfo(Type=0,Argument=1033) MSI (s) (3C:84) [13:26:10:070]: Executing op: DialogInfo(Type=1,Argument=PGServicePOC) MSI (s) (3C:84) [13:26:10:070]: Executing op: RollbackInfo(,RollbackAction=Rollback,RollbackDescription=Rolling back action:,RollbackTemplate=[1],CleanupAction=RollbackCleanup,CleanupDescription=Removing backup files,CleanupTemplate=File: [1]) Action 13:26:10: Rollback. Rolling back action: Rollback: _767BAAE8E80C032CE0926C2D2711391A.install MSI (s) (3C:84) [13:26:10:070]: Executing op: ActionStart(Name=_767BAAE8E80C032CE0926C2D2711391A.install,,) MSI (s) (3C:84) [13:26:10:070]: Executing op: ProductInfo(ProductKey={A3436B1E-573E-4D62-8074-F1264A82BE75},ProductName=PGServicePOC,PackageName=PGServicePOC.msi,Language=1033,Version=16777216,Assignment=1,ObsoleteArg=0,ProductIcon=ARPPRODUCTICON.exe,,PackageCode={D43B84BC-1ACB-4146-8B5F-0B3FCCAFC805},,,InstanceType=0,LUASetting=0,RemoteURTInstalls=0,ProductDeploymentFlags=3) Rollback: _767BAAE8E80C032CE0926C2D2711391A.rollback MSI (s) (3C:84) [13:26:10:070]: Executing op: ActionStart(Name=_767BAAE8E80C032CE0926C2D2711391A.rollback,,) MSI (s) (3C:84) [13:26:10:070]: Executing op: CustomActionRollback(Action=_767BAAE8E80C032CE0926C2D2711391A.rollback,ActionType=3329,Source=BinaryData,Target=ManagedInstall,CustomActionData=/installtype=notransaction /action=rollback /LogFile= "C:\Program Files (x86)\Cisco\TSAgentPOC\ServiceCallPOC_x64.exe" "C:\Users\ADMINI~1\AppData\Local\Temp\2\{A3436B1E-573E-4D62-8074-F1264A82BE75}\_isconfig.xml") MSI (s) (3C:20) [13:26:10:070]: Invoking remote custom action. DLL: C:\Windows\Installer\MSI3923.tmp, Entrypoint: ManagedInstall Error 1001. MSI (s) (3C!D4) [13:26:10:726]: MSI (s) (3C:20) [13:26:10:726]: Leaked MSIHANDLE (10) of type 790531 for thread 2516 MSI (s) (3C:20) [13:26:10:726]: Note: 1: 2769 2: _767BAAE8E80C032CE0926C2D2711391A.rollback 3: 1 Info 2769. Custom Action _767BAAE8E80C032CE0926C2D2711391A.rollback did not close 1 MSIHANDLEs. CustomAction _767BAAE8E80C032CE0926C2D2711391A.rollback returned actual error code 1603 but will be translated to success due to continue marking Rollback: _767BAAE8E80C032CE0926C2D2711391A.commit
... View more
Oct 30, 2017
05:19 PM
Hi, Long story short, I have used InstallShield 2015 Professional to manage my solution's(windows service) installation. Now, I've got a requirement to do some logic before Uninstall. So, I've overridden onBeforeUninstall() event handler of Projectinstaller to do necessary logic for me. I've tested this functionality using InstallUtil uninstall command and everything worked fine. But, when I used my Installshield to uninstall, I'm not even getting control into my onBeforeUnsintall(). After browsing for some time, I came to know that I need to set User Installer Class to true to achieve what I need. But, after changing the value to true, I'm getting Error 1001 right when I'm installing my setup file. I would be really thankful if someone could help me out with this. Thanks.
... View more
Labels
- Labels:
-
InstallShield 2015
Latest posts by kmaddal39
Subject | Views | Posted |
---|---|---|
1113 | Nov 07, 2017 06:20 PM | |
1113 | Nov 07, 2017 04:38 PM | |
1991 | Nov 07, 2017 03:25 PM | |
1991 | Nov 07, 2017 02:30 PM | |
1991 | Nov 07, 2017 01:33 PM | |
1991 | Nov 07, 2017 12:22 PM | |
1991 | Nov 07, 2017 08:55 AM | |
2125 | Nov 06, 2017 05:20 PM | |
2896 | Nov 06, 2017 05:18 PM | |
2125 | Nov 01, 2017 03:31 PM |
Activity Feed
- Posted Re: Retaining Registries on Major Upgrade on InstallShield Forum. Nov 07, 2017 06:20 PM
- Posted Re: Retaining Registries on Major Upgrade on InstallShield Forum. Nov 07, 2017 04:38 PM
- Posted Re: Retaining Registries on Major Upgrade on InstallShield Forum. Nov 07, 2017 03:25 PM
- Posted Re: Retaining Registries on Major Upgrade on InstallShield Forum. Nov 07, 2017 02:30 PM
- Posted Re: Retaining Registries on Major Upgrade on InstallShield Forum. Nov 07, 2017 01:33 PM
- Posted Re: Retaining Registries on Major Upgrade on InstallShield Forum. Nov 07, 2017 12:22 PM
- Posted Re: Retaining Registries on Major Upgrade on InstallShield Forum. Nov 07, 2017 08:55 AM
- Posted Re: Using Installer Class not working on InstallShield Forum. Nov 06, 2017 05:20 PM
- Posted Retaining Registries on Major Upgrade on InstallShield Forum. Nov 06, 2017 05:18 PM
- Posted Re: Using Installer Class not working on InstallShield Forum. Nov 01, 2017 03:31 PM
- Posted Using Installer Class not working on InstallShield Forum. Oct 30, 2017 05:19 PM