AI MSIs fail Orca's Validation Suite, extra unneeded dialogs

[gordonf]

It seems minor, notably if you are not using a certain setup dialog box, but it should be simple enough to look at. For example, a package I put together, which omits the License Agreement, Setup Type and User Registration dialogs causes, Orca to generate the following errors in validation.

While the errors don't stop the resulting package from working, I believe omitting unused dialogs from the resulting package will reduce the package size. This can be important if you're offering the package for download and are trying to save bandwidth.

ICE03 ERROR Not a valid foreign key; Table: Control, Column: Control_Next, Key(s): LicenseAgreementDlg.BannerBitmap
ICE17 ERROR PushButton: 'Back' of Dialog: 'LicenseAgreementDlg' does not have an event defined in the ControlEvent table. It is a 'Do Nothing' button.
ICE17 ERROR PushButton: 'Next' of Dialog: 'LicenseAgreementDlg' does not have an event defined in the ControlEvent table. It is a 'Do Nothing' button.
ICE17 ERROR PushButton: 'Back' of Dialog: 'SetupTypeDlg' does not have an event defined in the ControlEvent table. It is a 'Do Nothing' button.
ICE17 ERROR PushButton: 'TypicalButton' of Dialog: 'SetupTypeDlg' does not have an event defined in the ControlEvent table. It is a 'Do Nothing' button.
ICE17 ERROR PushButton: 'CustomButton' of Dialog: 'SetupTypeDlg' does not have an event defined in the ControlEvent table. It is a 'Do Nothing' button.
ICE17 ERROR PushButton: 'CompleteButton' of Dialog: 'SetupTypeDlg' does not have an event defined in the ControlEvent table. It is a 'Do Nothing' button.
ICE17 ERROR PushButton: 'Back' of Dialog: 'UserRegistrationDlg' does not have an event defined in the ControlEvent table. It is a 'Do Nothing' button.
ICE17 ERROR PushButton: 'Next' of Dialog: 'UserRegistrationDlg' does not have an event defined in the ControlEvent table. It is a 'Do Nothing' button.
ICE23 ERROR Control_Next of control LicenseAgreementDlg.BannerBitmap links to unknown control.
ICE32 ERROR Possible Mis-Aligned Foreign Keys
Feature.1 = s32
Extension.Feature_ = s38

[UdreaMihai]

Hi,

Yes, we are aware of the ICE errors but you can safely ignore them: they are harmless.

What happens is that Advanced Installer does not have yet a way fully define and customize UI. Instead, we built-in all the dialogs into the template MSI and we change their succession and parameters.

That is why the unused dialogs appear as unconnected (or connected to missing components) thus generating validation errors...

As for size, a dialog is in fact a collection of objects that are defined using database entries. These entries are text only, so the space required is very small.

Best,

[Nico-D]

Hello,
It has been a long time this post has been written.

Using latest (7.6) version of Advanced Installers, it seems that the "warnings" are still there, for all builds.

Code: Select all

ERROR ICE27 Unknown action: 'MsiConfigureServices' of InstallExecuteSequence table. Not a standard action and not found in CustomAction or Dialog tables
ERROR ICE32 Possible Mis-Aligned Foreign Keys
AI_SQLConnection.1 = s45
AI_SQLScript.ConnectionName = s100
WARNING ICE45 Row 'VerifyReadyDlg.Install' in table 'Control' has bits set in the 'Attributes' column that are reserved. They should be 0 to ensure compatability with future installer versions.
WARNING ICE45 Row 'VerifyRemoveDlg.Remove' in table 'Control' has bits set in the 'Attributes' column that are reserved. They should be 0 to ensure compatability with future installer versions.
WARNING ICE45 Row 'VerifyRepairDlg.Repair' in table 'Control' has bits set in the 'Attributes' column that are reserved. They should be 0 to ensure compatability with future installer versions.

Are they still minor? Can I still ignore these warnings?

Are you planing to work on this for a future release?
Best regards,
-- Nicolas D.

[GabrielBarbu]

Hi Nicolas,

The ICE 27 error can be safely ignored. It is caused because of the fact MsiConfigureServices is new and Microsoft didn't update ICE 27 to recognize it.

Regarding the rest of the warnings, please send your .aip project file to support at advancedinstaller dot com so we can investigate.

Best regards,
Gabriel

[dms]

Well that answers the Error ICE27 error I get, and I can ignore that, but I too get all three ICE45 Errors listed in the above post, and no matter what I doo to try and remove them it either makes no difference or breaks the installer.

For the time being at least I choose to ignore them, but it would be nice to know what's causing them in the first place.

Dom

[GabrielBarbu]

Hello,

Please send us your project.

Regards,
Gabriel

[GabrielBarbu]

Hello,

I have investigated the project and the validation errors you were encountering did not manifest themselves with the file you sent. However there were other validation errors which can be fixed like this:
- a component must not have both per-user and per-machine data. You are creating both advertised and unadvertised shortcuts for the same file. This is not correct.
- a per-user component must have a registry key as the key path of the component, not a file. Create a registry for your component, place the registry in your component and set it as KeyPath.

Regards,
Gabriel

[Nico-D]

Hi Gabriel,

Thank you very much for your answer. I've just sent a file to support at advanced installer dot com.

I did not send you any of my package as the problem occurs on all of them: I've sent you a newly created Enterprise package, with one file (the AIP file itself) and a blank SQL file with an unconfigured SQL connection.

The same ICE errors occurs.

Best regards,
-- Nicolas D.

[Cosmin]

Hi Nicolas,

We tested the project with Advanced Installer 7.6.1 and only the "MsiConfigureServices" error is shown. This error should be ignored because the action was added in Windows Installer 4.5, but the validation process was not updated by Microsoft.

Can you please try using the latest Advanced Installer version and see if the problem persists?

Regards,
Cosmin

[Nico-D]

Hi Cosmin,

I've just downloaded and installed AI 7.6.1. I've tried two experiments:

1- loading the test.aip I have sent to you
2- crating from scratch another test2.aip following the same steps as I did for test.aip

Both still have the same errors.

Maybe is it OS related? I'm using AI on a Windows Server 2003 R2 EN, with Windows Installers V 4.5.6001.22159. All upgrades from MS have been applied.

Regards,
-- Nicolas D.

[Nico-D]

Sorry, there are no more errors on ICE 32. There still be ICE 27 and ICE 45.
-- Nicolas D.

[Cosmin]

Hi Nicolas,

Can you please try installing Orca.msi from the latest Windows SDK? Perhaps your machine contains older validation information (usually installed by Windows SDK or Visual Studio).

Regards,
Cosmin

[Nico-D]

That seems to be a good idea, thanks Cosmin.

Is it that one you are suggesting?
http://www.microsoft.com/downloads/deta ... laylang=en

Do you have another link more direct to install Orca in the best version?

Regards,
-- Nicolas D.

[Cosmin]

Hi Nicolas,

Yes, this is it. You don't need the documentation or samples, but you should install the debugging tools. After that you can manually install Orca from the "bin" subfolder of the SDK folder.

Regards,
Cosmin

[Nico-D]

Hello Cosmin,

You are right: by installing the latest Microsoft SDK, the latest Orca MSI becomes available (Program Files/Microsoft SDKs/7.0/bin/). And installing this MSI (Orca v5.0) corrects the behaviour I previously described.

There is only ICE Error that is present is:

Code: Select all

ERROR ICE27 Unknown action: 'MsiConfigureServices' of InstallExecuteSequence table. Not a standard action and not found in CustomAction or Dialog tables

But Gabriel previously wrote in this thread that it could be ignored.

Regards,
-- Nicolas D.