PC Review


Reply
Thread Tools Rating: Thread Rating: 3 votes, 2.33 average.

Reinstallation problem

 
 
Jean-Francois Becan
Guest
Posts: n/a
 
      13th Jan 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

>"nsperry" <(E-Mail Removed)> a écrit dans le message de

news:Ol%(E-Mail Removed)...
> Another thing to do is run the Windows Installer Cleanup Utility
> http://support.microsoft.com/default...b;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
>
> "nsperry" <(E-Mail Removed)> wrote in message
> news:#(E-Mail Removed)...
> > 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?
> >
> > "Jean-Francois Becan" <(E-Mail Removed)> wrote in message
> > news:#(E-Mail Removed)...
> > > 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) (B00): Resetting cached policy values
> > > MSI (s) (B00): Machine policy value 'Debug' is 2
> > > MSI (s) (B00): ******* RunEngine:
> > > ******* Product: {6B36DEBF-27D0-4B1E-858D-D397091C6C7D}
> > > ******* Action:
> > > ******* CommandLine: **********
> > > MSI (s) (B00): Machine policy value 'DisableUserInstalls' is 0
> > > MSI (s) (B00): Setting cached product context: machine assigned for
> > > product: FBED63B60D72E1B458D83D7990C1C6D7
> > > MSI (s) (B00): Using cached product context: machine assigned for

> > product:
> > > FBED63B60D72E1B458D83D7990C1C6D7
> > > MSI (s) (B00): Using cached product context: machine assigned for

> > product:
> > > FBED63B60D72E1B458D83D7990C1C6D7
> > > MSI (s) (B00): Using cached product context: machine assigned for

> > product:
> > > FBED63B60D72E1B458D83D7990C1C6D7
> > > MSI (s) (B00): Using cached product context: machine assigned for

> > product:
> > > FBED63B60D72E1B458D83D7990C1C6D7
> > > MSI (s) (B00): Using cached product context: machine assigned for

> > product:
> > > FBED63B60D72E1B458D83D7990C1C6D7
> > > MSI (s) (B00): Using cached product context: machine assigned for

> > product:
> > > FBED63B60D72E1B458D83D7990C1C6D7
> > > MSI (s) (B00): End dialog not enabled
> > > MSI (s) (B00): Original package ==> C:\WINNT\Installer\2e1eae.msi
> > > MSI (s) (B00): Package we're running from ==>
> > > C:\WINNT\Installer\2e1eae.msi
> > > MSI (s) (B00): Using cached product context: machine assigned for

> > product:
> > > FBED63B60D72E1B458D83D7990C1C6D7
> > > MSI (s) (B00): Using cached product context: machine assigned for

> > product:
> > > FBED63B60D72E1B458D83D7990C1C6D7
> > > MSI (s) (B00): APPCOMPAT: looking for appcompat database entry with
> > > ProductCode '{6B36DEBF-27D0-4B1E-858D-D397091C6C7D}'.
> > > MSI (s) (B00): APPCOMPAT: no matching ProductCode found in database.
> > > MSI (s) (B00): Using cached product context: machine assigned for

> > product:
> > > FBED63B60D72E1B458D83D7990C1C6D7
> > > MSI (s) (B00): Using cached product context: machine assigned for

> > product:
> > > FBED63B60D72E1B458D83D7990C1C6D7
> > > MSI (s) (B00): Using cached product context: machine assigned for

> > product:
> > > FBED63B60D72E1B458D83D7990C1C6D7
> > > MSI (s) (B00): Using cached product context: machine assigned for

> > product:
> > > FBED63B60D72E1B458D83D7990C1C6D7
> > > MSI (s) (B00): APPCOMPAT: looking for appcompat database entry with
> > > ProductCode '{6B36DEBF-27D0-4B1E-858D-D397091C6C7D}'.
> > > MSI (s) (B00): APPCOMPAT: no matching ProductCode found in database.
> > > MSI (s) (B00): Transforms are not secure.
> > > MSI (s) (B00): Note: 1: 2262 2: Control 3: -2147287038
> > > MSI (s) (B00): Command Line: REMOVE=ALL

CURRENTDIRECTORY=C:\Documents
> > and
> > > Settings\jfbecan CLIENTUILEVEL=2 CLIENTPROCESSID=2048

> %HOMEPATH=\Documents
> > > and Settings\jfbecan %HOMEDRIVE=C: %HOMESHARE=
> > > MSI (s) (B00): Product Code passed to Engine.Initialize:
> > > '{6B36DEBF-27D0-4B1E-858D-D397091C6C7D}'
> > > MSI (s) (B00): Product Code from property table before transforms:
> > > '{6B36DEBF-27D0-4B1E-858D-D397091C6C7D}'
> > > MSI (s) (B00): Product Code from property table after transforms:
> > > '{6B36DEBF-27D0-4B1E-858D-D397091C6C7D}'
> > > MSI (s) (B00): Product registered: entering maintenance mode
> > > MSI (s) (B00): Using cached product context: machine assigned for

> > product:
> > > FBED63B60D72E1B458D83D7990C1C6D7
> > > MSI (s) (B00): Using cached product context: machine assigned for

> > product:
> > > FBED63B60D72E1B458D83D7990C1C6D7
> > > MSI (s) (B00): 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) (B00): 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" <(E-Mail Removed)> a écrit dans le message de
> > > news:(E-Mail Removed)...
> > > > 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.
> > > >
> > >
> > >

> >
> >

>
>



 
Reply With Quote
 
 
 
 
Carolyn Napier [MSFT]
Guest
Posts: n/a
 
      17th Jan 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/...sdk/sdkupdate/ >. Instructions on
how to use the tool can be found in the Windows Installer MSDN documentation at
<
http://msdn.microsoft.com/library/de...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>

"Jean-Francois Becan" <(E-Mail Removed)> wrote in message
news:e9AsT$(E-Mail Removed)...
> 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
>
>>"nsperry" <(E-Mail Removed)> a écrit dans le message de

> news:Ol%(E-Mail Removed)...
>> Another thing to do is run the Windows Installer Cleanup Utility
>> http://support.microsoft.com/default...b;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
>>
>> "nsperry" <(E-Mail Removed)> wrote in message
>> news:#(E-Mail Removed)...
>> > 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?
>> >
>> > "Jean-Francois Becan" <(E-Mail Removed)> wrote in message
>> > news:#(E-Mail Removed)...
>> > > 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) (B00): Resetting cached policy values
>> > > MSI (s) (B00): Machine policy value 'Debug' is 2
>> > > MSI (s) (B00): ******* RunEngine:
>> > > ******* Product: {6B36DEBF-27D0-4B1E-858D-D397091C6C7D}
>> > > ******* Action:
>> > > ******* CommandLine: **********
>> > > MSI (s) (B00): Machine policy value 'DisableUserInstalls' is 0
>> > > MSI (s) (B00): Setting cached product context: machine assigned for
>> > > product: FBED63B60D72E1B458D83D7990C1C6D7
>> > > MSI (s) (B00): Using cached product context: machine assigned for
>> > product:
>> > > FBED63B60D72E1B458D83D7990C1C6D7
>> > > MSI (s) (B00): Using cached product context: machine assigned for
>> > product:
>> > > FBED63B60D72E1B458D83D7990C1C6D7
>> > > MSI (s) (B00): Using cached product context: machine assigned for
>> > product:
>> > > FBED63B60D72E1B458D83D7990C1C6D7
>> > > MSI (s) (B00): Using cached product context: machine assigned for
>> > product:
>> > > FBED63B60D72E1B458D83D7990C1C6D7
>> > > MSI (s) (B00): Using cached product context: machine assigned for
>> > product:
>> > > FBED63B60D72E1B458D83D7990C1C6D7
>> > > MSI (s) (B00): Using cached product context: machine assigned for
>> > product:
>> > > FBED63B60D72E1B458D83D7990C1C6D7
>> > > MSI (s) (B00): End dialog not enabled
>> > > MSI (s) (B00): Original package ==> C:\WINNT\Installer\2e1eae.msi
>> > > MSI (s) (B00): Package we're running from ==>
>> > > C:\WINNT\Installer\2e1eae.msi
>> > > MSI (s) (B00): Using cached product context: machine assigned for
>> > product:
>> > > FBED63B60D72E1B458D83D7990C1C6D7
>> > > MSI (s) (B00): Using cached product context: machine assigned for
>> > product:
>> > > FBED63B60D72E1B458D83D7990C1C6D7
>> > > MSI (s) (B00): APPCOMPAT: looking for appcompat database entry with
>> > > ProductCode '{6B36DEBF-27D0-4B1E-858D-D397091C6C7D}'.
>> > > MSI (s) (B00): APPCOMPAT: no matching ProductCode found in database.
>> > > MSI (s) (B00): Using cached product context: machine assigned for
>> > product:
>> > > FBED63B60D72E1B458D83D7990C1C6D7
>> > > MSI (s) (B00): Using cached product context: machine assigned for
>> > product:
>> > > FBED63B60D72E1B458D83D7990C1C6D7
>> > > MSI (s) (B00): Using cached product context: machine assigned for
>> > product:
>> > > FBED63B60D72E1B458D83D7990C1C6D7
>> > > MSI (s) (B00): Using cached product context: machine assigned for
>> > product:
>> > > FBED63B60D72E1B458D83D7990C1C6D7
>> > > MSI (s) (B00): APPCOMPAT: looking for appcompat database entry with
>> > > ProductCode '{6B36DEBF-27D0-4B1E-858D-D397091C6C7D}'.
>> > > MSI (s) (B00): APPCOMPAT: no matching ProductCode found in database.
>> > > MSI (s) (B00): Transforms are not secure.
>> > > MSI (s) (B00): Note: 1: 2262 2: Control 3: -2147287038
>> > > MSI (s) (B00): Command Line: REMOVE=ALL

> CURRENTDIRECTORY=C:\Documents
>> > and
>> > > Settings\jfbecan CLIENTUILEVEL=2 CLIENTPROCESSID=2048

>> %HOMEPATH=\Documents
>> > > and Settings\jfbecan %HOMEDRIVE=C: %HOMESHARE=
>> > > MSI (s) (B00): Product Code passed to Engine.Initialize:
>> > > '{6B36DEBF-27D0-4B1E-858D-D397091C6C7D}'
>> > > MSI (s) (B00): Product Code from property table before transforms:
>> > > '{6B36DEBF-27D0-4B1E-858D-D397091C6C7D}'
>> > > MSI (s) (B00): Product Code from property table after transforms:
>> > > '{6B36DEBF-27D0-4B1E-858D-D397091C6C7D}'
>> > > MSI (s) (B00): Product registered: entering maintenance mode
>> > > MSI (s) (B00): Using cached product context: machine assigned for
>> > product:
>> > > FBED63B60D72E1B458D83D7990C1C6D7
>> > > MSI (s) (B00): Using cached product context: machine assigned for
>> > product:
>> > > FBED63B60D72E1B458D83D7990C1C6D7
>> > > MSI (s) (B00): 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) (B00): 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" <(E-Mail Removed)> a écrit dans le message de
>> > > news:(E-Mail Removed)...
>> > > > 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.
>> > > >
>> > >
>> > >
>> >
>> >

>>
>>

>
>



 
Reply With Quote
 
 
 
 
Carolyn Napier [MSFT]
Guest
Posts: n/a
 
      17th Jan 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>

"nsperry" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> 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" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed)...
>> 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" <(E-Mail Removed) <private.php?do=newpm&u=>> a écrit dans le message
>> de <news:%(E-Mail Removed)>...> 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" <(E-Mail Removed)

>> <private.php?do=newpm&u=>> wrote in message
>> > news:ulGJ#(E-Mail Removed) <news:ulGJ>...
>> > > 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."
>> > >

>> ...
>>
>> > > Is there a mean to know clearly why does this 1625 error occur ?
>> > >
>> > > Thanks
>> > >
>> > >
>> > > "nsperry" <(E-Mail Removed) <private.php?do=newpm&u=>> a écrit dans le

>> message de
>> > > <news:(E-Mail Removed)>...
>> > > > 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/de...-us/msi/setup/
>> m>
>> > > > achine_policies.asp and see if any of these policies are set.
>> > > >
>> > > > N
>> > > >
>> > > > "Jean-Francois Becan" <(E-Mail Removed)

> <private.php?do=newpm&u=>>
>> wrote in message
>> > > > news:#(E-Mail Removed) <news:>...
>> > > > > 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.

>> ...
>>
>>

>
>



 
Reply With Quote
 
New Member
Join Date: Jan 2009
Posts: 23
 
      27th Feb 2009
InstEd is a free MSI editor from www.instedit.com
 
Reply With Quote
 
 
 
Reply

Thread Tools
Rate This Thread
Rate This Thread:

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off


Similar Threads
Thread Thread Starter Forum Replies Last Post
Reinstallation problem John Windows XP Performance 1 1st Sep 2004 11:27 PM
XP Home Reinstallation Problem Alberto Windows XP Help 1 11th Jun 2004 06:26 PM
Problem after reinstallation =?Utf-8?B?RGFpaWt1bg==?= Windows XP Help 7 21st Mar 2004 12:05 AM
XP Reinstallation problem. h@n Windows XP General 1 11th Nov 2003 04:45 PM
reinstallation problem PaulM Windows XP General 1 2nd Aug 2003 11:28 PM


Features
 

Advertising
 

Newsgroups
 


All times are GMT +1. The time now is 03:25 AM.