.Net Framework error
The error, triggered at SxsInstallCA, is:
MSI (s) (18!84) [14:41:46:857]: Product: Microsoft .NET Framework 2.0 -- 1: ALLUSERS property is not 1 - this MSM cannot be used for a per-user or fallback-to-per-user install 2:
The very-wonderful Aaron Stebler's blog points to a cause but this is not the case here: there is no trace whatsoever of an existing installation. I thus got to digging deeper and elsewhere (lost the link...DAMN!) I read that replacing the VC80 runtime merge module fixes the problem.
My problem is, which of the MMs listed in the MSI is the VC80 one?!? The list is:
_32_bit_specific
BetaBlockDetect
CSharp_Watson20_RegKeys
Disable_Cancel_CA
GUIH_ARP_NETFXDIR_URT_STD_ENU_X86_IXP
GUIH_MaintMode_URT
mondo_urtm_std_enu_x86_ixp
NgenService_InstallControl_X86
Patch_PFRO_Assembly
PatchHooks_msm
SNV_Bypass_Key_Removal
SNV_RemoveReg
SourceList_CA
Watson
Watson20_Reg_Keys
WatsonIntl
Or am I barking up the wrong tree? Does anyone have experience of this error?
MSI (s) (18!84) [14:41:46:857]: Product: Microsoft .NET Framework 2.0 -- 1: ALLUSERS property is not 1 - this MSM cannot be used for a per-user or fallback-to-per-user install 2:
The very-wonderful Aaron Stebler's blog points to a cause but this is not the case here: there is no trace whatsoever of an existing installation. I thus got to digging deeper and elsewhere (lost the link...DAMN!) I read that replacing the VC80 runtime merge module fixes the problem.
My problem is, which of the MMs listed in the MSI is the VC80 one?!? The list is:
_32_bit_specific
BetaBlockDetect
CSharp_Watson20_RegKeys
Disable_Cancel_CA
GUIH_ARP_NETFXDIR_URT_STD_ENU_X86_IXP
GUIH_MaintMode_URT
mondo_urtm_std_enu_x86_ixp
NgenService_InstallControl_X86
Patch_PFRO_Assembly
PatchHooks_msm
SNV_Bypass_Key_Removal
SNV_RemoveReg
SourceList_CA
Watson
Watson20_Reg_Keys
WatsonIntl
Or am I barking up the wrong tree? Does anyone have experience of this error?
0 Comments
[ + ] Show comments
Answers (4)
Please log in to answer
Posted by:
spartacus
17 years ago
Are you using InstallShield to develop your packages, by any chance ?
This link may help if you are.
Regards,
Spartacus
This link may help if you are.
Regards,
Spartacus
Posted by:
anonymous_9363
17 years ago
No, we use WPS. In any event, one of the first things I do when packaging with dependencies is run a script against the main MSI and any called/nested MSIs to make sure that this kind of thing is aligned. ALLUSERS is top of the list. Thanks for the thought, though.
Posted by:
spartacus
17 years ago
So just to clarify, do you have the IsInitAllusers custom action anywhere in your package and, if so, is it setting ALLUSERS to 2 by any chance ?
Regards,
Spartacus
Regards,
Spartacus
Posted by:
anonymous_9363
17 years ago
This is the .Net f/w MSI as supplied by MS. There are no IS properties at all and no reference to ALLUSERS in any of the CAs.
My MST has ALLUSERS set to '1' and I've tried passing the property to the MSI on the command line as well (paranoia...)
My MST has ALLUSERS set to '1' and I've tried passing the property to the MSI on the command line as well (paranoia...)
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.