ICE Errors when validting package
Hello,
I am trying to deploy Adobe Acrobat 6 Elements through Group Policy. When trying to add the package I get the error that i need to validate this package. I vaildate with ORCA and get a slew of ICE64 and ICE79 Errors. I tried to fix the ICE64 errors by adding the folders in question to the REMOVE FILES Table, but ended getting a number of ICE03 errors because of it. Does anyone have any suggestions on how to fix these two types of validation errors; if more information is needed please let me know.
Thanks
Stan
I am trying to deploy Adobe Acrobat 6 Elements through Group Policy. When trying to add the package I get the error that i need to validate this package. I vaildate with ORCA and get a slew of ICE64 and ICE79 Errors. I tried to fix the ICE64 errors by adding the folders in question to the REMOVE FILES Table, but ended getting a number of ICE03 errors because of it. Does anyone have any suggestions on how to fix these two types of validation errors; if more information is needed please let me know.
Thanks
Stan
0 Comments
[ + ] Show comments
Answers (7)
Please log in to answer
Posted by:
nheim
16 years ago
Hi Stan,
normally an ICE64 shouldn't be a no go, but a ICE64 definitely is.
You need to log the GPO adding . Have a look at the log file then.
Regards, Nick
normally an ICE64 shouldn't be a no go, but a ICE64 definitely is.
You need to log the GPO adding . Have a look at the log file then.
Regards, Nick
Posted by:
Stanimosity
16 years ago
By the second ICE64, did you mean an ICE79. How would i log the GPO adding.
Thanks
Stan
Thanks
Stan
Posted by:
nheim
16 years ago
Hi Stan,
yes, of course i meant ICE79.
See: http://itninja.com/question/what-is-pxe?3
The log file go to your profiles temp folder.
Regards, Nick
yes, of course i meant ICE79.
See: http://itninja.com/question/what-is-pxe?3
The log file go to your profiles temp folder.
Regards, Nick
Posted by:
Inabus
16 years ago
If your getting 03's by fixing the 64's then your not populating the tables correctly, read the sdk to find out the correct information to put in that table.
FileKey Component_ FileName DirProperty InstallMode
Directly from the SDK....
FileKey
Primary key used to identify this particular table entry.
Component_
External key the first column of the Component table. This field references the component that controls the file to be removed.
FileName
This column contains the localizable name of the file to be removed. If this column is null, then the specified folder will be removed if it is empty. All of the files that match the wildcard will be removed from the specified directory.
DirProperty
Name of a property whose value is assumed to resolve to the full path to the folder of the file to be removed. The property can be the name of a directory in the Directory table, a property set by the AppSearch table, or any other property that represents a full path.
InstallMode
Must be one of the following values.
1 - Remove only when the associated component is being installed (msiInstallStateLocal or msiInstallStateSource).
2 - Remove only when the associated component is being removed (msiInstallStateAbsent).
3 - Remove in either of the above cases.
Paul
FileKey Component_ FileName DirProperty InstallMode
Directly from the SDK....
FileKey
Primary key used to identify this particular table entry.
Component_
External key the first column of the Component table. This field references the component that controls the file to be removed.
FileName
This column contains the localizable name of the file to be removed. If this column is null, then the specified folder will be removed if it is empty. All of the files that match the wildcard will be removed from the specified directory.
DirProperty
Name of a property whose value is assumed to resolve to the full path to the folder of the file to be removed. The property can be the name of a directory in the Directory table, a property set by the AppSearch table, or any other property that represents a full path.
InstallMode
Must be one of the following values.
1 - Remove only when the associated component is being installed (msiInstallStateLocal or msiInstallStateSource).
2 - Remove only when the associated component is being removed (msiInstallStateAbsent).
3 - Remove in either of the above cases.
Paul
Posted by:
Stanimosity
16 years ago
I think my problem is here
***Component_
External key the first column of the Component table. This field references the component that controls the file to be removed.***
there does not appear to be component in the component table that controls the field to be removed.
Is there a generic Component that i can put in there?
Thanks
Stan
***Component_
External key the first column of the Component table. This field references the component that controls the file to be removed.***
there does not appear to be component in the component table that controls the field to be removed.
Is there a generic Component that i can put in there?
Thanks
Stan
Posted by:
Inabus
16 years ago
I am assuming that the directory your trying to remove on uninstall has files in it on install, set the component entry to point to one of those files.
Paul
Paul
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.