Define File Bag, sometimes in upgrade, it does not work

[luapej]

We are using IA15 and are about to upgrade to X3.

In some of our scripts we are using "Define File Bag" and set the runtime location of the files to a default place, I belive. In Program Data and a folder with a GUID.
As our customers upgrade our product, sometimes it will be some errors in these folders. Our support tells us that sometime it works on half of the clients on a customer. Sometimes it's just two of 30 that's not working.
I cannot tell any specifics to why it's working or why it's not.

If you take away all the GUID folders and start the upgrade onec agin, it will work. Now our support have told us that the problem is increasing and wold like to know how to solve it. I have looked around on this forum and could find some posts about this problem, but they seem quite old. Is this solved in X3 or do we need to recreate our script?

[FrancescoT]

Dear luapej,

"File bag" files are available only while setup is running and are not permanently installed on the target system.
These get stored under the local temporary directory and not under "ProgramData".

Anyway, there was significant updates with the "File Bag" plugin and with the installer engine itself.
You may to run a quick test using the latest IA X3 trial.

Upgrading setups created in InstallAware 15 to InstallAware 16 or higher is automatic, unless your setup contains localizations, or it contains hard-coded strings in your MSIcode script that are in a different language from your system locale for non-Unicode programs

That said you should;

- verify that any "garbage" characters is not present with those script commands where is possible to enter literal text. Such "garbage" characters get generated when the UNICODE encoder is not able to recognize the original character as a valid ANSI character. If this is the case, correct the string or the character accordingly.

- Remove any strings resource localization from your project and use the "Localization Wizard" included in IA X3, to replace all them with a new re-generated set of localized string resources. NOTE! If you use a third party translation tool, this must full support UNICODE, otherwise localized resource strings cannot be imported in IA X3.

IMPORTANT NOTE!
Before to proceed with the above steps, make a backup copy of your projects and keep them in a safe location.

Hope this helps you.