Installation Issues

Inno Setup exit codes

  • 0: Setup completed successfully, or the /HELP or /? command line parameter was used.
  • 1: Setup failed to initialise.
  • 2: The user clicked Cancel in the wizard before installation started, or chose "No" on the opening "This will install..." message box.
  • 3: A fatal error occurred while preparing to move to the next installation phase, such as running out of memory or Windows resources.
  • 4: A fatal error occurred during the actual installation process.
  • 5: The user clicked Cancel during installation, or chose Abort at an Abort-Retry-Ignore box.
  • 6: Setup was forcefully terminated by the debugger.
  • 7: The Preparing to Install stage determined that Setup cannot proceed with installation.
  • 8: The Preparing to Install stage determined that Setup cannot proceed with installation, and that the system needs to be restarted to correct the problem.

Before returning exit codes 1, 3, 4, 7 or 8, an error message explaining the problem is normally displayed.

Unable to connect to SQL Server

  • Check that SQL Server is listening on the protocol you have selected. Usually this is TCP/IP for all but local instances.
  • Check that SQL Server is listening on the port you have selected. The default TCP port for SQL Server is 1433. If you use another port, add ,portnumber to the end of the server name.
  • Review the Microsoft article Solving connectivity errors to SQL Server.
  • If possible, check that connectivity to the port is open using telnet (see using telnet).

No internet access

Studio checks for updates at startup and connects to the Aireforge website to activate a licence. Without internet access, the update check is skipped without interrupting startup; a manual update check from the ribbon reports that it could not connect, and licence activation reports the same.

Proxies

Studio picks up proxy credentials from the system at startup. An invalid proxy is reported by the licensing dialog as "Invalid network proxy."