Reinstallation problem

Jean-Francois Becan · Jan 9, 2004

After a windows 2000 problem, I don't succeed in reinstalling HP
Precisionscan Pro 3.1.Msi. It's the last thing I need to reinstall.
I have a 1625 Error This installation is forbidden by system policy. Contact
your system administrator.
The MSI*.LOG file contains :
=== Verbose logging started: 08/01/2004 23:55:59 Build type: SHIP UNICODE
2.00.2600.1183 Calling process: C:\WINNT\system32\MSIEXEC.EXE ===
MSI (c) (FC

C): Resetting cached policy values
MSI (c) (FC

C): Machine policy value 'Debug' is 7
MSI (c) (FC

C): ******* RunEngine:
******* Product: G:\HP\scanjet 5490c\Windows
2000\sj668\hppspro\HP Precisionscan Pro 3.1.Msi
******* Action:
******* CommandLine: HP5400C="Yes" TRANSFORMS="1036.MST"
MSI (c) (FC

C): Machine policy value 'DisableUserInstalls' is 0
MSI (c) (FC

C): Cloaking enabled.
MSI (c) (FC

C): End dialog not enabled
MSI (c) (FC

C): Original package ==> G:\HP\scanjet 5490c\Windows
2000\sj668\hppspro\HP Precisionscan Pro 3.1.Msi
MSI (c) (FC

C): Package we're running from ==>
C:\DOCUME~1\jfbecan\LOCALS~1\Temp\59e3d7.msi
MSI (c) (FC

C): APPCOMPAT: looking for appcompat database entry with
ProductCode '{6B36DEBF-27D0-4B1E-858D-D397091C6C7D}'.
MSI (c) (FC

C): APPCOMPAT: no matching ProductCode found in database.
MSI (c) (FC

C): APPCOMPAT: looking for appcompat database entry with
ProductCode '{6B36DEBF-27D0-4B1E-858D-D397091C6C7D}'.
MSI (c) (FC

C): APPCOMPAT: no matching ProductCode found in database.
MSI (c) (FC

C): Transforms are not secure.
MSI (c) (FC

C): Note: 1: 2262 2: Control 3: -2147287038
MSI (c) (FC

C): Command Line: HP5400C=Yes TRANSFORMS=1036.MST
CURRENTDIRECTORY=G:\HP\scanjet 5490c\Windows 2000\sj668 CLIENTUILEVEL=0
CLIENTPROCESSID=2300 %HOMEPATH=\Documents and Settings\jfbecan %HOMEDRIVE=C:
%HOMESHARE=
MSI (c) (FC

C): Product Code passed to Engine.Initialize: ''
MSI (c) (FC

C): Product Code from property table before transforms:
'{6B36DEBF-27D0-4B1E-858D-D397091C6C7D}'
MSI (c) (FC

C): Product Code from property table after transforms:
'{6B36DEBF-27D0-4B1E-858D-D397091C6C7D}'
MSI (c) (FC

C): Product registered: entering maintenance mode
MSI (c) (FC

C): Entering CMsiConfigurationManager::SetLastUsedSource.
MSI (c) (FC

C): Note: 1: 2720 2: 2
L'installation est interdite par la stratégie du système. Contactez votre
administrateur système.
G:\HP\scanjet 5490c\Windows 2000\sj668\hppspro\HP Precisionscan Pro 3.1.Msi
MSI (c) (FC

C): MainEngineThread is returning 1625
=== Verbose logging stopped: 08/01/2004 23:56:00 ===

Is there a mean to know why there is such problem with this file ?

How can I bypass this 1625 Error to reinstall entirely the package ?

I installed Windows Installer SDK and Orca, is there help file for Orca ?

Thanks

JF BECAN

nsperry · Jan 9, 2004

As it states 'a system policy' has been set to forbid you installing the
MSI, its probably AlwaysInstallElevated or DisableMSI

Take a look at
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/msi/setup/m
achine_policies.asp and see if any of these policies are set.

N

Jean-Francois Becan · Jan 10, 2004

I set some register values in
HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\Installer :
AllowLockdownBrowse = 1
AllowLockdownMedia = 1
AllowLockdownPatch = 1
AlwaysInstallElevated = 1 (also in
HKEY_CURRENT_USER\Software\Policies\Microsoft\Windows\Installer)
Debug = 2
DisableMSI = 0
DisableUserInstalls = 0
LimitSystemRestoreCheckpointing = 0
Logging = voicewarmup

But I have always the same problem : I have a 1625 Error "This installation
is forbidden by system policy. Contact your system administrator."

LOG File contains :
=== Verbose logging started: 10/01/2004 15:11:57 Build type: SHIP UNICODE
2.00.2600.1183 Calling process: C:\WINNT\system32\MSIEXEC.EXE ===MSI (c)
(2C:74): Resetting cached policy values

MSI (c) (2C:74): Machine policy value 'Debug' is 2

MSI (c) (2C:74): ******* RunEngine:

******* Product: G:\HP\scanjet 5490c\Windows 2000\sj668\hppspro\HP
Precisionscan Pro 3.1.Msi

******* Action:

******* CommandLine: **********

MSI (c) (2C:74): Machine policy value 'DisableUserInstalls' is 1

MSI (c) (2C:74): Cloaking enabled.

MSI (c) (2C:74): End dialog not enabled

MSI (c) (2C:74): Original package ==> G:\HP\scanjet 5490c\Windows
2000\sj668\hppspro\HP Precisionscan Pro 3.1.Msi

MSI (c) (2C:74): Package we're running from ==>
C:\DOCUME~1\jfbecan\LOCALS~1\Temp\27ffce.msi

MSI (c) (2C:74): APPCOMPAT: looking for appcompat database entry with
ProductCode '{6B36DEBF-27D0-4B1E-858D-D397091C6C7D}'.

MSI (c) (2C:74): APPCOMPAT: no matching ProductCode found in database.

MSI (c) (2C:74): APPCOMPAT: looking for appcompat database entry with
ProductCode '{6B36DEBF-27D0-4B1E-858D-D397091C6C7D}'.

MSI (c) (2C:74): APPCOMPAT: no matching ProductCode found in database.

MSI (c) (2C:74): Transforms are not secure.

MSI (c) (2C:74): Note: 1: 2262 2: Control 3: -2147287038

MSI (c) (2C:74): Command Line: HP5400C=Yes TRANSFORMS=1036.MST
CURRENTDIRECTORY=G:\HP\scanjet 5490c\Windows 2000\sj668 CLIENTUILEVEL=0
CLIENTPROCESSID=2092 %HOMEPATH=\Documents and Settings\jfbecan %HOMEDRIVE=C:
%HOMESHARE=

MSI (c) (2C:74): Product Code passed to Engine.Initialize: ''

MSI (c) (2C:74): Product Code from property table before transforms:
'{6B36DEBF-27D0-4B1E-858D-D397091C6C7D}'

MSI (c) (2C:74): Product Code from property table after transforms:
'{6B36DEBF-27D0-4B1E-858D-D397091C6C7D}'

MSI (c) (2C:74): Product registered: entering maintenance mode

MSI (c) (2C:74): Entering CMsiConfigurationManager::SetLastUsedSource.

MSI (c) (2C:74): Note: 1: 2720 2: 2

L'installation est interdite par la stratégie du système. Contactez votre
administrateur système.

G:\HP\scanjet 5490c\Windows 2000\sj668\hppspro\HP Precisionscan Pro 3.1.Msi

MSI (c) (2C:74): MainEngineThread is returning 1625

=== Verbose logging stopped: 10/01/2004 15:11:57 ===

Is there a mean to know clearly why does this 1625 error occur ?

Thanks

nsperry · Jan 11, 2004

According to your log file:

MSI (c) (2C:74): Machine policy value 'DisableUserInstalls' is 1

Which means a Machine Policy has been set in:

HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\Installer\DisableUser
Installs = 1

The DisableUserInstalls is a Machine Policy and should not be set in HKCU as
you've done, I actually think it ignores it anyway.

From the description from TechNet:

"If this policy is not set, the installer searches the registry for products
in the following order: managed products registered as per-user, unmanaged
products registered as per-user, and finally products registered as
per-machine.
If this policy is set to 1, the installer ignores all products registered as
per-user and only searches for products registered as per-machine. An
attempt to perform a per-user installation causes the installer to display
an error message and stops the installation.

Available with Windows Installer version 2.0 and later versions."

If ALLUSERS is not set, the installer does a per-user installation. If the
ALLUSERS property is set to 1, the installer attempts a per-machine
installation. The per-machine installation succeeds only if the user has
administrative access privileges on the computer. If ALLUSERS is set to 2,
the installer first attempts a per-machine installation. In this case, the
per-machine installation succeeds only if the user has administrative access
privileges on the computer, otherwise the installer does a per-user
installation. If ALLUSERS is set to 2, the installer always resets ALLUSERS
property to null or 1 based upon whether it determines to do a per-user or a
per-machine installation.

The best way to overcome your problem is the install your MSI as a
administrator. Quite simply your system administrators don't want people
installing MSI's or more to the point ones which are a per-user install.

N

Jean-Francois Becan · Jan 12, 2004

I certainly made a mistake, I retried to install "HP Precisionscan Pro
3.1.Msi" and I got this Log File ('DisableUserInstalls' is 0 as I set HKLM
value) :

=== Verbose logging started: 12/01/2004 02:13:58 Build type: SHIP UNICODE
2.00.2600.1183 Calling process: C:\WINNT\system32\MSIEXEC.EXE ===
MSI (c) (38:A8): Resetting cached policy values
MSI (c) (38:A8): Machine policy value 'Debug' is 2
MSI (c) (38:A8): ******* RunEngine:
******* Product: G:\HP\scanjet 5490c\Windows 2000\sj668\hppspro\HP
Precisionscan Pro 3.1.Msi
******* Action:
******* CommandLine: **********
MSI (c) (38:A8): Machine policy value 'DisableUserInstalls' is 0
MSI (c) (38:A8): Cloaking enabled.
MSI (c) (38:A8): End dialog not enabled
MSI (c) (38:A8): Original package ==> G:\HP\scanjet 5490c\Windows
2000\sj668\hppspro\HP Precisionscan Pro 3.1.Msi
MSI (c) (38:A8): Package we're running from ==>
C:\DOCUME~1\jfbecan\LOCALS~1\Temp\cd6c2.msi
MSI (c) (38:A8): APPCOMPAT: looking for appcompat database entry with
ProductCode '{6B36DEBF-27D0-4B1E-858D-D397091C6C7D}'.
MSI (c) (38:A8): APPCOMPAT: no matching ProductCode found in database.
MSI (c) (38:A8): APPCOMPAT: looking for appcompat database entry with
ProductCode '{6B36DEBF-27D0-4B1E-858D-D397091C6C7D}'.
MSI (c) (38:A8): APPCOMPAT: no matching ProductCode found in database.
MSI (c) (38:A8): Transforms are not secure.
MSI (c) (38:A8): Note: 1: 2262 2: Control 3: -2147287038
MSI (c) (38:A8): Command Line: HP5400C=Yes TRANSFORMS=1036.MST
CURRENTDIRECTORY=G:\HP\scanjet 5490c\Windows 2000\sj668 CLIENTUILEVEL=0
CLIENTPROCESSID=1848 %HOMEPATH=\Documents and Settings\jfbecan %HOMEDRIVE=C:
%HOMESHARE=
MSI (c) (38:A8): Product Code passed to Engine.Initialize: ''
MSI (c) (38:A8): Product Code from property table before transforms:
'{6B36DEBF-27D0-4B1E-858D-D397091C6C7D}'
MSI (c) (38:A8): Product Code from property table after transforms:
'{6B36DEBF-27D0-4B1E-858D-D397091C6C7D}'
MSI (c) (38:A8): Product registered: entering maintenance mode
MSI (c) (38:A8): Entering CMsiConfigurationManager::SetLastUsedSource.
MSI (c) (38:A8): Note: 1: 2720 2: 2
L'installation est interdite par la stratégie du système. Contactez votre
administrateur système.
G:\HP\scanjet 5490c\Windows 2000\sj668\hppspro\HP Precisionscan Pro 3.1.Msi
MSI (c) (38:A8): MainEngineThread is returning 1625
=== Verbose logging stopped: 12/01/2004 02:13:59 ===

I am the administrator of this computer and install MSI with administrator
rights. I don't understand why I have this 1625 Error, I set nearly all
register values to enable the installation but I have same result.

Perhaps, is there a problem with Windows Installer. Is there a mean to
entirely uninstall it and then completly reinstall it to be sure there is no
problem with a DLL or an EXE file ?

"nsperry" <[email protected] <mailto:[email protected]>> a écrit dans le message

de said:
MSI (c) (2C:74): Machine policy value 'DisableUserInstalls' is 1

Which means a Machine Policy has been set in:

HKEY_LOCAL_MACHINE\Software\Policies\Microsoft\Windows\Installer\DisableUser
Installs = 1

The DisableUserInstalls is a Machine Policy and should not be set in HKCU as
you've done, I actually think it ignores it anyway.

From the description from TechNet:

"If this policy is not set, the installer searches the registry for products
in the following order: managed products registered as per-user, unmanaged
products registered as per-user, and finally products registered as
per-machine.
If this policy is set to 1, the installer ignores all products registered as
per-user and only searches for products registered as per-machine. An
attempt to perform a per-user installation causes the installer to display
an error message and stops the installation.

Available with Windows Installer version 2.0 and later versions."

If ALLUSERS is not set, the installer does a per-user installation. If the
ALLUSERS property is set to 1, the installer attempts a per-machine
installation. The per-machine installation succeeds only if the user has
administrative access privileges on the computer. If ALLUSERS is set to 2,
the installer first attempts a per-machine installation. In this case, the
per-machine installation succeeds only if the user has administrative access
privileges on the computer, otherwise the installer does a per-user
installation. If ALLUSERS is set to 2, the installer always resets ALLUSERS
property to null or 1 based upon whether it determines to do a per-user or a
per-machine installation.

The best way to overcome your problem is the install your MSI as a
administrator. Quite simply your system administrators don't want people
installing MSI's or more to the point ones which are a per-user install.

N

"Jean-Francois Becan" <[email protected]

....

<http://msdn.microsoft.com/library/default.asp?url=/library/en-us/msi/setup/
m>

....

nsperry · Jan 12, 2004

From the log file it seems the product is already installed in some way:

MSI (c) (38:A8): Product registered: entering maintenance mode
MSI (c) (38:A8): Entering CMsiConfigurationManager::SetLastUsedSource.

Trying running msiexec /x {6B36DEBF-27D0-4B1E-858D-D397091C6C7D} from the
command line , which should uninstall the MSI, and see what message you get
back. Then try and install it again.

N

Jean-Francois Becan · Jan 12, 2004

Thank a lot for your help.

I tried "msiexec /x {6B36DEBF-27D0-4B1E-858D-D397091C6C7D}"

and obtained the following Log File :

=== Verbose logging started: 12/01/2004 20:58:47 Build type: SHIP UNICODE
2.00.2600.1183 Calling process: C:\WINNT\system32\msiexec.exe ===
MSI (c) (00:50): Resetting cached policy values
MSI (c) (00:50): Machine policy value 'Debug' is 2
MSI (c) (00:50): ******* RunEngine:
******* Product: {6B36DEBF-27D0-4B1E-858D-D397091C6C7D}
******* Action:
******* CommandLine: **********
MSI (c) (00:50): Client-side and UI is none or basic: Running entire install
on the server.
MSI (c) (00:50): Grabbed execution mutex.
MSI (c) (00:50): Cloaking enabled.
MSI (c) (00:50): Incrementing counter to disable shutdown. Counter after
increment: 0
MSI (s) (B0

0): Resetting cached policy values
MSI (s) (B0

0): Machine policy value 'Debug' is 2
MSI (s) (B0

0): ******* RunEngine:
******* Product: {6B36DEBF-27D0-4B1E-858D-D397091C6C7D}
******* Action:
******* CommandLine: **********
MSI (s) (B0

0): Machine policy value 'DisableUserInstalls' is 0
MSI (s) (B0

0): Setting cached product context: machine assigned for
product: FBED63B60D72E1B458D83D7990C1C6D7
MSI (s) (B0

0): Using cached product context: machine assigned for product:
FBED63B60D72E1B458D83D7990C1C6D7
MSI (s) (B0

0): End dialog not enabled
MSI (s) (B0

0): Original package ==> C:\WINNT\Installer\2e1eae.msi
MSI (s) (B0

0): Package we're running from ==>
C:\WINNT\Installer\2e1eae.msi
MSI (s) (B0

0): Using cached product context: machine assigned for product:
FBED63B60D72E1B458D83D7990C1C6D7
MSI (s) (B0

0): APPCOMPAT: looking for appcompat database entry with
ProductCode '{6B36DEBF-27D0-4B1E-858D-D397091C6C7D}'.
MSI (s) (B0

0): APPCOMPAT: no matching ProductCode found in database.
MSI (s) (B0

0): Using cached product context: machine assigned for product:
FBED63B60D72E1B458D83D7990C1C6D7
MSI (s) (B0

0): APPCOMPAT: looking for appcompat database entry with
ProductCode '{6B36DEBF-27D0-4B1E-858D-D397091C6C7D}'.
MSI (s) (B0

0): APPCOMPAT: no matching ProductCode found in database.
MSI (s) (B0

0): Transforms are not secure.
MSI (s) (B0

0): Note: 1: 2262 2: Control 3: -2147287038
MSI (s) (B0

0): Command Line: REMOVE=ALL CURRENTDIRECTORY=C:\Documents and
Settings\jfbecan CLIENTUILEVEL=2 CLIENTPROCESSID=2048 %HOMEPATH=\Documents
and Settings\jfbecan %HOMEDRIVE=C: %HOMESHARE=
MSI (s) (B0

0): Product Code passed to Engine.Initialize:
'{6B36DEBF-27D0-4B1E-858D-D397091C6C7D}'
MSI (s) (B0

0): Product Code from property table before transforms:
'{6B36DEBF-27D0-4B1E-858D-D397091C6C7D}'
MSI (s) (B0

0): Product Code from property table after transforms:
'{6B36DEBF-27D0-4B1E-858D-D397091C6C7D}'
MSI (s) (B0

0): Product registered: entering maintenance mode
MSI (s) (B0

0): Using cached product context: machine assigned for product:
FBED63B60D72E1B458D83D7990C1C6D7
MSI (s) (B0

0): Using cached product context: machine assigned for product:
FBED63B60D72E1B458D83D7990C1C6D7
Une autre version de ce produit est déjà installée. L'installation de cette
version ne peut pas continuer. Pour configurer ou supprimer la version
existante de ce produit utilisez Ajout/Suppression de programmes depuis le
Panneau de configuration.
{6B36DEBF-27D0-4B1E-858D-D397091C6C7D}
MSI (s) (B0

0): MainEngineThread is returning 1638
MSI (c) (00:50): Decrementing counter to disable shutdown. If counter >= 0,
shutdown will be denied. Counter after decrement: -1
MSI (c) (00:50): MainEngineThread is returning 1638
=== Verbose logging stopped: 12/01/2004 20:58:48 ===

A dialog box appeared telling me another installation is present.

Jean-Francois BECAN

nsperry · Jan 12, 2004

Did you get this message while uninstalling the product using "msiexec /x
{6B36DEBF-27D0-4B1E-858D-D397091C6C7D}" ??

Does the follwoing registry key exist:

HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\Current
Version\Uninstall\{6B36DEBF-27D0-4B1E-858D-D397091C6C7D}

and what value does UninstallString have?

nsperry · Jan 12, 2004

Another thing to do is run the Windows Installer Cleanup Utility
http://support.microsoft.com/default.aspx?scid=kb;EN-US;238413. This utility
cleans up registry
information left be a corrupt Windows Installer package. I would strongly
recommend you backup your registry before you run this though.

N

Jean-Francois Becan · Jan 12, 2004

Yes, I got this message during uninstallation using msiexec /x
{6B36DEBF-27D0-4B1E-858D-D397091C6C7D}" .

I don't find "HKEY_LOCAL_MACHINE\Software\Microsoft\Windows\Current
Version\Uninstall\{6B36DEBF-27D0-4B1E-858D-D397091C6C7D}" key.
The two only keys I found where I have
"{6B36DEBF-27D0-4B1E-858D-D397091C6C7D}" string are
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\App
Management\ARPCache\{6B36DEBF-27D0-4B1E-858D-D397091C6C7D}
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Installer\UserD
ata\S-1-5-18\Products\FBED63B60D72E1B458D83D7990C1C6D7\InstallProperties
(ModifyPath and UninstallString with same value : "MsiExec.exe
/I{6B36DEBF-27D0-4B1E-858D-D397091C6C7D}").

Jean-Francois Becan · Jan 12, 2004

In the page you indicated, I can see :
1 - Important The Msicu.exe and Msicuu.exe utilities are not supported on
systems where Microsoft Windows Installer 2.0 or later is installed,
including Microsoft Windows XP.
2 - If your version is earlier than 2.0, for example 1.1, the Windows
Installer CleanUp Tool is supported on your system.

My version is 2.0.2600.1183, I suppose Windows Installer CleanUp Tool is not
supported on mysystem.

Is there a version working for version later than 2.0 ?

Thanks

Carolyn Napier [MSFT] · Jan 17, 2004

The only problem with MSICU.EXE (and MSICUU.EXE) is that it doesn't support
machines with Windows Installer version 2.0. The utility is just a GUI wrapper
around MSIZAP.EXE. Most of what you can accomplish using MSICU/MSICUU you should
be able to do with MSIZAP.

All you need to do is obtain the latest version of MSIZAP.EXE (minimum version
of 2.0.2600.0). This tool is found in the Windows Installer SDK at <
http://www.microsoft.com/msdownload/platformsdk/sdkupdate/ >. Instructions on
how to use the tool can be found in the Windows Installer MSDN documentation at
<
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/msi/setup/msizap_exe.asp

.

Hope this helps,
- Carolyn Napier
Microsoft Windows Installer Team

--
This posting is provided "AS IS" with no warranties, and confers no rights.
Please do not send email directly to this alias. This alias is for newsgroup
purposes only.
MSI FAQ:
<http://www.microsoft.com/windows2000/community/centers/management/msi_faq.mspx>

Carolyn Napier [MSFT] · Jan 17, 2004

Were there any other MSI packages at G:\HP\scanjet 5490c\Windows
2000\sj668\hppspro or some directory above that within the path? The error
messages provided here almost seem that the HP Precisionscan Pro 3.1.Msi was
installed as a nested installation of some parent product. (At least, that would
partially explain the 1:2720 2: 2 error message which indicates that the source
list key for the product was not found -- nested installs do not have their own
source list).

If this is a nested installation, you can't accomplish the reinstall directly
through the package. You have to use the "parent" installation package that
installed the product as a nested installation.

Outside of that, the MSIZAP possibility (discussed within this thread) is one
way to remove the registration so that you can just install the single MSI
package.

- Carolyn Napier
Microsoft Windows Installer Team

--
This posting is provided "AS IS" with no warranties, and confers no rights.
Please do not send email directly to this alias. This alias is for newsgroup
purposes only.
MSI FAQ:
<http://www.microsoft.com/windows2000/community/centers/management/msi_faq.mspx>

csteddy · Feb 26, 2009

InstEd is a free MSI editor from www.instedit.com

Reinstallation problem

Jean-Francois Becan

nsperry

Jean-Francois Becan

nsperry

Jean-Francois Becan

nsperry

Jean-Francois Becan

nsperry

nsperry

Jean-Francois Becan

Jean-Francois Becan

Carolyn Napier [MSFT]

Carolyn Napier [MSFT]

csteddy