Two Include Scripts have overlapping command GUIDs -

[jsmith]

What happens if two scripts included by the main MSIcode have the same GUIDs for their commands in the .mia files? Will this cause problems? I ask because I have found that if I include setupmsi31 and setupmsi45 (both were generated by InstallAware) in the same project, setupmsi45 does not work. It exits as soon as it reaches the first line of the setupmsi45 script.

If I comment out the line that includes setupmsi31, then setupmsi45 works just fine. I opened both scripts' .mia files in a text editor and have found that there are GUIDs in setupmsi31 that also appear in setupmsi45. Would this cause the faulty behavior I am seeing?

I am going to try removing setupmsi31 from my project, creating a new script and re-adding all the code manually to see if it generates non-conflicting GUIDs and, if so, if this makes the problem go away.

Thanks!

[jsmith]

OK, I deleted every line of code from setupmsi31, saved the script, then manually re-added each line, one by one, by dragging the code elements from the "Drag-Drop or Type MSIcode:" window into the MSIcode window for setupmsi31. After doing this, I compared the updated setupmsi31.mia with setupmsi45.mia in a text editor and found that they no longer have overlapping GUIDs. Furthermore, after making this change, setupmsi45 no longer fails just because setupmsi31 is also included from the main script.

So... it seems that the setupmsi31.mia and setupmsi45.mia that get added to your project when you add their respective runtimes are imcompatible.

[mills]

I couldn't reproduce this. I created a basic setup and added only the runtimes for MSI 3.1 and 4.5. I made no changes to the scripts.

Running the installer on Windows XP SP 2, the following happened:

- MSI 3.1 was installed. Asked to reboot.
- After reboot, MSI 4.5 was installed. Reboot again.

Just to make sure that 4.5 was installed:

Start->Run-> msiexec
Output:

Windows ® Installer. V 4.5.6001.22159

What GUID did you find to match?

What OS did you test this on?

[jsmith]

I have uploaded the setupmsi31.mia and setupmsi45.mia scripts. I added a .txt extension to them because this forum doesn't allow .mia attachments. These are the files that were added to our source repository after InstallAware placed them in our project based on our choosing to include their respective runtimes.

setupmsi31 was added on 11/13/2008. setupmsi45 was added on 4/29/2009. Whatever version of IA was the latest is likely what version of IA we were running at these times.

Four of the first five guids listed in setupmsi31.mia also appear in setupmsi45.mia. I stopped searching after that. These ones all appear in each file:

Code: Select all

{E62C0C0A-CBC6-4DBD-9C96-57007EDB32C4}
{83E641E4-0F03-4275-AC0B-E9F0BEF07111}
{044CA851-9CBC-4BE9-BFA2-B9345FF7A5D3}
{5246E0BD-7CCA-4580-9717-217AB57C642F}

They appear in the same order in each script, suggesting that maybe setupmsi45 began life as an exact copy of setupmsi31 and had some of its guts changed, while the skeleton logic directive lines remained the same.

[mills]

I think I'm going to encourage you to upgrade to the latest version of IA. It really looks like you're running into issues you shouldn't on the latest version.

I'm including the scripts that were shipped with SP3 for you to try, though. They don't seem to have matching GUIDs or the problem you report.

[jsmith]

Thanks Andy. It sounds like the overlapping GUIDs issue has been corrected sometime between when we first added these runtimes to our projects when we were running IA 8 and/or IA 9R1 and now. We're actually running IA 9.08. Even if that's not the latest, upgrading won't replace the scripts already checked into our source repository; it would merely make it so if we started new projects and included these runtimes, the scripts would not have this issue, correct?

[jsmith]

[quote="mills"]I think I'm going to encourage you to upgrade to the latest version of IA. It really looks like you're running into issues you shouldn't on the latest version./quote]

So I just discovered that even though I'd installed IA 9.08 that we downloaded over this summer, my splash screen said I was running sp1.070409. I believe this is because we did not generate a new license file after downloading the new version. How exactly does licensing work? I downloaded a new 9.08 installer, installed it, then ran the old license installer. I'd think if the license isn't valid for this version, it should say so. Instead, it succeeds without any errors or warnings and silently sets the version listed in the splash screen as being the older version. Is the version of the code we actually run dependent upon the version of the license we installed?

[mills]

The process you should take for upgrading is as follows:

Download and install the latest "trial" installer.
Regenerate, download and install the license.

If successful, you're version will match this:

version.jpg (82.06 KiB) Viewed 10446 times