ISSETUPDRIVEN and not installing files
Hi,
I have a msi that needs the setup.exe run to install. (ISSCRIPT8.msi is part of it too). I included the property ISSETUPDRIVEN=1, and the msi is not screaming anymore that it needs to run by setup.exe.
So, thought I could make a mst, but no such luck.
I put a comment in front of OnCheckSilentinstall.
Eventhough that the progress bar is making you believe it's installing the msi, nothing get's installed. Program Files is empty. This software is Act 2006.
Any ideas?
Thank you.
Gizsha
I have a msi that needs the setup.exe run to install. (ISSCRIPT8.msi is part of it too). I included the property ISSETUPDRIVEN=1, and the msi is not screaming anymore that it needs to run by setup.exe.
So, thought I could make a mst, but no such luck.
I put a comment in front of OnCheckSilentinstall.
Eventhough that the progress bar is making you believe it's installing the msi, nothing get's installed. Program Files is empty. This software is Act 2006.
Any ideas?
Thank you.
Gizsha
0 Comments
[ + ] Show comments
Answers (10)
Please log in to answer
Posted by:
anonymous_9363
15 years ago
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.
.........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.
Posted by:
wynnem
15 years ago
Thanks VBScab...
I've found this: http://helpnet.acresso.com/robo/projects/adminstudio75/ISRTaskConvertISMSI.htm
Do you think its worth doing the conversion?
I've found this: http://helpnet.acresso.com/robo/projects/adminstudio75/ISRTaskConvertISMSI.htm
Do you think its worth doing the conversion?
Posted by:
anonymous_9363
15 years ago
ORIGINAL: wynnemI 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.
Do you think its worth doing the conversion?
Posted by:
vmnit
11 years ago
Please go through this link http://www.symantec.com/business/support/index?page=content&id=HOWTO4204
Posted by:
vmnit
11 years ago
Even this is also useful...http://www.symantec.com/connect/blogs/how-solve-error-msi-can-be-installed-through-setupexe-only
Posted by:
viswakar
18 years ago
Posted by:
aogilmor
18 years ago
Posted by:
Shawnz
18 years ago
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.
Posted by:
viswakar
18 years ago
Posted by:
wynnem
15 years ago
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?
Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.
so that the conversation will remain readable.