7 replies to this topic

[aakash.tiwari12@gmail.com]

Hi ,

 

we are using installshield Developer 7. Our project is standard project.

The requirement is how to design major or minor upadate design for our project.

I dont know how to start and from where to start ,means any step by step procedure for designing major or minor upgrade.

What is REINSTALL property?

 

Please any provide me information regarding this as soon as possible.

 

 

Thanks in advance.

 

 

Aakash

[Glytzhkof]

There is no way to answer such a general question. What we can do is to point you in the direction of information you need:

 

I would start here: https://www.youtube....stallshieldield

 

And the Installshield documentation itself is actually very good. It is also available inside the Installshield tool.

 

Forget all complex stuff, and do the basics first if you go "hands on" tinkering without reading or watching anything:

• Add files
• Add registry settings
• Set up a major upgrade (later versions of Installshield have better upgrade documentation and features. Version 7 was quite complicated to work out)
• Run test installations

You then take things from there. Add COM, install to GAC, etc... We have no idea from your question what the application is really like, and can only provide generic advice.

 

If you are a developer just getting into setups I would recommend going for WIX instead of Installshield. In that case try this tutorial out: http://wix.tramontana.co.hu/tutorial

Edited by Glytzhkof, 02 April 2014 - 13:46.

[aakash.tiwari12@gmail.com]

Hi ,

 

i created the minor upgrade for isntall script MSI

But whenever i am installing this upgraded setup i am getting this error

 

Another version of this product is already installed.............

 

Even though i am changing package code every time. i am not at all changing upgrade and product code.

i have incremented version also 1.3 to 1.4

 

REINSTALLMODE=vomus, REINSTALL=ALL  this is added in Onbegin()

 

 

 

 

Thanks

Edited by aakash.tiwari12@gmail.com, 04 April 2014 - 13:50.

[Glytzhkof]

I forgot to mention that Installscript MSI is not recommended. Basic MSI is a better project type - much less buggy. I would convert your existing project into a Basic MSI project. I am not sure if Installshield has a conversion feature in newer versions of their product, but in older versions I used to export each setup component by right clicking it and selecting "Export into..." or something like that and select a new setup file to export to.

 

Once you have a Basic MSI project, you should be able to define a proper update in the Updates / Upgrades view of Installshield.

[aakash.tiwari12@gmail.com]

Hi Glytzhkof,

 

Please find my log file for this.

 

 === Verbose logging started: 4/8/2014  18:34:47  Build type: SHIP UNICODE 5.00.7601.00  Calling process: C:\PROGRA~1\COMMON~1\INSTAL~1\Driver\7\INTEL3~1\IDriver.exe ===

MSI © (C4:A8) [18:34:47:223]: SOFTWARE RESTRICTION POLICY: Verifying package --> 'C:\Users\taakash\AppData\Local\Temp\_is9C0\FTP Server.msi' against software restriction policy

MSI © (C4:A8) [18:34:47:223]: Note: 1: 2262 2: DigitalSignature 3: -2147287038 

MSI © (C4:A8) [18:34:47:223]: SOFTWARE RESTRICTION POLICY: C:\Users\taakash\AppData\Local\Temp\_is9C0\FTP Server.msi is not digitally signed

MSI © (C4:A8) [18:34:47:231]: SOFTWARE RESTRICTION POLICY: C:\Users\taakash\AppData\Local\Temp\_is9C0\FTP Server.msi is permitted to run at the 'unrestricted' authorization level.

MSI © (C4:A8) [18:34:47:233]: Cloaking enabled.

MSI © (C4:A8) [18:34:47:233]: Attempting to enable all disabled privileges before calling Install on Server

MSI © (C4:A8) [18:34:47:236]: End dialog not enabled

MSI © (C4:A8) [18:34:47:236]: Original package ==> C:\Users\taakash\AppData\Local\Temp\_is9C0\FTP Server.msi

MSI © (C4:A8) [18:34:47:236]: Package we're running from ==> C:\Users\taakash\AppData\Local\Temp\_is9C0\FTP Server.msi

MSI © (C4:A8) [18:34:47:238]: Machine policy value 'DisableUserInstalls' is 0

MSI © (C4:A8) [18:34:47:238]: APPCOMPAT: Uninstall Flags override found.

MSI © (C4:A8) [18:34:47:238]: APPCOMPAT: Uninstall VersionNT override found.

MSI © (C4:A8) [18:34:47:238]: APPCOMPAT: Uninstall ServicePackLevel override found.

MSI © (C4:A8) [18:34:47:238]: APPCOMPAT: looking for appcompat database entry with ProductCode '{619E3260-203D-4858-9968-555C64E65377}'.

MSI © (C4:A8) [18:34:47:239]: APPCOMPAT: no matching ProductCode found in database.

MSI © (C4:A8) [18:34:47:250]: MSCOREE not loaded loading copy from system32

MSI © (C4:A8) [18:34:47:256]: Note: 1: 2262 2: MsiFileHash 3: -2147287038 

MSI © (C4:A8) [18:34:47:256]: Machine policy value 'DisablePatch' is 0

MSI © (C4:A8) [18:34:47:256]: Machine policy value 'AllowLockdownPatch' is 0

MSI © (C4:A8) [18:34:47:256]: Machine policy value 'DisableLUAPatching' is 0

MSI © (C4:A8) [18:34:47:256]: Machine policy value 'DisableFlyWeightPatching' is 0

MSI © (C4:A8) [18:34:47:256]: Enabling baseline caching for this transaction since all active patches are MSI 3.0 style MSPs or at least one MSI 3.0 minor update patch is active

MSI © (C4:A8) [18:34:47:257]: APPCOMPAT: looking for appcompat database entry with ProductCode '{619E3260-203D-4858-9968-555C64E65377}'.

MSI © (C4:A8) [18:34:47:257]: APPCOMPAT: no matching ProductCode found in database.

MSI © (C4:A8) [18:34:47:257]: Transforms are not secure.

MSI © (C4:A8) [18:34:47:257]: Note: 1: 2262 2: Control 3: -2147287038 

MSI © (C4:A8) [18:34:47:257]: PROPERTY CHANGE: Adding MsiLogFileLocation property. Its value is 'C:\Users\taakash\AppData\Local\Temp\MSI31d2f.LOG'.

MSI © (C4:A8) [18:34:47:257]: No Command Line.

MSI © (C4:A8) [18:34:47:257]: PROPERTY CHANGE: Adding PackageCode property. Its value is '{91ED91CD-C57F-471F-9798-54605ED68CA4}'.

MSI © (C4:A8) [18:34:47:257]: Product Code passed to Engine.Initialize:           '(none)'

MSI © (C4:A8) [18:34:47:257]: Product Code from property table before transforms: '{619E3260-203D-4858-9968-555C64E65377}'

MSI © (C4:A8) [18:34:47:257]: Product Code from property table after transforms:  '{619E3260-203D-4858-9968-555C64E65377}'

MSI © (C4:A8) [18:34:47:257]: Product registered: entering maintenance mode

MSI © (C4:A8) [18:34:47:257]: Determined that existing product (either this product or the product being upgraded with a patch) is installed per-machine.

MSI © (C4:A8) [18:34:47:257]: PROPERTY CHANGE: Adding ALLUSERS property. Its value is '1'.

MSI © (C4:A8) [18:34:47:257]: PROPERTY CHANGE: Adding ProductState property. Its value is '5'.

MSI © (C4:A8) [18:34:47:257]: PROPERTY CHANGE: Adding ProductToBeRegistered property. Its value is '1'.

MSI © (C4:A8) [18:34:47:257]: Entering CMsiConfigurationManager::SetLastUsedSource.

MSI © (C4:A8) [18:34:47:257]: Specifed source is not already in a list.

MSI © (C4:A8) [18:34:47:257]: User policy value 'SearchOrder' is 'nmu'

MSI © (C4:A8) [18:34:47:257]: Machine policy value 'DisableBrowse' is 0

MSI © (C4:A8) [18:34:47:257]: Machine policy value 'AllowLockdownBrowse' is 1

MSI © (C4:A8) [18:34:47:257]: Adding new sources is allowed.

MSI © (C4:A8) [18:34:47:257]: PROPERTY CHANGE: Adding PackagecodeChanging property. Its value is '1'.

Another version of this product is already installed. Installation of this version cannot continue. To configure or remove the existing version of this product, use Add/Remove Programs on the Control Panel.

{619E3260-203D-4858-9968-555C64E65377}

MSI © (C4:A8) [18:34:47:302]: Note: 1: 1729 

MSI © (C4:A8) [18:34:47:302]: Product: FTP Server -- Configuration failed.

 

MSI © (C4:A8) [18:34:47:304]: Windows Installer reconfigured the product. Product Name: FTP Server. Product Version: 1.2. Product Language: 1033. Manufacturer: XYZ Reconfiguration success or error status: 1638.

 

=== Verbose logging stopped: 4/8/2014  18:34:47 ===

 

 

 

Thanks and Regards,

Aakash

Edited by aakash.tiwari12@gmail.com, 08 April 2014 - 14:11.

[Glytzhkof]

You may need to read this thoroughly: http://www.msigeek.c...g-installshield

 

I would strongly recommend that you convert to a Basic MSI project. This Installscript MSI project type is buggy, and should not be used unless you have strong reasons to do so. The only reason in my opinion is to show advanced dialogs to the user, and even then I would code this in a dll rather than resorting to the Installscript project type. It is that buggy.

 

Also: the command line REINSTALLMODE=vomus, REINSTALL=ALL should not be added to the package, but specified on the command line when running msiexec.exe.

[aakash.tiwari12@gmail.com]

Hi Glytzhkof

 

Actually we dont have much time for converting the project to basic msi.

 

i have changed the setup.ini also,but this is not giving any effect on this behaviour and my installshield version is 7.02.

Project type is standard (compressed). i have found that it is bug in installshield dev 7.02.

 

 

thanks and regards,

Aakash

[Glytzhkof]

As I recall there is a massive bug in version 7 of Installshield Developer that causes all upgrade scenarios using major upgrades for Installscript MSI projects to fail. You really need to check this, since it will most definitely be a problem for you unless the product will never be upgraded.