After installing this update I am no longer able to uninstall Adobe Acrobat reader 8.1.2 I receive an "Error applying transforms. Verify that the specified transform paths are valid"

I have traced this down to a specific registry key:

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Installer\Products\68AB67CA7DA73301B7448A2100000030]
"Transforms"=@AcroRead812.mst;C:\Program Files\Adobe\Reader 8.0\Setup Files\{AC76BA86-7AD7-1033-7B44-A81200000003}\RdrSU.mst

The update is appending on the part after the semicolon. If I remove everything after the semicolon I can then uninstall Adobe Reader. How do I fix this problem? I don't want to deploy a patch to our organization that is going to prevent me from uninstalling the application if I need to.

I think I don't like Adobe products [:'(]
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
Hi Joe,
what does the logfile exactly tell you?
If you can't solve the issue, you can produce your own version of v 8.1.2SU1 quite easily.
See: http://www.appdeploy.com/messageboards/fb.asp?m=37232
It's basically the exchange of one file.
Regards, Nick
Answered 07/24/2008 by: nheim
Tenth Degree Black Belt

Please log in to comment
0
Not very much.

=== Verbose logging started: 7/24/2008 10:10:19 Build type: SHIP UNICODE 3.01.4000.4039 Calling process: C:\WINDOWS\system32\rundll32.exe ===
MSI (c) (34:C4) [10:10:19:171]: Resetting cached policy values
MSI (c) (34:C4) [10:10:19:171]: Machine policy value 'Debug' is 0
MSI (c) (34:C4) [10:10:19:171]: ******* RunEngine:
******* Product: {AC76BA86-7AD7-1033-7B44-A81200000003}
******* Action:
******* CommandLine: **********
MSI (c) (34:C4) [10:10:19:171]: Client-side and UI is none or basic: Running entire install on the server.
MSI (c) (34:C4) [10:10:19:171]: Grabbed execution mutex.
MSI (c) (34:C4) [10:10:19:187]: Cloaking enabled.
MSI (c) (34:C4) [10:10:19:187]: Attempting to enable all disabled priveleges before calling Install on Server
MSI (c) (34:C4) [10:10:19:187]: Incrementing counter to disable shutdown. Counter after increment: 0
MSI (s) (1C:3C) [10:10:19:187]: Grabbed execution mutex.
MSI (s) (1C:B0) [10:10:19:187]: Resetting cached policy values
MSI (s) (1C:B0) [10:10:19:187]: Machine policy value 'Debug' is 0
MSI (s) (1C:B0) [10:10:19:187]: ******* RunEngine:
******* Product: {AC76BA86-7AD7-1033-7B44-A81200000003}
******* Action:
******* CommandLine: **********
MSI (s) (1C:B0) [10:10:19:187]: Machine policy value 'DisableUserInstalls' is 0
MSI (s) (1C:B0) [10:10:19:187]: End dialog not enabled
MSI (s) (1C:B0) [10:10:19:187]: Original package ==> C:\WINDOWS\Installer\12b6b.msi
MSI (s) (1C:B0) [10:10:19:187]: Package we're running from ==> C:\WINDOWS\Installer\12b6b.msi
MSI (s) (1C:B0) [10:10:19:187]: APPCOMPAT: looking for appcompat database entry with ProductCode '{AC76BA86-7AD7-1033-7B44-A81200000003}'.
MSI (s) (1C:B0) [10:10:19:187]: APPCOMPAT: no matching ProductCode found in database.
MSI (s) (1C:B0) [10:10:19:203]: MSCOREE not loaded loading copy from system32
MSI (s) (1C:B0) [10:10:19:203]: Machine policy value 'DisablePatch' is 0
MSI (s) (1C:B0) [10:10:19:203]: Machine policy value 'AllowLockdownPatch' is 1
MSI (s) (1C:B0) [10:10:19:203]: Machine policy value 'DisableLUAPatching' is 0
MSI (s) (1C:B0) [10:10:19:203]: Machine policy value 'DisableFlyWeightPatching' is 0
MSI (s) (1C:B0) [10:10:19:203]: Looking for secure file transform: C:\WINDOWS\Installer\12b6c.mst
MSI (s) (1C:B0) [10:10:19:203]: Validating transform 'C:\WINDOWS\Installer\12b6c.mst' with validation bits 0
MSI (s) (1C:B0) [10:10:19:203]: Transform 'C:\WINDOWS\Installer\12b6c.mst' is valid.
MSI (s) (1C:B0) [10:10:19:203]: Note: 1: 2262 2: Patch 3: -2147287038
MSI (s) (1C:B0) [10:10:19:203]: Note: 1: 2262 2: PatchPackage 3: -2147287038
MSI (s) (1C:B0) [10:10:19:203]: Note: 1: 2262 2: Media 3: -2147287038
MSI (s) (1C:B0) [10:10:19:203]: Note: 1: 2262 2: File 3: -2147287038
MSI (s) (1C:B0) [10:10:19:203]: Note: 1: 2262 2: PatchPackage 3: -2147287038
MSI (s) (1C:B0) [10:10:19:203]: Note: 1: 2262 2: Patch 3: -2147287038
MSI (s) (1C:B0) [10:10:19:203]: TRANSFORM: 'PatchPackage' table is missing or empty. No pre-transform fixup necessary.
MSI (s) (1C:B0) [10:10:19:203]: TRANSFORM: Applying regular transform to database.
MSI (s) (1C:B0) [10:10:19:203]: Note: 1: 2262 2: ActionText 3: -2147287038
MSI (s) (1C:B0) [10:10:19:203]: Note: 1: 2262 2: AdminExecuteSequence 3: -2147287038
MSI (s) (1C:B0) [10:10:19:203]: Note: 1: 2262 2: Condition 3: -2147287038
MSI (s) (1C:B0) [10:10:19:203]: Note: 1: 2262 2: AdminUISequence 3: -2147287038
MSI (s) (1C:B0) [10:10:19:203]: Note: 1: 2262 2: AdvtExecuteSequence 3: -2147287038
MSI (s) (1C:B0) [10:10:19:203]: Note: 1: 2262 2: AdvtUISequence 3: -2147287038
MSI (s) (1C:B0) [10:10:19:203]: Note: 1: 2262 2: AppId 3: -2147287038
MSI (s) (1C:B0) [10:10:19:203]: Note: 1: 2262 2: AppSearch 3: -2147287038
MSI (s) (1C:B0) [10:10:19:203]: Note: 1: 2262 2: BBControl 3: -2147287038
MSI (s) (1C:B0) [10:10:19:203]: Note: 1: 2262 2: Billboard 3: -2147287038
MSI (s) (1C:B0) [10:10:19:203]: Note: 1: 2262 2: BindImage 3: -2147287038
MSI (s) (1C:B0) [10:10:19:203]: Note: 1: 2262 2: File 3: -2147287038
MSI (s) (1C:B0) [10:10:19:203]: Note: 1: 2262 2: CCPSearch 3: -2147287038
MSI (s) (1C:B0) [10:10:19:203]: Note: 1: 2262 2: CheckBox 3: -2147287038
MSI (s) (1C:B0) [10:10:19:203]: Note: 1: 2262 2: Class 3: -2147287038
MSI (s) (1C:B0) [10:10:19:203]: Note: 1: 2262 2: Component 3: -2147287038
MSI (s) (1C:B0) [10:10:19:203]: Note: 1: 2262 2: Icon 3: -2147287038
MSI (s) (1C:B0) [10:10:19:203]: Note: 1: 2262 2: ProgId 3: -2147287038
MSI (s) (1C:B0) [10:10:19:203]: Note: 1: 2262 2: ComboBox 3: -2147287038
MSI (s) (1C:B0) [10:10:19:203]: Note: 1: 2262 2: CompLocator 3: -2147287038
MSI (s) (1C:B0) [10:10:19:203]: Note: 1: 2262 2: Complus 3: -2147287038
MSI (s) (1C:B0) [10:10:19:203]: Note: 1: 2262 2: Directory 3: -2147287038
MSI (s) (1C:B0) [10:10:19:203]: Note: 1: 2262 2: Control 3: -2147287038
MSI (s) (1C:B0) [10:10:19:203]: Note: 1: 2262 2: Dialog 3: -2147287038
MSI (s) (1C:B0) [10:10:19:203]: Note: 1: 2262 2: ControlCondition 3: -2147287038
MSI (s) (1C:B0) [10:10:19:203]: Note: 1: 2262 2: ControlEvent 3: -2147287038
MSI (s) (1C:B0) [10:10:19:203]: Note: 1: 2262 2: CreateFolder 3: -2147287038
MSI (s) (1C:B0) [10:10:19:203]: Note: 1: 2262 2: DrLocator 3: -2147287038
MSI (s) (1C:B0) [10:10:19:203]: Note: 1: 2262 2: DuplicateFile 3: -2147287038
MSI (s) (1C:B0) [10:10:19:203]: Note: 1: 2262 2: Environment 3: -2147287038
MSI (s) (1C:B0) [10:10:19:203]: Note: 1: 2262 2: ModuleDependency 3: -2147287038
MSI (s) (1C:B0) [10:10:19:203]: Note: 1: 2262 2: Error 3: -2147287038
MSI (s) (1C:B0) [10:10:19:203]: Note: 1: 2262 2: ModuleSignature 3: -2147287038
MSI (s) (1C:B0) [10:10:19:203]: Note: 1: 2262 2: EventMapping 3: -2147287038
MSI (s) (1C:B0) [10:10:19:203]: Note: 1: 2262 2: Extension 3: -2147287038
MSI (s) (1C:B0) [10:10:19:203]: Note: 1: 2262 2: MIME 3: -2147287038
MSI (s) (1C:B0) [10:10:19:203]: Note: 1: 2262 2: FeatureComponents 3: -2147287038
MSI (s) (1C:B0) [10:10:19:203]: Note: 1: 2262 2: FileSFPCatalog 3: -2147287038
MSI (s) (1C:B0) [10:10:19:203]: Note: 1: 2262 2: SFPCatalog 3: -2147287038
MSI (s) (1C:B0) [10:10:19:203]: Note: 1: 2262 2: Font 3: -2147287038
MSI (s) (1C:B0) [10:10:19:203]: Note: 1: 2262 2: IniFile 3: -2147287038
MSI (s) (1C:B0) [10:10:19:203]: Note: 1: 2262 2: IniLocator 3: -2147287038
MSI (s) (1C:B0) [10:10:19:203]: Note: 1: 2262 2: InstallUISequence 3: -2147287038
MSI (s) (1C:B0) [10:10:19:203]: Note: 1: 2262 2: IsolatedComponent 3: -2147287038
MSI (s) (1C:B0) [10:10:19:203]: Note: 1: 2262 2: LaunchCondition 3: -2147287038
MSI (s) (1C:B0) [10:10:19:203]: Note: 1: 2262 2: ListBox 3: -2147287038
MSI (s) (1C:B0) [10:10:19:203]: Note: 1: 2262 2: ListView 3: -2147287038
MSI (s) (1C:B0) [10:10:19:203]: Note: 1: 2262 2: LockPermissions 3: -2147287038
MSI (s) (1C:B0) [10:10:19:203]: Note: 1: 2262 2: Media 3: -2147287038
MSI (s) (1C:B0) [10:10:19:203]: Note: 1: 2262 2: ModuleComponents 3: -2147287038
MSI (s) (1C:B0) [10:10:19:203]: Note: 1: 2262 2: MoveFile 3: -2147287038
MSI (s) (1C:B0) [10:10:19:203]: Note: 1: 2262 2: MsiAssembly 3: -2147287038
MSI (s) (1C:B0) [10:10:19:203]: Note: 1: 2262 2: MsiAssemblyName 3: -2147287038
MSI (s) (1C:B0) [10:10:19:203]: Note: 1: 2262 2: MsiDigitalCertificate 3: -2147287038
MSI (s) (1C:B0) [10:10:19:203]: Note: 1: 2262 2: MsiDigitalSignature 3: -2147287038
MSI (s) (1C:B0) [10:10:19:203]: Note: 1: 2262 2: MsiFileHash 3: -2147287038
MSI (s) (1C:B0) [10:10:19:203]: Note: 1: 2262 2: ODBCAttribute 3: -2147287038
MSI (s) (1C:B0) [10:10:19:203]: Note: 1: 2262 2: ODBCDriver 3: -2147287038
MSI (s) (1C:B0) [10:10:19:203]: Note: 1: 2262 2: ODBCDataSource 3: -2147287038
MSI (s) (1C:B0) [10:10:19:203]: Note: 1: 2262 2: ODBCSourceAttribute 3: -2147287038
MSI (s) (1C:B0) [10:10:19:203]: Note: 1: 2262 2: ODBCTranslator 3: -2147287038
MSI (s) (1C:B0) [10:10:19:203]: Note: 1: 2262 2: Patch 3: -2147287038
MSI (s) (1C:B0) [10:10:19:203]: Note: 1: 2262 2: PatchPackage 3: -2147287038
MSI (s) (1C:B0) [10:10:19:203]: Note: 1: 2262 2: PublishComponent 3: -2147287038
MSI (s) (1C:B0) [10:10:19:203]: Note: 1: 2262 2: RadioButton 3: -2147287038
MSI (s) (1C:B0) [10:10:19:203]: Note: 1: 2262 2: RegLocator 3: -2147287038
MSI (s) (1C:B0) [10:10:19:203]: Note: 1: 2262 2: RemoveFile 3: -2147287038
MSI (s) (1C:B0) [10:10:19:203]: Note: 1: 2262 2: RemoveIniFile 3: -2147287038
MSI (s) (1C:B0) [10:10:19:203]: Note: 1: 2262 2: RemoveRegistry 3: -2147287038
MSI (s) (1C:B0) [10:10:19:203]: Note: 1: 2262 2: ReserveCost 3: -2147287038
MSI (s) (1C:B0) [10:10:19:203]: Note: 1: 2262 2: SelfReg 3: -2147287038
MSI (s) (1C:B0) [10:10:19:203]: Note: 1: 2262 2: ServiceControl 3: -2147287038
MSI (s) (1C:B0) [10:10:19:203]: Note: 1: 2262 2: ServiceInstall 3: -2147287038
MSI (s) (1C:B0) [10:10:19:203]: Note: 1: 2262 2: Signature 3: -2147287038
MSI (s) (1C:B0) [10:10:19:203]: Note: 1: 2262 2: TextStyle 3: -2147287038
MSI (s) (1C:B0) [10:10:19:203]: Note: 1: 2262 2: TypeLib 3: -2147287038
MSI (s) (1C:B0) [10:10:19:203]: Note: 1: 2262 2: UIText 3: -2147287038
MSI (s) (1C:B0) [10:10:19:203]: Note: 1: 2262 2: Upgrade 3: -2147287038
MSI (s) (1C:B0) [10:10:19:203]: Note: 1: 2262 2: UpgradeCode 3: -2147287038
MSI (s) (1C:B0) [10:10:19:203]: Note: 1: 2262 2: Verb 3: -2147287038
MSI (s) (1C:B0) [10:10:19:203]: Note: 1: 2262 2: _Validation 3: -2147287038
MSI (s) (1C:B0) [10:10:19:203]: Note: 1: 2262 2: SxsMsmGenComponents 3: -2147287038
MSI (s) (1C:B0) [10:10:19:203]: Note: 1: 2262 2: MsiSFCBypass 3: -2147287038
MSI (s) (1C:B0) [10:10:19:203]: Note: 1: 2262 2: ISDFLInfo 3: -2147287038
MSI (s) (1C:B0) [10:10:19:203]: Note: 1: 2262 2: ISSelfReg 3: -2147287038
MSI (s) (1C:B0) [10:10:19:203]: Note: 1: 2262 2: LockRegPermissions 3: -2147287038
MSI (s) (1C:B0) [10:10:19:203]: Note: 1: 2262 2: DeleteRegistry 3: -2147287038
MSI (s) (1C:B0) [10:10:19:203]: Note: 1: 2262 2: DeleteProducts 3: -2147287038
MSI (s) (1C:B0) [10:10:19:203]: Note: 1: 2262 2: DeleteFiles 3: -2147287038
MSI (s) (1C:B0) [10:10:19:203]: Note: 1: 2262 2: DeleteComponents 3: -2147287038
MSI (s) (1C:B0) [10:10:19:203]: Note: 1: 2262 2: DefragFiles 3: -2147287038
MSI (s) (1C:B0) [10:10:19:203]: Note: 1: 2262 2: BackupAndRestorePreferences 3: -2147287038
MSI (s) (1C:B0) [10:10:19:203]: Note: 1: 2262 2: BackupAndRestoreRegistry 3: -2147287038
MSI (s) (1C:B0) [10:10:19:203]: Note: 1: 2262 2: MsiPatchCertificate 3: -2147287038
MSI (s) (1C:B0) [10:10:19:203]: Note: 1: 2262 2: AppsInUse 3: -2147287038
MSI (s) (1C:B0) [10:10:19:203]: Note: 1: 2262 2: ISDistribution 3: -2147287038
MSI (s) (1C:B0) [10:10:19:203]: Note: 1: 2262 2: ISSetupFile 3: -2147287038
MSI (s) (1C:B0) [10:10:19:203]: Note: 1: 2262 2: _MsiPatchTransformView 3: -2147287038
MSI (s) (1C:B0) [10:10:19:203]: Note: 1: 2262 2: #_BaselineCost 3: -2147287038
MSI (s) (1C:B0) [10:10:19:203]: Note: 1: 2262 2: #_BaselineFile 3: -2147287038
MSI (s) (1C:B0) [10:10:19:203]: Note: 1: 2262 2: #_BaselineData 3: -2147287038
MSI (s) (1C:B0) [10:10:19:203]: Note: 1: 2262 2: #_PatchCache 3: -2147287038
MSI (s) (1C:B0) [10:10:19:234]: Note: 1: 1708
MSI (s) (1C:B0) [10:10:19:234]: Note: 1: 2729
MSI (s) (1C:B0) [10:10:19:250]: Note: 1: 2729
MSI (s) (1C:B0) [10:10:19:250]: Product: Adobe Reader 8.1.2 -- Installation failed.

MSI (s) (1C:B0) [10:10:19:250]: MainEngineThread is returning 1624
Error applying transforms. Verify that the specified transform paths are valid.
MSI (c) (34:C4) [10:10:19:250]: Decrementing counter to disable shutdown. If counter >= 0, shutdown will be denied. Counter after decrement: -1
MSI (c) (34:C4) [10:10:19:250]: MainEngineThread is returning 1624
=== Verbose logging stopped: 7/24/2008 10:10:19 ===


I may just manually copy the file to the workstations and overwrite the existing file and update the network install point as well. Why adobe didn't release this as a patch (msp)...
Answered 07/24/2008 by: joedown
Second Degree Brown Belt

Please log in to comment
0
Stupid question, but does 'C:\Program Files\Adobe\Reader 8.0\Setup Files\{AC76BA86-7AD7-1033-7B44-A81200000003}\RdrSU.mst' exist?

Also, please use the 'code' button (it's marked '<%') when posting text of any length.
Answered 07/25/2008 by: VBScab
Red Belt

Please log in to comment
0
Yes the file exists. What is different is the @AcroRead812.mst which is something I'm not familiar with. Does the @ symbol specify the C:\Windows\Installer directory? I thought that the update was supposed to merge a transform with an existing transform... I don't have this problem with the full version of Acrobat after applying the patch but it specifies the full path to the transform.

Thanks for the code tip. I was looking for that when I posted but I thought the code button was for inserting html.


ORIGINAL: VBScab

Stupid question, but does 'C:\Program Files\Adobe\Reader 8.0\Setup Files\{AC76BA86-7AD7-1033-7B44-A81200000003}\RdrSU.mst' exist?

Also, please use the 'code' button (it's marked '<%') when posting text of any length.

Answered 08/01/2008 by: joedown
Second Degree Brown Belt

Please log in to comment
0
ORIGINAL: joedown
Does the @ symbol specify the C:\Windows\Installer directory?
No, it indicates that the transform is 'secure'. Nice write-up about the different transform types can be found here http://juice.altiris.com/tip/2642/msi-transforms-and-its-types

As the article says, you can't mix secure and non-secure transforms :(
Answered 08/04/2008 by: VBScab
Red Belt

Please log in to comment
0
Someone should tell that to Adobe. Shouldn't they already know that...


ORIGINAL: VBScab

As the article says, you can't mix secure and non-secure transforms :(

Answered 08/04/2008 by: joedown
Second Degree Brown Belt

Please log in to comment
0
I tried setting the property TRANSFORMSSECURE=1 but that still didn't make the transform deployed by the patch secure. Is there more that has to be done to change the transform to be secure?
Answered 08/14/2008 by: joedown
Second Degree Brown Belt

Please log in to comment
0
Any ideas on how to make the transform secure instead of unsecure?
Answered 08/20/2008 by: joedown
Second Degree Brown Belt

Please log in to comment
0
Hi Joe,
have you tried to add the "@" in front of your MST?
i would check your transform. This case results in the application of 2 transforms.
If i look at the log file, i see lots of errors regarding the application of the transform.
In my experience, 2 or more transforms often result in strange errors, because the first one does something which a later applied transform doesn't expect to be there.
A test could be to extract the "RdrSU.mst" transform from "AcrobatReaderUpd812_SU1_all.msi" and apply it with msitran to the readers 8.1.2 MSI. After that, load your transform against this new MSI in ORCA and save it.

However, as i wrote earlier: If you drive this things this far, it would probably easier to produce your own version with the SU1 already applied. We went this route and it works.

Regards, Nick
Answered 08/22/2008 by: nheim
Tenth Degree Black Belt

Please log in to comment
0
I'm going to curse Adobe (yet again) and roll my eyes if this fixes it, but have you tried using a shortname path, i.e. C:\Progra~1\Adobe\Reader~1\SetupF~1 instead of C:\Program Files\Adobe\Reader 8.0\Setup Files?
Answered 08/22/2008 by: dtrammell
Senior Yellow Belt

Please log in to comment
0
Anyone know why Adobe decided to release this patch as a msi instead of the more logical msp? Hopefully 8.1.3 comes out soon!
Answered 09/04/2008 by: oilernut
Senior Yellow Belt

Please log in to comment
0
Acrobat 9 is out...
Answered 09/04/2008 by: kiptek
Second Degree Green Belt

Please log in to comment
0
ORIGINAL: kiptek
Acrobat 9 is out...
Let joy be unconfined...
Answered 09/05/2008 by: VBScab
Red Belt

Please log in to comment
0
Yeah, I'm bagging this update and recommending to my organization that we upgrade to version 9. I will permanently disable Javascript in 9 and then I won't have to worry about JS security vulnerabilities in Acrocrap. We will end up doing it anyway so why not get started now...


ORIGINAL: kiptek

Acrobat 9 is out...
Answered 09/05/2008 by: joedown
Second Degree Brown Belt

Please log in to comment
0
Let joy be unconfined...
(clip of monks chanting from youtube goes here! :-)
Answered 09/05/2008 by: kiptek
Second Degree Green Belt

Please log in to comment
0
ORIGINAL: joedown

After installing this update I am no longer able to uninstall Adobe Acrobat reader 8.1.2 I receive an "Error applying transforms. Verify that the specified transform paths are valid"

I have traced this down to a specific registry key:

[HKEY_LOCAL_MACHINE\SOFTWARE\Classes\Installer\Products\68AB67CA7DA73301B7448A2100000030]
"Transforms"=@AcroRead812.mst;C:\Program Files\Adobe\Reader 8.0\Setup Files\{AC76BA86-7AD7-1033-7B44-A81200000003}\RdrSU.mst

The update is appending on the part after the semicolon. If I remove everything after the semicolon I can then uninstall Adobe Reader. How do I fix this problem? I don't want to deploy a patch to our organization that is going to prevent me from uninstalling the application if I need to.

I think I don't like Adobe products [:'(]



Yeah, I actually ended up deploying that patch, only to later upgrade, well try to upgrade, to Reader 9. You can actually patch their patch via scripting. I've written one that can be found here: http://www.michichael.com/misc/AdobeSU1Fixer.vbs

It's a basic vbscript that can be run with psexec or via startup scripts in your GPO - it only needs to run once to fix the issue. (This script basically changes the @ to a full pathname on the system, if it's installed).

The script includes a handy logging feature that makes it useful to run from a single workstation if you use psexec - I never did test it with login scripts. Lemme know if you have any questions!
Answered 11/04/2008 by: Michichael
Yellow Belt

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