Hi all,


I am trying to add a vendor supplied MSI to a Group Policy for deployment via AD.

When I add it, it throws the following error:
"Add operation failed. Unable to extract deployment information from the package. Run validation on the package to ensure that the package is correct."

I have looked over the forums and scoured the web.
The three things that I found were

1.) Wrong version of the Installer service on the server.

Not the case. Win2k3 running Installer v.2

2.) Not enough room on the sysvol

FAQ 6944

http://www.jsiinc.com/SUBN/tip6900/rh6944.htm

Not the case, as I can add other packages and create new Policies.

3.) Property in MSI requiring setup.exe (ISSETUPDRIVEN) or similar feature.

Not there or anything similar.

The Installshield package, although it probably doesn't matter is Lawson's Microsoft Office Add-ins 1.0.10.
What is weird is that I have successfully added and deployed version 1.0.9.1. now I just need to upgrade it.

When I run validation against the MSI, do get a lot of errors stating that things are used in incorrect ways, etc. Mostly related to redistributable controls.

Anyone have any ideas on where else to look?

Thanks.
Nate
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Rating comments in this legacy AppDeploy message board thread won't reorder them,
so that the conversation will remain readable.

Answers

0
If you use DFS, make sure that the source package has properly replicated to all sites.
Answered 11/19/2004 by: cdupuis
Third Degree Green Belt

Please log in to comment
0
I do use DFS and the package has been replicated to all DFS links.

Thanks.
Nate
Answered 11/19/2004 by: nmead
Senior Yellow Belt

Please log in to comment
0
That is typically the cause for when i get such messages. Try making a new policy and adding it to that policy and see what happens, it may be the policy you are adding into.
Answered 11/19/2004 by: cdupuis
Third Degree Green Belt

Please log in to comment
0
Tried that as well. I deleted the existing GPO. Created a new Object named something completely different, gave it time to replicate and tried adding the package.
Unfortunately, I got the same error.

Thanks.
Nate
Answered 11/19/2004 by: nmead
Senior Yellow Belt

Please log in to comment
0
Map a drive to the DFS link and try it that way.
Answered 11/19/2004 by: MSIMaker
Second Degree Black Belt

Please log in to comment
0
I've seen this occur when the computer I was using to add it from already had the MSI in question installed. The fix was to either uninstall the MSI from the machine you are using to run the MMC snap-in, or to simply jump over to another machine and add it from there.

Hope this helps,
Bob
Answered 11/20/2004 by: bkelly
Red Belt

Please log in to comment
0
simply jump over to another machine and add it from there.

Specifically what Bob is talking about is installing the adminpak.msi on a workstation, running Active Directory Users and Computers from it, and adding the package that way. I have found this to be the most sure fire way to get around this issue. It saves alot of footsteps or keystrokes too, since you don't have to go to the server or remote into it.

I have seen this message many times when WinZip is installed on a server, and WinZip is being added as a package. Un-installing WinZip from the server usually doesn't even do the trick.


Craig --<>.
Answered 11/21/2004 by: craig16229
Third Degree Brown Belt

Please log in to comment
0
I am doing this from my workstation, XP SP2 With Admin Tools and GPMC installed.
I do not have the package(or the version of it) in question installed on my PC.

I have tried this from server consoles as well, though.

Thanks.
Nate
Answered 11/21/2004 by: nmead
Senior Yellow Belt

Please log in to comment
0
What is the behavior of the .msi if installed via command line?


Craig --<>.
Answered 11/22/2004 by: craig16229
Third Degree Brown Belt

Please log in to comment
0
The package installs correctly via command-line with and without my mst.


Thanks,
Nate
Answered 11/22/2004 by: nmead
Senior Yellow Belt

Please log in to comment
0
I've seen some of my repackaged MSI's install OK from command line, but then when I try to add to a GPO, it fails. I found that it put an entry in the application event viewer - eg. W:\ is not a valid drive, which indicated a rogue property defined in the MSI.

May be a red herring tho...

Ian E
Answered 11/23/2004 by: IanE
Senior Yellow Belt

Please log in to comment
Answer this question or Comment on this question for clarity