About emmanuelc

emmanuelc · ‎Jun 10, 2020

Its a minor upgrade. And yes it adds new components. I have attached the setup log below, it you do a search on INSTALLDIR you will see that it initialises the value MSI (c) (B4:B8) [19:17:46:190]: PROPERTY CHANGE: Adding INSTALLDIR property. Its value is 'C:\Program Files (x86)\Knowledgeone Corporation\RecFind 6\Web Client and Mini-API'. and the shortly later it modifies it MSI (c) (B4:B8) [19:17:46:190]: PROPERTY CHANGE: Modifying INSTALLDIR property. Its current value is 'C:\Program Files (x86)\Knowledgeone Corporation\RecFind 6\Web Client and Mini-API'. Its new value: 'C:\Program Files (x86)\Knowledgeone Corporation\RecFind 6\Web Client and Mini-API\Images\Test'. I do not understand what is making the system modify the value, or how to stop it. I have found that its predictable though, so I have been able to work around it by copying the files back to the right place in script. The project is an old one and has been upgraded through several different versions of IS. When I inherited it, it was missing a number of files that I had to create removefile entries for, and there was a lot of redundant script, so it was a bit of a mess with lots of errors. This is the only thing that I have not been able to fix.

emmanuelc · ‎May 28, 2020

I am using Installshield 2019 and am trying to modify my web app IS project to install a new version. I am finding that a clean install works fine and the files all go where they are supposed to, but if I try to update a previous version then the INSTALLDIR is incorrect and puts some files in an wrong directory. Specifically, it seems to select one of the existing subdirectories as the new INSTALLDIR so the files go there. This appeared to start when I added some components to the install. Removing those components did not fix it, it just chose another wrong folder, a different one this time. I tried to reset the INSTALLDIR with an MsiSetProperty in InstallScript, but it does not seem to take and continues to use the incorrect folder that it selected before. I saw a similar problem where the solution was to add a component that had INSTALLDIR as its target and I have tried that but that also has not worked. Any help much appreciated. Thanks

emmanuelc · ‎Mar 11, 2020

Hi I'm getting the above problem and am having a difficult time tracking it down. The answer written here previously was that it it could be resolved by adding the ProcessComponents action after InstallInitialize action. I checked the Custom actions and saw that it was already set up like this. In fact this was an installshield project that had been used successfully before and no change had been made to the custom actions at all, so it doesnt make sense to me for it to say that something was out of sequence. The main change (that was intended) of was to change one of the dlls and to update the version number. Somehow I assume something else environmental had changed and its causing this error. I tried running the setup with /debuglog but I cant see anything in there. Any help or some suggestion that points me in the right direction would be much appreciated.

emmanuelc · ‎Aug 25, 2019

Looks like it was due to a typo on the product code. Thank you for your assistance .

emmanuelc · ‎Aug 23, 2019

Sorry did not understand your question. I have a setup program from 2 years ago that was built with InstallShield 2014. I no longer have the ISM that built it in its original form; this was before I started at this company. The file I do have looks like it might be the same, but I don't know what might have changed. I am trying to modify the ISM that I do have to create an install for an upgraded version of the software. When I run it, I expect it to create a minor update. Ie. I have a old setup program version 2.9 and a new ism set to version 2.10 I have set the product code and package code and version number in line with what the documentation says it should be. The build gives an error when I try to create a minor upgrade with an error that says it cannot build a minor upgrade, but does not tell me why. The validation tells me it will do a minor upgrade, but it doesn't work. If I create an automatic or major upgrade, then it builds, but creates a new install on the target machine. So its not an upgrade at all, its a new install. I just need this software to create an upgrade of an existing install, or to tell me why it cant. I have attached the new ISM for v2.10 and the old setup for v2.9 to this message. Thanks for your help.

emmanuelc · ‎Aug 21, 2019

Thank you for your reply, I had already seen that page. It tells me to change to a major upgrade. Otherwise;- "If you must use a Minor Upgrade item, you need to compare the latest version of the project to the previous version and ensure all the criteria in the Cause section above are met. Once these criteria are met, a minor upgrade should build correctly with no errors." I have compared all the criteria, and a minor upgrade does not build. Frustratingly, it does not tell me what criteria failed. Is there a way to find that out? Thanks

emmanuelc · ‎Aug 21, 2019

Hello I am trying to create a new setup program that does a minor upgrade of a previous setup. This is failing on the build with the following error: ISDEV : error -6423: The project contains a Minor Upgrade item that references the setup C:\Users\devadmin\AppData\Local\Temp\8985\RecFind 6 SDK.msi. However, the referenced setup can only be upgraded with a Major upgrade. Please use the Major Upgrade item or the automatic upgrade item. So its telling me that it cant do a minor upgrade; the documentation says that the prerequisites for a minor upgrade are that the the Package Code is updated, that the version number should be incremented, and that the Product Code should be the same. I have done all of those things and it hasn't helped. Also I have tried validating the setup.exe that I am trying to upgrade from in the Upgrade page. It gives me this result: Val0003 This setup will perform a SMALL upgrade of the referenced previous setup c:\users\devadmin\appdata\local\temp\2245\recfind 6 sdk.msi Val0003 The package code for the latest setup does not differ from that of the previous version. In order to perform an upgrade the package code MUST change. c:\users\devadmin\appdata\local\temp\2245\recfind 6 sdk.msi Validation Complete! 1. it tells me that it will do a small upgrade which does not actually happen, 2. it says the package code needs updating which I have done; Note that I was originally having this problem in installshield 2015, and tried again using 2019, but got the same error.

emmanuelc · ‎Jul 08, 2019

Running under Winders Server 2016.

emmanuelc · ‎Jul 07, 2019

My problem is not about SQL Server, its about TLS1.2 I have a custom DLL that communicates with a process on the server via TCP. Its referenced in the script like this: function number CheckServerExistsApp(hMSI) OBJECT oObj; STRING sDLL, sRet, szServername; STRING svSupportDir[MAX_PATH]; begin try svSupportDir = MyGetProperty(hMSI, "SUPPORTDIR"); sDLL = svSupportDir ^ "InstallShieldFunctions.dll"; UseDLL( sDLL ); set oObj = CoCreateObjectDotNet(sDLL, "InstallShieldFunctions.InstallShieldFunctions"); szServername = MyGetProperty(hMSI, "SERVERNAME"); sRet = oObj.CheckServer(szServername); MsiSetProperty(hMSI, "SERVEREXISTS", sRet); //MessageBox( "Return = " ^ sRet, MB_OK ); catch MessageBox( "Caught Error = " ^ Err.Description, INFORMATION); endcatch; return 0; end; This code works fine with TLS1.0 but fails with 1.2. Similarly a test program that I use with that same DLL works with TLS1.0 and 1.2. So it looks like IS 2019 is not TLS1.2 compliant, is that correct?

emmanuelc · ‎Jul 04, 2019

Hello was there any update to this issue? I am having a similar problem.

emmanuelc · ‎Jun 30, 2019

Further info, attempting to a verify (right click on an entry in the upgrades section) one of the previous versions causes Installshield IDE to crash. This happens for all of the previous versions except the very oldest.

emmanuelc · ‎Jun 30, 2019

Hi thanks for your reply. - I have a number of previous versions that are referenced as minor upgrades. If I remove all of these then the build completes. Including any of them causes the same error. - Marking the install as a major upgrade of any previous version also works - Building in the IDE generates the same error. I have attached a screen shot. There is not much info here, any advice? Thx

emmanuelc · ‎Jun 28, 2019

Received this error when running installshield 2019 via the command line. The .ism file had been one used in IS 2014 and worked correctly. Can you assist please? Log file attached

Online Status	Offline
Date Last Visited	‎Jul 07, 2020 09:51 PM

Re: INSTALLDIR Points to the wrong directory on package update

INSTALLDIR Points to the wrong directory on package update

Error 2902. Operation ixfAssemblyCopy called out of sequence. ProcessComponent looks fine.

Re: Setup will not create minor upgrade

Re: Setup will not create minor upgrade

Re: Setup will not create minor upgrade

Setup will not create minor upgrade

Re: Installshield database wizard is not allowing to next screen in case TLS 1.2 enable

Re: Installshield database wizard is not allowing to next screen in case TLS 1.2 enable

Re: Installshield database wizard is not allowing to next screen in case TLS 1.2 enable

Re: ISDEV : fatal error -6418: An unexpected error occurred while processing items to be upgraded

Re: ISDEV : fatal error -6418: An unexpected error occurred while processing items to be upgraded

ISDEV : fatal error -6418: An unexpected error occurred while processing items to be upgraded

Re: INSTALLDIR Points to the wrong directory on package update

INSTALLDIR Points to the wrong directory on package update

Error 2902. Operation ixfAssemblyCopy called out of sequence. ProcessComponent looks fine.

Re: Setup will not create minor upgrade

Re: Setup will not create minor upgrade

Re: Setup will not create minor upgrade

Setup will not create minor upgrade

Re: Installshield database wizard is not allowing to next screen in case TLS 1.2 enable

Re: Installshield database wizard is not allowing to next screen in case TLS 1.2 enable

Re: Installshield database wizard is not allowing to next screen in case TLS 1.2 enable

Suggested Actions

Suggest an improvement

Open a support case