About farukhsharipov

farukhsharipov · ‎May 19, 2016

I ran Build -> Validate -> Upgrade Validation Wizard... I selected 2.3 version to compare with current 2.6 version Result is empty and seems like everything is ok.

farukhsharipov · ‎May 19, 2016

Hi All We have Basic MSI project that was working fine files would get replaced if we go from version 2.1 to 2.2 ........ 2.5 Now for the 2.6 version something changed that files are not being updated when we going from 2.1 to 2.6. We still see prompt stating that "This setup will perform an upgrade of 'Application Name". Do you want to continue?" When checking files they still are from 2.1 version, but if we look at the "Programs and Features" is showing 2.6 version. Looking at the log for one of the files showing following For 2.1 to 2.6 [CODE]MSI (s) (68:5C) [15:35:21:095]: Component: CompanyName.Product.Core.dll; Installed: Local; Request: Null; Action: Null[/CODE] While for 2.1 to 2.2 [CODE] MSI (s) (68:A8) [15:26:29:667]: Component: CompanyName.Product.Core.dll; Installed: Local; Request: Local; Action: Local[/CODE] Our upgrade settings are set to default. Which only has ISPreventDowngrade. All the changes are minor, we didn't removed or renamed any components. Question: What could cause not to update files? Installer Log: Thank you.

farukhsharipov · ‎Nov 06, 2015

Hi All I have Basic MSI which installs Windows Service. I followed this thread to set it as "Delayed Start": How can I install a service with the start type of "Delayed Start" It works on Windows 7 (my machine) and Windows 2012 but it's not working on Windows 2008 SP2 Did anyone else come across this issue before? Any insight what could be the issue would be appreciated. I am attaching install log below.

farukhsharipov · ‎Aug 13, 2015

Not sure what was the issue, but I changed Component Code that was tide to registry creation and it solved the problem. Steps: Go to Organization -> Setup Design -> (locate component that is associated with registry creation look in System Configuration -> Registry) -> Change Component Code

farukhsharipov · ‎Aug 12, 2015

Hi all I have Basic MSI Project where I used Registry view in InstallShield (System Configuration -> Registry) to create key with values. Now I am facing an issue that registry key is not deleted during uninstall on some machines. It works fine on my machine and one other test VM we have, but it doesn't delete on several other VM's we have. I am not sure why this is happening. I already spend two days trying to find what I am doing wrong, I tried setting registry flag to Automatic or Install if absent, Uninstall if present (*) nothing works. I also tried to create separate Basic MSI test with similar registry entry and it works on the VM that my installer doesn't work. If anybody here had similar situation, I would appreciate the help.

farukhsharipov · ‎Jul 28, 2015

What is specified environment variable for machine ip address. I can get computer name doing this [%COMPUTERNAME], Are there same thing for ip address? Side note: where I can find list of available environment variables.

farukhsharipov · ‎Jul 27, 2015

How can I do something like this: And then run InstallerB like this: [HTML] setup.exe/s /V"/qb /l*v \"%SystemDrive%\DEFInstall.log\" ADDLOCAL=\"ALL\" INSTALLDIR=\"C:\Program Files\MyCompanyName\DEF\" PREREQCMDLINE=\"/s /V /qb /l*v \"%SystemDrive%\ABCInstall.log\" ADDLOCAL=\"ALL\" INSTALLDIR=\"C:\Program Files\MyCompanyName\ABC\"\" [/HTML] Right now I am getting this error: As you can see I created public property and I would like to set it's value from cmd.exe and pass it to prerequisite.

farukhsharipov · ‎Jul 27, 2015

Hi All I have two Basic MSI projects (installerA and InstallerB) one of them (installerA) is set as prerequisite of second (installerB). Now I need to run installerB using /qb - Basic UI with no modal dialog box displayed at the end of the installation. My command line looks as following: [HTML] InstallerA.exe/s /V"/qb /l*v \"%SystemDrive%\Install.log\" ADDLOCAL=\"ALL\" INSTALLDIR=\"C:\Program Files\MyCompanyName\InstallerB\" IS_SQLSERVER_SERVER=\"(local)\" [/HTML] This runs fine but if installerA hasn't been installed it invokes installerA with Full UI and waits for user interaction. I found that you can set command line for the prerequisite application. Since you can set public properties for Basic MSI from cmd line (as shown above) I was wondering if I can set that command line property. My question is how can I set that prerequisite command line from cmd line, similar to what is shown above for IS_SQLSERVER_SERVER property.

farukhsharipov · ‎Jul 27, 2015

I changed registry location from Default to 64-bit (my Basic MSI is x64 bit) this seems to solve the issue. Thank you.

farukhsharipov · ‎Jul 27, 2015

Hello I have two Basic MSI projects, (installerA and installerB) one of them (installerA) set as prerequisite of the second (installerB). I am trying to run installerA if it hasn't been installed or older version exist. Below are my prerequisite settings. Conditions Type of condition: A registry entry has a specified version value Specify the registry key name to check: HKEY_LOCAL_MACHINE\SOFTWARE\MyCompany\InstallerCache\{GUID} Specify the registry value name to check: ProductVersion Specify the registry value data to check: 1.5.0 Run this prerequisite if: Data on target system is less than specified data Registry Location: Default Behavior The prerequisite requires administrative privileges: Check If, after installing the prerequisite, the conditions still indicate it is required Abort the setup installerA installs fine for me but after clicking finish in installerA and returning to prerequisite screen I get error I think because it checks prerequisite again after installing installerA as described in settings above, but I am not sure why it fails I can see that that registry entry is created with value 1.5.0 What condition should I use if I would like to invoke prerequisite if it doesn't exist or older version is installed? Thank you for your time reading this.

farukhsharipov · ‎Jun 22, 2015

DLee65 wrote: I am sorry, I mistyped. You need to configure the upgrade table. You will want to get familiar with this table and the values you need to know. The help file has a section regarding the upgrade table, just open help, type in 'Upgrade Table' in the Index. This will give an explanation of the columns, their data types, etc. Below is an example of what I use to upgrade a previous version that was created by someone else: UpgradeCode MinVer MaxVer Attributes ActionProperty ISDisplayName {10817CA8-89D1-11D6-B3F4-00034721ED1B} 1.0.1 ***ALL_VERSIONS*** 772 UPGRADE_EARLY_AC_APP1 NewUpgradeEntry1 You will need to get the upgrade code from your previous MSI installer. You will also want to figure out what the absolute minimum version you want to support for upgrade. IF the upgrade code is the same between yours and the previous version, then you can simply insert {00000000-0000-0000-0000-000000000000} and at compile time the current UPGRADECODE will be inserted. InstallShield also has a UI section for creating a new upgrade event. In the view list, scroll down to 'Media' and click on 'Upgrades'. You want to author a new major upgrade for each previous UpgradeCode. In most cases you can simply specify 'Any earlier version' for the Product Version. Read up on the advanced settings. You may want to migrate feature states, OR ignore them entirely; especially if you have restructured the features within your new install. Hopefully this helps. Hi again, I followed your advice, but it doesn't seem to do anything. Below is my Upgrade Table: I made sure that my upgrade code is correct. Any ideas why? Thank you for your help. //---Update---// I didn't had any components in my example so it wasn't working. I added component and followed your advice and it seems to work. Thank you very much.

farukhsharipov · ‎Jun 22, 2015

DLee65 wrote: Why are you not just simply authoring the uninstall table to remove the previous version? Essentially that is the purpose for this table. It can even have a different upgrade code and specify version ranges. One problem that might occur using your approach is that only one MSI installer can run at a time. If you are sequencing this in the EXECUTE sequence, then it should error out. Thank you for response, can you point me where I can find how to use "uninstall table to remove the previous version"?

farukhsharipov · ‎Jun 22, 2015

Hi All I have Basic MSI Project where I am trying to uninstall previous version of the product that was created by different developed. I was thinking using msiexec since it seems to work fine from command line. I created InstallScript function and set it to: Synchronous (Check exit code) Immediate Execution Always execute After File Cost [HTML] function UninstallSilently(hMSI) NUMBER nResult; begin if(LaunchAppAndWait("msiexec", "/uninstall {XXXXXXXX-XXXX-XXXX-XXXX-XXXXXXXXXXXX} /passive", WAIT | LAAW_OPTION_WAIT_INCL_CHILD) < 0)then MessageBox ("Failed to uninstall",SEVERE); endif; end; [/HTML] I can see that it starts uninstalling previous product, but it exits before it's done uninstalling. So my question is how to make sure that LaunchAppAndWait will wait for product uninstall and then continue? Or if you have better way to uninstall previous product I will be happy to hear it. Thank you in advance.

farukhsharipov · ‎Jun 16, 2015

Thank you for explanation. Added component, working now.

farukhsharipov · ‎Jun 16, 2015

What components, have you tried steps that I listed to reproduce the issue?

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

Upgrade Validation Results

Files not updated during upgrade

service with the start type of "Delayed Start" is not working

Re: Basic MSI registry key is not deleted on uninstall

Basic MSI registry key is not deleted on uninstall

specified environment variable for ip address

Re: How to pass command line parameter for prerequisite

How to pass command line parameter for prerequisite

Re: Prerequisite condition

Prerequisite condition

Re: LaunchAppAndWait with msiexec doesn't wait