FeatureMoveData does not move data!

[psr-Kumar]

Which event handler are you using to put FeatureTransferData in?
e.g. Before Move Data or Move Data and so on... Maybe that makes a difference.
-Kumar

[MonkeyK]

I do not believe any event handlers are being used explicitely. There is one main program and several functions. The main program calls functions and the functions call the installscript methods.

One function: "MoveFileData" calls the "FeatureTransferData" method. I can verify that FeatureTransferData is doing it's thing because I added "OnInstallFilesActionBefore" with code to verify the selected features.

One other thing that I noticed was that one of my features is getting installed, but none of the others are. The only difference in the feature parameters that I can see is the name and component assigned to it.

[davidh]

Try logging the install. Then, search for the feature names in the log. The log should give information on why the feature is not installing.

http://support.installshield.com/kb/...icleid=q105237

Also, search your code to find out if you are calling FeatureMoveData more than once. The help file for FeatureMoveData says that you can use it "more than once on the same media, but you must reset internal structures before the second and subsequent calls by calling FeatureMoveData with a null string (“”)"

[MonkeyK]

FeatureTransferData (and previously FeatureMoveData) is only being called once.

I created the log, but am not sure how to read it. One thing looks a little suspicous:
under the section
MSI (s) (F0:24): Doing action: InstallValidate
Action start 11:29:23: InstallValidate.

I can see the Feature that installs and one that does not (first one installs):
MSI (s) (F0:24): Feature: Print_Presentations; Installed: Absent; Request: Local; Action: Local
MSI (s) (F0:24): Feature: Annuities_Immed_Defer; Installed: Absent; Request: Local; Action: Local

They apear the same, however when respective components are listed:
MSI (s) (F0:24): Component: Print_Presentation_Template_Files; Installed: Local; Request: Null; Action: Local
MSI (s) (F0:24): Component: Annuity_Program_Files; Installed: Local; Request: Null; Action: Null

they vary in the action.

Does this mean anything?

[davidh]

Does the component 'Annuity_Program_Files' contain the data that is not being installed?

If so, I am not sure why MSI is not installing that component. All we know at this point, from the log, is that the request to install the component is null. Please try the following:
1. Perhaps MSI thinks that the component is already installed (it appears that this is the case because it says "Installed:Local). Msi keeps track of whether a component is installed by using the component code. Go to the Setup Design view, locate this component, and change the 'component code' property. Build and run the install again (make sure to uninstall the product from add/remove programs first).
2. If you have another machine that has never seen this installation (or a clean machine), the simpler option would be to run the install on a clean machine to see if the behavior is different.
3. Just to check, make sure the component is associated with a feature in the setup design view. Also, check the 'condition' property of the feature AND component to make sure a condition is not preventing the component from being installed.