Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
Error 1605 with Group Policy install of msi
773 views
Skip to first unread message
Anthony Yates
Jan 20, 2006, 11:10:29 AM1/20/06
to
I have an msi that installs succesfully when you run it manually, but gives
an error when installed by Group Policy. The error is: "This action is only
valid for products that are currently installed". I get it even on an
entirely clean machine.
Can you think why I would get this with a Group Policy install but not
manually? How would I trace it? The error happens right at the start of the
Group Policy install. If I run the msi in debugger it completes without
error.
Any ideas?
Thanks
an error when installed by Group Policy. The error is: "This action is only
valid for products that are currently installed". I get it even on an
entirely clean machine.
Can you think why I would get this with a Group Policy install but not
manually? How would I trace it? The error happens right at the start of the
Group Policy install. If I run the msi in debugger it completes without
error.
Any ideas?
Thanks
Phil Wilson
Jan 20, 2006, 2:36:41 PM1/20/06
to
That's the exact message you get when you try to uninstall something! Odd.
Sure you're really trying to install, and not repair or uninstall or
something?
--
Phil Wilson [MVP Windows Installer]
----
"Anthony Yates" <anthon...@nospam.com> wrote in message
news:eIetEwd...@TK2MSFTNGP11.phx.gbl...
Sure you're really trying to install, and not repair or uninstall or
something?
--
Phil Wilson [MVP Windows Installer]
----
"Anthony Yates" <anthon...@nospam.com> wrote in message
news:eIetEwd...@TK2MSFTNGP11.phx.gbl...
Anthony Yates
Jan 23, 2006, 5:14:44 AM1/23/06
to
Absolutely sure. It happens on a new build. The product is Nero. The fault
happens right at the start of installation, but I can't tell what action or
property is causing it.
happens right at the start of installation, but I can't tell what action or
property is causing it.
"Phil Wilson" <Phil....@unisys.spamcom> wrote in message
news:OeCwXjfH...@TK2MSFTNGP11.phx.gbl...
Dennis Bareis
Jan 25, 2006, 4:56:41 PM1/25/06
to
Hi,
On Mon, 23 Jan 2006 10:14:44 -0000, "Anthony Yates" <anthon...@spammedout.com> wrote:
>Absolutely sure. It happens on a new build. The product is Nero. The fault
>happens right at the start of installation, but I can't tell what action or
>property is causing it.
You'll have to turn on the Windowws Installer policies for verbose logging an examine the generated logs.
Bye,
Dennis
Dennis Bareis [MVP] (den...@KillSpam.dennisbareis.id.au)
http://dennisbareis.id.au/index.htm
Freeware Windows Installer creation tool (+ "ORCA automation"):
http://dennisbareis.id.au/makemsi.htm
Bugbear.1973
Jan 27, 2006, 2:37:44 AM1/27/06
to
I would suggest inspecting your clean machine (before attempting to
install Nero), to verify that it truly does not contain any traces of
Nero. Suggest searching the registry for "Nero" or perhaps the
ProductCode of your Nero msi.
install Nero), to verify that it truly does not contain any traces of
Nero. Suggest searching the registry for "Nero" or perhaps the
ProductCode of your Nero msi.
Anthony Yates
Jan 27, 2006, 7:03:57 AM1/27/06
to
Thanks,
I have verbose logging on but could not see the step at which this occured.
I might try again
I have verbose logging on but could not see the step at which this occured.
I might try again
"Dennis Bareis" <dba...@newsgroup.nospam> wrote in message
news:2usft1t4n89ha1q61...@4ax.com...
Anthony Yates
Jan 27, 2006, 7:05:27 AM1/27/06
to
Thanks,
It is a clean machine, as in just rebuilt.
It is a clean machine, as in just rebuilt.
"Bugbear.1973" <bugbea...@gmail.com> wrote in message
news:1138347464.5...@g47g2000cwa.googlegroups.com...
Anthony Yates
Jan 27, 2006, 7:12:46 AM1/27/06
to
Nero is a slightly odd msi. It is a load of custom actions, calling what
seems to be a number of dll's created to handle the installation. I have a
slight idea that what is happening is:
- The installation runs to copy files and registry keys etc as normal
- Then a Part Two happens, which sets up file associations and shortcuts
based on the features you selected. This part is exactly the same as when
you use one of the shortcuts after installation to change the Nero
configuration. I suspect this part is set to happen in Repair mode.
- For some reason as a user running the setup you are able to move on past
the 1605 error, but the Group Policy installation can't.
This is just a complete guess, but it is based on seeing the same 1605 error
in the successful manual installation log.
Does anyone know if it would be possible to construct an msi like that?
seems to be a number of dll's created to handle the installation. I have a
slight idea that what is happening is:
- The installation runs to copy files and registry keys etc as normal
- Then a Part Two happens, which sets up file associations and shortcuts
based on the features you selected. This part is exactly the same as when
you use one of the shortcuts after installation to change the Nero
configuration. I suspect this part is set to happen in Repair mode.
- For some reason as a user running the setup you are able to move on past
the 1605 error, but the Group Policy installation can't.
This is just a complete guess, but it is based on seeing the same 1605 error
in the successful manual installation log.
Does anyone know if it would be possible to construct an msi like that?
"Phil Wilson" <Phil....@unisys.spamcom> wrote in message
news:OeCwXjfH...@TK2MSFTNGP11.phx.gbl...
Anthony Yates
Jan 30, 2006, 8:34:02 AM1/30/06
to
I have checked the logs again. I have three separate log files:
Extracts below. The first and third process are executing the same msi, with
slightly different results. The middle process generates the 1605 error.
====================================================================
MSI (c) (4C:D0) [13:05:26:353]: User policy value 'DisableRollback' is 0
MSI (c) (4C:D0) [13:05:26:353]: Machine policy value 'DisableRollback' is 0
MSI (c) (4C:D0) [13:05:26:368]: Executing op:
Header(Signature=1397708873,Version=301,Timestamp=875854617,LangId=1033,Platform=0,ScriptType=3,ScriptMajorVersion=21,ScriptMinorVersion=4,ScriptAttributes=0)
MSI (c) (4C:D0) [13:05:26:368]: Executing op:
ProductInfo(ProductKey={C93369CB-B4E9-E095-9289-E6B5AE941033},ProductName=Nero
7,PackageName=Nero.msi,Language=1033,Version=117443246,Assignment=1,ObsoleteArg=0,ProductIcon=ARPPRODUCTICON.exe,,PackageCode={29101F0A-9817-7D92-E4F6-9CE6197F1C5B},,,InstanceType=0,LUASetting=0,RemoteURTInstalls=0)
==================================================================
=== Verbose logging started: 30/01/2006 13:05:27 Build type: SHIP UNICODE
3.01.4000.2435 Calling process: \??\C:\WINDOWS\system32\winlogon.exe ===
MSI (c) (4C:FC) [13:05:27:431]: Resetting cached policy values
MSI (c) (4C:FC) [13:05:27:431]: Machine policy value 'Debug' is 0
MSI (c) (4C:FC) [13:05:27:431]: ******* RunEngine:
******* Product: {c93369cb-b4e9-e095-9289-e6b5ae94fa5f}
******* Action:
******* CommandLine: **********
MSI (c) (4C:FC) [13:05:27:446]: Client-side and UI is none or basic: Running
entire install on the server.
MSI (c) (4C:FC) [13:05:27:446]: Grabbed execution mutex.
MSI (c) (4C:FC) [13:05:27:539]: Cloaking enabled.
MSI (c) (4C:FC) [13:05:27:539]: Attempting to enable all disabled priveleges
before calling Install on Server
MSI (c) (4C:FC) [13:05:27:554]: Incrementing counter to disable shutdown.
Counter after increment: 0
MSI (s) (28:44) [13:05:27:569]: Grabbed execution mutex.
MSI (s) (28:48) [13:05:27:569]: Resetting cached policy values
MSI (s) (28:48) [13:05:27:569]: Machine policy value 'Debug' is 0
MSI (s) (28:48) [13:05:27:569]: ******* RunEngine:
******* Product: {c93369cb-b4e9-e095-9289-e6b5ae94fa5f}
******* Action:
******* CommandLine: **********
MSI (s) (28:48) [13:05:27:569]: Machine policy value 'DisableUserInstalls'
is 0
MSI (s) (28:48) [13:05:27:569]: MainEngineThread is returning 1605
MSI (c) (4C:FC) [13:05:27:569]: Decrementing counter to disable shutdown. If
counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (4C:FC) [13:05:27:569]: MainEngineThread is returning 1605
=== Verbose logging stopped: 30/01/2006 13:05:27 ===
=========================================================
MSI (c) (4C:D0) [13:05:27:569]: User policy value 'DisableRollback' is 0
MSI (c) (4C:D0) [13:05:27:569]: Machine policy value 'DisableRollback' is 0
MSI (c) (4C:D0) [13:05:27:569]: Executing op:
Header(Signature=1397708873,Version=301,Timestamp=875854617,LangId=1033,Platform=0,ScriptType=3,ScriptMajorVersion=21,ScriptMinorVersion=4,ScriptAttributes=0)
MSI (c) (4C:D0) [13:05:27:569]: Executing op:
ProductInfo(ProductKey={C93369CB-B4E9-E095-9289-E6B5AE941033},ProductName=Nero
7,PackageName=Nero.msi,Language=1033,Version=117443246,Assignment=1,ObsoleteArg=0,ProductIcon=ARPPRODUCTICON.exe,,PackageCode={29101F0A-9817-7D92-E4F6-9CE6197F1C5B},,,InstanceType=0,LUASetting=0,RemoteURTInstalls=0)
MSI (c) (4C:D0) [13:05:27:569]: Executing op:
DialogInfo(Type=0,Argument=1033)
MSI (c) (4C:D0) [13:05:27:569]: Executing op:
DialogInfo(Type=1,Argument=Nero 7)
MSI (c) (4C:D0) [13:05:27:569]: Executing op:
RollbackInfo(,RollbackAction=Rollback,RollbackDescription=Rolling back
action:,RollbackTemplate=[1],CleanupAction=RollbackCleanup,CleanupDescription=Removing
backup files,CleanupTemplate=File: [1])
MSI (c) (4C:D0) [13:05:27:569]: Executing op:
ActionStart(Name=PublishFeatures,Description=Publishing Product
Features,Template=Feature: [1])
=========================================================
Extracts below. The first and third process are executing the same msi, with
slightly different results. The middle process generates the 1605 error.
====================================================================
MSI (c) (4C:D0) [13:05:26:353]: User policy value 'DisableRollback' is 0
MSI (c) (4C:D0) [13:05:26:353]: Machine policy value 'DisableRollback' is 0
MSI (c) (4C:D0) [13:05:26:368]: Executing op:
Header(Signature=1397708873,Version=301,Timestamp=875854617,LangId=1033,Platform=0,ScriptType=3,ScriptMajorVersion=21,ScriptMinorVersion=4,ScriptAttributes=0)
MSI (c) (4C:D0) [13:05:26:368]: Executing op:
ProductInfo(ProductKey={C93369CB-B4E9-E095-9289-E6B5AE941033},ProductName=Nero
7,PackageName=Nero.msi,Language=1033,Version=117443246,Assignment=1,ObsoleteArg=0,ProductIcon=ARPPRODUCTICON.exe,,PackageCode={29101F0A-9817-7D92-E4F6-9CE6197F1C5B},,,InstanceType=0,LUASetting=0,RemoteURTInstalls=0)
==================================================================
=== Verbose logging started: 30/01/2006 13:05:27 Build type: SHIP UNICODE
3.01.4000.2435 Calling process: \??\C:\WINDOWS\system32\winlogon.exe ===
MSI (c) (4C:FC) [13:05:27:431]: Resetting cached policy values
MSI (c) (4C:FC) [13:05:27:431]: Machine policy value 'Debug' is 0
MSI (c) (4C:FC) [13:05:27:431]: ******* RunEngine:
******* Product: {c93369cb-b4e9-e095-9289-e6b5ae94fa5f}
******* Action:
******* CommandLine: **********
MSI (c) (4C:FC) [13:05:27:446]: Client-side and UI is none or basic: Running
entire install on the server.
MSI (c) (4C:FC) [13:05:27:446]: Grabbed execution mutex.
MSI (c) (4C:FC) [13:05:27:539]: Cloaking enabled.
MSI (c) (4C:FC) [13:05:27:539]: Attempting to enable all disabled priveleges
before calling Install on Server
MSI (c) (4C:FC) [13:05:27:554]: Incrementing counter to disable shutdown.
Counter after increment: 0
MSI (s) (28:44) [13:05:27:569]: Grabbed execution mutex.
MSI (s) (28:48) [13:05:27:569]: Resetting cached policy values
MSI (s) (28:48) [13:05:27:569]: Machine policy value 'Debug' is 0
MSI (s) (28:48) [13:05:27:569]: ******* RunEngine:
******* Product: {c93369cb-b4e9-e095-9289-e6b5ae94fa5f}
******* Action:
******* CommandLine: **********
MSI (s) (28:48) [13:05:27:569]: Machine policy value 'DisableUserInstalls'
is 0
MSI (s) (28:48) [13:05:27:569]: MainEngineThread is returning 1605
MSI (c) (4C:FC) [13:05:27:569]: Decrementing counter to disable shutdown. If
counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (4C:FC) [13:05:27:569]: MainEngineThread is returning 1605
=== Verbose logging stopped: 30/01/2006 13:05:27 ===
=========================================================
MSI (c) (4C:D0) [13:05:27:569]: User policy value 'DisableRollback' is 0
MSI (c) (4C:D0) [13:05:27:569]: Machine policy value 'DisableRollback' is 0
MSI (c) (4C:D0) [13:05:27:569]: Executing op:
Header(Signature=1397708873,Version=301,Timestamp=875854617,LangId=1033,Platform=0,ScriptType=3,ScriptMajorVersion=21,ScriptMinorVersion=4,ScriptAttributes=0)
MSI (c) (4C:D0) [13:05:27:569]: Executing op:
ProductInfo(ProductKey={C93369CB-B4E9-E095-9289-E6B5AE941033},ProductName=Nero
7,PackageName=Nero.msi,Language=1033,Version=117443246,Assignment=1,ObsoleteArg=0,ProductIcon=ARPPRODUCTICON.exe,,PackageCode={29101F0A-9817-7D92-E4F6-9CE6197F1C5B},,,InstanceType=0,LUASetting=0,RemoteURTInstalls=0)
MSI (c) (4C:D0) [13:05:27:569]: Executing op:
DialogInfo(Type=0,Argument=1033)
MSI (c) (4C:D0) [13:05:27:569]: Executing op:
DialogInfo(Type=1,Argument=Nero 7)
MSI (c) (4C:D0) [13:05:27:569]: Executing op:
RollbackInfo(,RollbackAction=Rollback,RollbackDescription=Rolling back
action:,RollbackTemplate=[1],CleanupAction=RollbackCleanup,CleanupDescription=Removing
backup files,CleanupTemplate=File: [1])
MSI (c) (4C:D0) [13:05:27:569]: Executing op:
ActionStart(Name=PublishFeatures,Description=Publishing Product
Features,Template=Feature: [1])
=========================================================
Any ideas what it means and if I can get around the error?
Thanks,
Anthony
"Anthony Yates" <anthon...@nospam.com> wrote in message
news:eV6S9mzI...@TK2MSFTNGP11.phx.gbl...
0 new messages