Software Deployment

It seems to me more likely that the INI file hasn't been installed to the target folder before the action requiring it (CTMEM_EncryptUserPasswordScript?) gets run. Have a look at the sequencing. 1024 means that it's an ExecuteDeferred action.

ORIGINAL: VBScab

It seems to me more likely that the INI file hasn't been installed to the target folder before the action requiring it (CTMEM_EncryptUserPasswordScript?) gets run. Have a look at the sequencing. 1024 means that it's an ExecuteDeferred action.



Sequencing would not change depending on UI level would it? Was 1024 a typo on your part or did you really mean 1024? I was asking about 1042. Doing some testing I see that the file is not getting copied. Since it is just a file listed in the Files table what would prevent it from being copied?

I do not think it was a typo.
From the log:
MSI (s) (B8:38) [14:24:47:593]: Executing op: CustomActionSchedule(Action=CTMEM_EncryptUserPasswordScript,ActionType=1025,Source=BinaryData,Target=f69,)
1025 = Custom Action Type 1 (DLL file stored in a Binary table stream.) + (Custom Action In-Script Execution Options) msidbCustomActionTypeInScript; 1 + 1024

1042 would be Custom Action Type 18 (This custom action calls an executable launched with a command line.) + msidbCustomActionTypeInScript; 18 + 1024

Looking at the log files for a successful and unsuccessful installation I cannot find any reference to to the missing file getting copied. I did a manual file copy during a /qb install and the installation completed successfully. I cannot figure out why this file is not getting copied during a /qb install but magically appears during a /qr install. This is just a file in the file table not a dynamically created file during the install. In case someone sees something I don't I've included the lines from the different tables that reference this file.


File:
_DFF75AAB10394FEAAE76D2ABECD29CD3 _B636D01A90134D5D95047377BC8132DB CLIENT~1.INI|ClientServerSSL.ini 50 16385 5094

ISDLInfo:
_203D07F9317F4084A5444AF56A932129 _B636D01A90134D5D95047377BC8132DB CommonServerReportFacFolder|<PACK_LOCATION_INST>\commonserverreportfac\ini\ssl

Component:
_B636D01A90134D5D95047377BC8132DB {B636D01A-9013-4D5D-9504-7377BC8132DB} _203D07F9317F4084A5444AF56A932129 0 (TASK_SELCTION = "FULL_INST") OR ((TASK_SELCTION = "BASIC_INST") AND (REPORT_FAC = "Yes")) _DFF75AAB10394FEAAE76D2ABECD29CD3

Feature Components:
CTMEM_COMMON_SERVER_REPORTFAC _B636D01A90134D5D95047377BC8132DB



Sounds like a condition issue
(TASK_SELCTION = "FULL_INST") OR ((TASK_SELCTION = "BASIC_INST") AND (REPORT_FAC = "Yes"))

What value does the TASK_SELCTION & REPORT_FAC property hold during install?

As a previous test I had removed the condition but ended up with the same results.

Checking the log files for the successful install and unsuccessful install there is no value for the REPORT_FAC property in either log file but the property is listed in the successful log file. But what is strange is it's not listed at the end of the log file where all the property values are listed. Is this because it had no value? Both log files have a TASK_SELCTION entry and both have the same value of BASIC_INST

Check the log to see if the component is set to be installed.

log example:
Component: <Component.Component> Installed: Null; Request: Local; Action: Local;

Yes, I had looked at that but since it was the same for the successful install and unsuccessful I figured that would probably not be the issue. Here is what the log shows:


MSI (s) (C4:C0) [09:18:15:750]: Component: _B636D01A90134D5D95047377BC8132DB; Installed: Absent; Request: Null; Action: Null


It's a puzzle to me as to why for the successful install and unsuccessful there is not entry in the log for the installation of this component or for installing the file.

Ok, I got this figured out. I was missing the REPORT_FAC in the property table. Even though it is set to zero it apparently needs to exist. I figured that if the property was 0 the entry would not need to present.