Software Deployment

Repeat the install but this time with a verbose log. Then check the entries in that log that detail the features, their installed state, their requested state and the action that will take place. For example:

.........MSI (s) <process info>: Feature: LanguageTools; Installed: Absent; Request: Local; Action: Local

shows that the feature 'LanguageTools' isn't currently installed, was requested to be installed to run locally and will be so installed. I expect the log for your install would look like this:

.........MSI (s) <process info>: Feature: LanguageTools; Installed: Absent; Request: Local; Action: Null

or

.........MSI (s) <process info>: Feature: LanguageTools; Installed: Absent; Request: Null; Action: Null

The first means it was requested to be installed but some condition or other overrode that request, and the second means that it wasn't requested to be installed.

I've just been fighting with the joke which is the BusinessObjects 6.5.1 MSI, where a set of Custom Actions featured only in the UI sequence. That meant that a normal, attended install worked fine but silent installs installed only a tiny proportion of the features. Moving those CAs to the Execute sequence (as well as some other work - see my entry in the relevant 'Package KB' post for details) fixed it. I suspect something similar is happening in your case.

Thanks VBScab...

I've found this: http://helpnet.acresso.com/robo/projects/adminstudio75/ISRTaskConvertISMSI.htm

Do you think its worth doing the conversion?

ORIGINAL: wynnem
Do you think its worth doing the conversion? I couldn't say. I guess it depends if the MSI is indeed InstallScript-driven. Just because it's launched by a stub doesn't necessarily mean that it's an InstallScript MSI. If you have the time, there can't be much harm in trying it out. Make sure you have a back-up of the MSI.

Please go through this link http://www.symantec.com/business/support/index?page=content&id=HOWTO4204

Even this is also useful...http://www.symantec.com/connect/blogs/how-solve-error-msi-can-be-installed-through-setupexe-only

Hi,

Try Creating an iss file and execute the setup.exe with iss file .

Cheers .

sometimes you can install isscript first and then everything is hunky dory
Other times it can be difficult.
have you tried installing isscript8 first?

I'm having a similar problem with another package. I set the ISSETUPDRIVEN=1 property in a transform and while I get the program files directory and many of the files, I don't get everything. I also don't get any of the start menu stuff or desktop shortcuts. I also noticed that when executing the install verbose, I don't get all of the dialogs that I get when running Setup.exe. There must be another property to tweak.

Shawn ,

You can check the INSTALLLEVEL value Set for this package . This May restrict some of the features to get installed .
" A Feature is installed only if the value in the Level field of the feature Table is less than or equal to the current INSTALLLEVEL value".

Cheers !!

I'm getting the same results, in that the msi looks like its installing but nothing actually gets installed. All the pre-reqs are installed (ISSCRIPT and a few others such as MSXML) I've set ISSETUPDRIVEN=1 and set the INSTALLLEVEL and also ensured the ONCHECKSILENTINSTALL custom action isn't running. Do I need to be listing all the features I want installing in the ADDLOCAL property?