PDA

View Full Version : Basic MSI Project Wizard errors



Shuttledude
04-12-2006, 04:41 PM
Got these errors when using the Project Wizard to create a BasicMSI project (did not happen for a new InstallScript project):

ListBox: 'IS_SQLSERVER_LIST' for Control: 'lstSQLServer' of Dialog: 'SQLBrowse' not found in ListBox table. Control Property SQLBrowse lstSQLServer ERROR CODE ICE17

ComboBox: 'IS_SQLSERVER_SERVER' for Control: 'cboServers' of Dialog: 'SQLLogin' not found in ComboBox table. Control Property SQLLogin cboServers ERROR ICE17

An MsiPatchCertificate table entry is required for User Account Control (UAC) patching ERROR ISICE09

MichaelU
04-12-2006, 04:46 PM
These are all MSI validation errors. The first two are not something that can be addressed as not populating the ListBox table is the only way to represent the empty list. The last reflects the fact that your install is not signed and also not manually primed with a patch certificate, and is only a problem if you're worried about Vista Logo compliance. The validation can be disabled if it's not relevant for you, via Tools > Options > Validation.

MartinMarkevics
04-14-2006, 10:52 AM
Actually, the first issue (regarding the SQL dialogs) will be addressed (at least partially), but probably not for the 12.0 release. The SQL related dialogs are in the base project template by default. So, whether or not you use the SQL support in the product, the dialogs are always there. Though, they are sequenced and used only when you use the SQL functionality in the product (i.e. you make any changes in the SQL Scripts view). We will change the code to add them to your project dynamically when you add your first SQL setting. So, for those people not using SQL functionality in their setup, they will not get this validation error. If you are, there's really no way to avoid it as Michael mentioned.

In the meantime, if you will not be using the SQL functionality, you can remove the SQLBrowse and SQLLogin dialogs from your project, which will make the fix the ICE error. Admittedly this is not ideal, but we will fix this soon.

In case you need to reference this in the future, the issue # for this is IOC-000045009.