HKCU healing in Acrobat 6 Pro
Got a weird problem here...
I've created a transform for AcroPro 6 to basically insert CU reg settings, covering preferences and the like. Now, I know the way MSI healing works is that only components within the feature that has the advertised shortcut are checked to see if they need fixing, and this isn't a problem...I just create a new component with my CU settings, assign a keypath regkey, and put it in the parent feature.
However, when I log on as a user and run the shortcut I get a "You do not have sufficient privileges to run this installer. Setup will now terminate." error, and then "Fatal error during installation", and it doesn't even load the app, let alone install the CU component.
This has me puzzled as I've used this method on other vendor provided MSIs before with no probs...the HKCU key is completely open to Users here, so that can't be it. Even opening up the C drive didn't help. Any idea what it's trying to write??
Thanks in advance. [:)]
I've created a transform for AcroPro 6 to basically insert CU reg settings, covering preferences and the like. Now, I know the way MSI healing works is that only components within the feature that has the advertised shortcut are checked to see if they need fixing, and this isn't a problem...I just create a new component with my CU settings, assign a keypath regkey, and put it in the parent feature.
However, when I log on as a user and run the shortcut I get a "You do not have sufficient privileges to run this installer. Setup will now terminate." error, and then "Fatal error during installation", and it doesn't even load the app, let alone install the CU component.
This has me puzzled as I've used this method on other vendor provided MSIs before with no probs...the HKCU key is completely open to Users here, so that can't be it. Even opening up the C drive didn't help. Any idea what it's trying to write??
Thanks in advance. [:)]
0 Comments
[ + ] Show comments
Answers (3)
Please log in to answer
Posted by:
MSIMaker
20 years ago
Acrobat has a few Installshield custom actions that run to check if the user is an Admin or not and generates the Installer error. Look in the Custom Actions for conditions marked Is_Priviledged.
Posted by:
mickman
20 years ago
Has the file been installed before on that client and never been uninstalled? Then these errors can arise.
Posted by:
ianwil1976
20 years ago
Thanks guys, we actually decided to just go via login script in the end! Saves me grief! [;)]
Jim, that custom action wasn't present, just FYI.
Cheers,
Ian
Jim, that custom action wasn't present, just FYI.
Cheers,
Ian
Rating comments in this legacy AppDeploy message board thread won't reorder them,so that the conversation will remain readable.