Why do I receive the 1627 error?

Usually this problem is caused by a duplicate Control Event on one of the installation dialogs. If you cannot find a duplicate control event please send us the project file to support at advancedinstaller dot com so we can investigate it.

Why do I receive the 2350 error?

This error means "FDI server error" and it shows that there is a problem with Windows Installer. The solution is to upgrade or downgrade Windows Installer on the machine which gives this error.

Why do I receive the 2869 error?

Usually this error is encountered if a property which contains a folder path is used in the Action Data field of a .NET custom action. The problem is caused by the trailing backslash which escapes the quote character which comes after the property. This can be solved by adding a blank space after the property. For example, "[APPDIR]" should be modified to "[APPDIR] ".

Also, instead of a blank space you can add a "\" character after the property. For example: "[APPDIR]\".

Another cause may be an exception in the custom action's code. Therefore, if adding the blank space or a backslash doesn't make a difference, you should investigate the code.

In some cases this error may occur if /ReqVersion option set for a ".NET Installer Class Action" does not match the .NET version installed on the target machine. To fix this, simply make sure the Action Data field of the custom action refers to a .NET version installed on the target machine.

Why do I receive the 4154 warning?

This warning number is accompanied by the Required Application prerequisite was not correctly installed... message. The install conditions for prerequisites are evaluated at two specific moments:

  • At the beginning of the package installation process. If the condition is met then the prerequisite will not be installed as it is already present on the target machine. If the condition is not met the prerequisite will be scheduled for installation.
  • After the installation of prerequisites. Once the prerequisites are installed the associated conditions will be re-evaluated. If the conditions are met then the prerequisites were successfully installed. If the conditions are not met then the installation of the prerequisites failed and the 4154 warning message is displayed.

Usually, this warning appears when the install conditions associated with prerequisites are not valid. In order for a prerequisite to successfully be reported as installed a valid install condition is needed that will not be met if the prerequisite is not installed and will be met if the prerequisite is installed.

Why is one backslash removed from a network location passed to a .NET Custom Action?

This problem appears when passing a parameter that contains a network location to the Action Data field of a .NET Custom Action.

Server = \\MyServer\Location

Unfortunately Windows Installer will remove the first backslash and the resulted value will be:

Server = \MyServer\Location

The solution is to use three backslashes when defining properties that point to network locations:

Server = \\\MyServer\Location

Why do I receive an exception when importing an MSI?

This problem is encountered because some of the tables contained by the MSI have an invalid format. These errors are not fatal, therefore the MSI installation probably works on most computers. However, Advanced Installer verifies these tables and tries to correct them. Sometimes, the errors are too severe and Advanced Installer cannot correct them (you receive an exception message). Note that you can correct the errors with Orca and then try to import the MSI.

Why do I receive the "Another installation is already in progress" message?

Windows Installer allows only one MSI-based installation to run at any given time. Therefore, if you launch another MSI package while an MSI installation is in progress, you will see this message. Note that if your package requires other software to be installed, you can use prerequisites or chained packages.

Why do I receive the "Verify that you have sufficient privileges to start system services" message?

By default, a user cannot start system services (even if he is an Administrator). However, this can be changed through a custom action. You can find more details about this in the Install a service for a custom user How-To.

Why do I receive the "Windows cannot find 'C:\Program'" error?

Paths used in command lines inside the package (for example by a custom action) need to be enclosed by quotes (") in order to be recognized by Windows Installer. To fix this error, make sure that all paths used in command line fields (including references to files or folders) are surrounded by quotes.