I have a project where in my initial test build, the setup failed before I ever even go to the UI sequence. When I checked the logs, I found this:
MSI (c) (A0:F0) [15:28:59:617]: Connected to service for CA interface. MSI (c) (A0!1C) [15:28:59:883]: Note: 1: 2205 2: 3: ISSQLConnection MSI (c) (A0!1C) [15:28:59:883]: Note: 1: 2228 2: 3: ISSQLConnection 4: Select * FROM `ISSQLConnection` ORDER BY `Order` MSI (c) (A0!1C) [15:28:59:883]: Note: 1: 2205 2: 3: ISSQLConnection MSI (c) (A0!1C) [15:28:59:883]: Note: 1: 2228 2: 3: ISSQLConnection 4: Select * FROM `ISSQLConnection` ORDER BY `Order` Action ended 15:28:59: ISSQLServerInitialize. Return value 3. MSI (c) (A0:8C) [15:28:59:883]: Doing action: SetupCompleteError Action 15:28:59: SetupCompleteError. Action start 15:28:59: SetupCompleteError.
This is essentially a new installer. I captured a package based on a legacy installer, and have made some minor edits, but that's about it. I tried doing a search for information on what ISSQLServerInitialize does, but didn't uncover anything.
The 2205 indicates the listed table (ISSQLConnection) does not exist (look it up with Windows Installer Error Messages, and scan for 2205). It sounds like somehow your project got into a state where it had the SQL support, but no data to work with it. To return to the default state you could try adding and then removing a SQL connection, or backing up your project, going to the custom actions view, and using right click to show all actions so you can delete the SQL related actions.
