For error 7354 follow the KB article links and resolutions provided, https://community.flexera.com/t5/InstallShield-Knowledge-Base/Error-7354-When-Building-MSI/ta-p/4025   https://community.flexera.com/t5/InstallShield-Knowledge-Base/Build-Error-7354-When-Building-a-Project-with-More-Than-8/ta-p/180877   You can find string editor under User Interface , refer attachement. ... View more

If you haven't already gotten your hands on at least version 23.0.0.290 of ISWIBuild.dll (download), give that a try (back up and then replace the ISWIBuild.dll in your InstallShield System folder with this one). It fixes some potential errors, and clears up some remaining confusion in the error messages when there is more than one localizable string column in a table. In this case, both Name and Value of ISXmlElementAttrib are localizable, so this is likely to be relevant. Looking at the categories for the fields in the ISXml* tables, however, I don't see any string validation issues that I would expect to arise. So until we're certain exactly what string is causing problems, I'm going to have to fall back to some general guidance here. The quoted value you show looks fine: it has a few property references, but both UG_WEBAPI_PROTOCOL and UG_WEBAPI_FQDN look perfectly valid. In the screenshot I see reference to a string include add[ ] where that stuff is not a valid property reference. If somehow this is being validated as Formatted text, the square brackets that are around things other than property references would need to be escaped - that is, replaced with [\[] and [\]] respectively. Keep this in mind as a possibility; hopefully the updated ISWIBuild.dll will make more sense of things. ... View more

For example, the FileName column of the RemoveFile table requires a FileName data type. This data type will need a short file name. Adding a short file name will fix the issue. ... View more

Thank you very much for your reply. This simplifies the analysis of the log files in our sandbox. The tool that a was referring to is the one from InstallShield (MSILogAnalyzer.exe) which is located in C:\Program Files\InstallShield\2011\System\ Sadly it does not run in silent mode (with command line) and is also not included with the StandAlone Build. It would be nice if Flexera would support that because it generates multiple configurable professional reports that the WILogUtil does not provide. ... View more

Are you trying to create a minor upgrade? If so, see the following help topic: Configuring Minor Upgrades to Remove Installed Data ... View more

I have solved it. You can use the well-known security identifiers. The SID for the NetworkService user is: S-1-5-20 see http://support.microsoft.com/kb/243330 NasB ... View more

Hello, Thank you for you answer. The files in components are .NET assemblies and all components are set by default to "Dependencies and Properties" I have modified them to "properties Only" as you suggested. This solves my issue (Thanks a lot) I just don't understand why InstallShield decides to add identical .net assemblies from other features/location. Note that that building a release with the IS IDE produces another output than building a release with the IS Standalone Build. Anyway, thanks a lot for your support. NasB ... View more

I experienced some behavior today that brought me to this thread. I think there is still a bug here. In my case I wanted to do a change operation and I have a UI that prompts for username and password. I would think I should be able to do that. But it seems ISIISCosting is only scheduled for the execute and not the UI sequence so nothing pulls the data back. Also if I enter new data in the UI when ISIISCosting executes in the execute sequence it doesn't respect this new information rather it just blasts it with the data that was persisted. I would say that it should only set the property if the property is null. Otherwise it should be assumed that the property is updated correct information and should be used to reconfigure and recache the persisted data. ... View more