Gidday All,

We have an app that has been packaged successfully. But when we deploy using GP we are unable to associate the GPO with the package.

The error we get:
Unable to extract deployment information from the package. Run validation on the package to ensure that the package is correct.

What is showing up is validation errors in the extensions table. Why would the AD GPO be trying to assess this?

Has anyone got this error before.

Any help appreciated.

0 Comments   [ - ] Hide 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.
Answer this question or Comment on this question for clarity


I have had this issue and turned out that the server just needed to have the windows installer upgraded to 3.1. In my case I just installed SP1 onto my 2003 server.

Hope that helps.

Answered 06/08/2007 by: l3igh
Senior Yellow Belt

Please log in to comment
Thanks Leigh,

I'm not at work now, but I'll check that out on Tuesday.

I got around the problem by doing two things (although I consider it a workaround rather than a fix).

1) I did another snapshot of the app install, without using WPS Smartmonitor and also opening the gui interface for the SanDisk e200 and transferred a file into the device during the install.

2) This also gave me validation errors in the extensions table (ice19's incorrect progID's) deleting all the entries in the extensions table (not just the invalid ones) allowed me to connect the GPO with the package. Very interesting...

Still don't know why the AD attribute was not allowing me to connect to the package, I wouldn't have thought the AD would delve into the object (package) itself, maybe someone could point me towards an explanation?

I'm used to working in SMS, not GP deploy. Still getting my head around this part in my new job [8D]

Answered 06/08/2007 by: WayneB
Blue Belt

Please log in to comment
If I remember correct there are some requirements for an MSI package to be added to a GPO.
One of them I think was that the required advertise tables must be present so that the package can be Assigned or Published when you add it to the GPO.
Answered 06/08/2007 by: AngelD
Red Belt

Please log in to comment