Hi all

I have a package for Microsoft Office 2003 Primary Interoperabilities it is a nitive windows msi, I need to deploy this via Group Policy for my client however everytime I go to add it as a package I get the following error:

"Add operation failed: unable to extract deployment information........"

After doing some google searching I found a few links which gave some ideas so I have checked, the language of the MSI using Orca and that is all fine it only has 1033 which is the default English language.

I have updated my GPMC addin to be the latest one available. I'm using Windows Server 2003 with the latest service pack.
I have tried adding the package on a different domain and get the same problem so I know its not a domain specific issue.

I've run the pacakge through WISE Package Studio 7SP2 to validate it and everything came back ok, so i am at a loss as to why group policy wont add this pacakge.

Any help would be appreciated.
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
Did you set the GP to ignore the language?

Properties/Deployment/Advanced/Ignore language when deployingthis package
Answered 01/09/2009 by: VBScab
Red Belt

Please log in to comment
0
Wasn't able to get even that far, as the package wont add to the group policy, all I get is the "Add operation failed: unable to extract deployment information....." error and thats it, no other dialog boxes show up after that.

I look through the list of software that is deployed via this policy and the app I am trying to add doesn't appear in the list.
Answered 01/11/2009 by: smallbytes
Senior Yellow Belt

Please log in to comment
0
Are there any network drives or UNCs being pointed to in the MSI? Unlikely, I know, since you say it's the native MSI but, it's not unknown for WPS to add tables to MSIs.

EDIT:
I just tried this, as both a machine-based and user-based package and got the same error in both scenarios.

In the Event Viewer, I got:
Product: Microsoft Office 2003 Primary Interop Assemblies -- Microsoft Office 2003 Primary Interop Assemblies can not be installed with the ADVERTISE action.

Clearly, this is where to begin your investigation. Does the package install silently when run stand-alone, i.e. with GP in the way?
Answered 01/12/2009 by: VBScab
Red Belt

Please log in to comment
0
OK, a bit more digging and we find this in the LaunchCondition table:

"ACTION~<>"ADVERTISE"","[ProductName] can not be installed with the ADVERTISE action."

Simply add an impossible-to-meet condition (e.g. 0=1) to this LC via a transform, which you'll obviously need to add to the GP and you should be in business.
Answered 01/12/2009 by: VBScab
Red Belt

Please log in to comment
0
Thanks VB I will give that a try and see how it goes and post back the result
Answered 01/14/2009 by: smallbytes
Senior Yellow Belt

Please log in to comment
0
Well tried what you suggested VB I added a 0=1 condition to that LC and I still got the same error when adding to GP and the event viewer shows the same message that you got.

I can run the package silently from a command line using the standard switches.

Am starting to think Microsoft don't want this package deployed via GP for some reason :)
Answered 01/14/2009 by: smallbytes
Senior Yellow Belt

Please log in to comment
0
I was able to reproduce that scenario exactly. Bizarre! To get the packaged added, I had to remove the LC altogether.

Here we have amply demonstrated one of the few occasions where direct editing of a vendor MSI is the only solution to a problem. FWIW, I ensured we had a back-up copy of the MSI.

BTW, I haven't tested a deployment, as I have other projects to get done today. I can't see why it wouldn't work, though.
Answered 01/15/2009 by: VBScab
Red Belt

Please log in to comment
0
I opened the Office 2003 Primary Interop Assemblies MSI file in Orca 3.1.4000.1830, dropped the ACTION~<>"ADVERTISE" launch condition, saved the modified MSI as a new file and I was able to publish the modified MSI file in a Group Policy Object. But when I try to install the published package, I get a "Error 2356. An internal error has occurred. (PIA.CAB)" message and the installation fails. Does anybody know what I can do to make this work? This is a requisite installation to go with other software I want to deploy in our organization. Thank you in advance for any and all help that anybody could provide.
Answered 05/11/2011 by: raynebc
Yellow Belt

Please log in to comment
0
Normal practice is to never edit vendor-supplied MSIs. Rather, you should use a transform to apply changes. Also, I bet by "dropping" the CA, you mean you deleted the row in the CustomAction table? There's your mistake. There will be an entry for that CA in the InstallExecuteSequence table.

Go back to the back-up you took of the MSI and use Orca to create a transform, in which you add an impossible-to-meet condition for the CA in the InstallExecuteSequence table.
Answered 05/12/2011 by: VBScab
Red Belt

Please log in to comment
0
Your previous post said the transform didn't work and you concluded that directly editing the original MSI was necessary. Is this no longer your stance for this particular installation package? I can only add it to a group policy with a transform if it will accept the MSI file itself, and at this point it refuses as long as that launch condition is there. Can I create a transform as you suggest, and pre-apply it to the original MSI to create a modified MSI file to deploy?
Answered 05/12/2011 by: raynebc
Yellow Belt

Please log in to comment
1

I was getting this; was because I was accessing the .MSI from a local drive in an RDP session.  Copied the file somewhere where the group policy management could access it properly and it started working!  Rookie error perhaps, but the message isn't exactly helpful!

Answered 07/13/2012 by: anwarmahmood
White Belt

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