[gptalk] Re: Error Deploying .MSI
- From: Thorbjörn Sjövold <thorbjorn.sjovold@xxxxxxxxxxxxxxx>
- To: <gptalk@xxxxxxxxxxxxx>
- Date: Tue, 7 Nov 2006 17:33:20 +0100
Strange, if it actually is a version problem of Windows Installer it should
really be the other way around AFAIR, e.g. a computer with Windows Installer
3.0 should be able to handle a older version MSI schema but not the other way
around and W2K3 (with SP1) have Windows Installer 3.1 installed automatically
so it should be on the top of the food chain. Anyway I still believe that your
problem boils down to an error when the Advertisement sequence is run during
aas file creation, but in this case it is not that the actual sequence that is
blocked, but rather something else.
1) Could you check the event log after you try to add the application, I think
that Windows Installer is logging the actual error, hopefully without having to
enable verbose logging, look for MsiInstaller as the Source since it would be
the Windows Installer API that throws an error.
2) Could it be that the product is already installed on the W2K3 computer, this
could also cause the Advertisement sequence to fail and resulting in this type
of problem.
Best,
Thorbjörn Sjövold
Special Operations Software
www.specopssoft.com
thorbjorn.sjovold a t specopssoft.com
Download our free tool for remote Gpupdate with graphical reporting,
http://www.specopssoft.com/products/specopsgpupdate/default.asp
________________________________
From: gptalk-bounce@xxxxxxxxxxxxx [mailto:gptalk-bounce@xxxxxxxxxxxxx] On
Behalf Of Attardo, Joe
Sent: Tuesday, November 07, 2006 3:52 PM
To: gptalk@xxxxxxxxxxxxx
Subject: [gptalk] Re: Error Deploying .MSI
It is a home grown package, and the only one causing grief from a 2K3 DC. If I
log on to a 2K DC, I can create the policy with no issues.
-----Original Message-----
From: gptalk-bounce@xxxxxxxxxxxxx [mailto:gptalk-bounce@xxxxxxxxxxxxx]
On Behalf Of Thorbjörn Sjövold
Sent: Tuesday, November 07, 2006 3:13 AM
To: gptalk@xxxxxxxxxxxxx
Subject: [gptalk] Re: Error Deploying .MSI
Joe,
my guess is that this package does not have the proper advertising
tables, or even worse advertising is disabled all together in the the MSI. Is
it a home grown package or something public? When you add a package the *.aas
file is created using the Windows Installer APIs and they rely on the
information in the Advertising sequence. Is this the only package that behaves
like this?
Best,
Thorbjörn Sjövold
Special Operations Software
www.specopssoft.com
thorbjorn.sjovold a t specopssoft.com
Download our free tool for remote Gpupdate with graphical reporting,
http://www.specopssoft.com/products/specopsgpupdate/default.asp
________________________________
From: gptalk-bounce@xxxxxxxxxxxxx [mailto:gptalk-bounce@xxxxxxxxxxxxx]
On Behalf Of Darren Mar-Elia
Sent: Monday, November 06, 2006 8:16 PM
To: gptalk@xxxxxxxxxxxxx
Subject: [gptalk] Re: Error Deploying .MSI
Different MSI versions could definitely cause it. You might want to
enable verbose software deployment logging (see my gpolog.adm for this) and see
what messages are being thrown there.
Darren
________________________________
From: gptalk-bounce@xxxxxxxxxxxxx [mailto:gptalk-bounce@xxxxxxxxxxxxx]
On Behalf Of Attardo, Joe
Sent: Monday, November 06, 2006 9:44 AM
To: gptalk@xxxxxxxxxxxxx
Subject: [gptalk] Error Deploying .MSI
I a receive the following error while trying to add a new policy for
deploying a software package. The DC is a 2K3 server. I am able to do this when
logged onto a Win2K DC without error.
Add Operation Failed. Unable to extract deployment information from the
package. Run validation on the package to ensure that the package is correct.
Would this be a result of different versions of Windows Installer?
Thanks
Joe
Other related posts:
