gbilios
asked on
ALLUSERS Property is NOT 1
I get this error during .msi installation - But during installation this merge module gives an error: "1: ALLUSERS property is not 1 - the MSM cannot be used for a per-user or fallback-to-per-user install
Where is this ALLUSERS property so i can change it?
Where is this ALLUSERS property so i can change it?
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
sorry, disregard the pi bit - typo
ASKER
This is the action for opening / installing the .msi package in the folder options -> edit:
"C:\WINNT\system32\msiexec
I replaced 1 with nothing or added a 2 and the installer file fails to launch.
"C:\WINNT\system32\msiexec
I replaced 1 with nothing or added a 2 and the installer file fails to launch.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
i downloaded ORCA and changed the ALLUSERS property to 2 and the .msi installer file does not install. The error says that the .msi installer file is missing.
ASKER
i change any values whether it is null, 1 or 2, the msi installer fails to install. I get the following error code in the install.log file MsiInstallProduct returned '1619' - the package does not exist.
how do i fix this problem?
how do i fix this problem?
ASKER
okay, i just found out that having orca running at the same time as the .msi installation causes the '1619' error. Can you please explain why the .msi installer still does not install per user/machine even if i change the ALLUSERS value to 1 or 2? What else is there? Do i have to re-build the setup project?
ALLUSERS=2 is not a specific mode: the Installer service works out if the user is an admin and if so, installs it per-machine. If the user is not an admin, it attempts to install it per user (equivalent to ALLUSERS=0). If you want a per-user install, set ALLUSERS=0. However, it will fail if the package attempts to install to restricted areas.
If you're still getting problems, set the install to create a verbose log, using the commandline switch /L*V <Log filename>. This will give you more information.
If you're still getting problems, set the install to create a verbose log, using the commandline switch /L*V <Log filename>. This will give you more information.
ASKER
i am going to install the msi installer on the client's machine. i am concerned whether the settings remain the same for per user/machine install.
I heard from another customer with the same problem. On their system, the .NET Framework 2.0 had been advertised on their system as a per-user install, likely by an Active Directory group policy deployment on their network. They were able to solve this issue by uninstalling the advertised version of the .NET Framework from Add/Remove Programs and then re-running the dotnetfx.exe installer to install the .NET Framework 2.0.
If uninstalling from Add/Remove Programs doesn't help, or if you don't have an Add/Remove Programs entry for the .NET Framework 2.0, you may need to use the automated cleanup tool described at http://blogs.msdn.com/astebner/archive/2006/05/30/611355.aspx.
If uninstalling from Add/Remove Programs doesn't help, or if you don't have an Add/Remove Programs entry for the .NET Framework 2.0, you may need to use the automated cleanup tool described at http://blogs.msdn.com/astebner/archive/2006/05/30/611355.aspx.
ASKER
of msiexec /i MyPackage.msi ALLUSERS="1"
The .msi installer should also be able to install per user/machine.
the command line does not work. Is there a property in the .msi pi project where i can enter this command?