Exit
  • Global community
    • Language:
      • Deutsch
      • English
      • Español
      • Français
      • Português
  • 日本語コミュニティ
  • 한국 커뮤니티
0

Can't upgrade Acrobat Professional 9.0 to Acrobat Professional 9.3

Guest
Feb 12, 2010 Feb 12, 2010

We have been installing Acrobat Pro 9.0 on machines.  Now that the 9.3 update has been released we want to update the computers.  I have followed the instructions to create an AIP. 9.0, 9.1, 9.1.2, 9.2, 9.3.  When I attempt to install Acrobat Professional 9.3 on a computer that has Acrobat Professional 9.0 on it I receive the following error message.

Another version of this product is already installed.  Installation of this version cannot continue.  To configure or remove the existing version of this product, use Add/Remove Programs on the Control Panel.

If I install the package I created on a computer that does not have Adobe Acrobat Pro installed on it, there are no problems.  The package is installed and it is at the correct version.

I obviously don't think I should have to manually remove Acrobat Pro 9 from the computers.  Shouldn't the patched 9.3 product install over 9.0?

7.7K
Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Mar 11, 2010 Mar 11, 2010

How did you get past the missing dll errors on your aip when moving from 9.1 to 9.1

2?

I've burned almost 3 days on this.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Guest
Mar 12, 2010 Mar 12, 2010

The actual problem is one of Adobe's creation.

When making an adminstrative install point you can upgrade in the folowing manner:

Original product --> Qaurterly update 1 --> ,,,, --> Quarterly update N (--> security update)

Notice the order : Original, Quarterly, Security. **Adobe** made the deliberate decision to do it this way.

You can NOT install a quarterly update after a security update, event though the quarterly contains the security.

Reference http://kb2.adobe.com/cps/498/cpsid_49880.html

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Guest
Mar 12, 2010 Mar 12, 2010

The order for patching for this needs to be 9.0.0, 9.1.0, 9.1.2, 9.2.0,

9.3.0

Cheryl L. Robinson

NYS Office of State Comptroller

Customer Services/Desktop Support

(518) 474-8808

clrobinson@osc.state.ny.us

ghbpiper

<forums@adobe.com

> To

Cheryl Robinson

03/12/2010 02:19 <clrobinson@osc.state.ny.us>

AM cc

Subject

Please respond to

clearspace-551192 Can't upgrade Acrobat Professional

659-462618-2-2653 9.0 to Acrobat Professional 9.3

913@mail.forums.a

dobe.com

How did you get past the missing dll errors on your aip when moving from

9.1 to 9.1

2?

I've burned almost 3 days on this.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Guest
Mar 12, 2010 Mar 12, 2010

And if you install the current 9.3.1 you can forget about installing any quarterly updates afterwards. Thanks Adobe for giving us the choice of fouling our installations or being open to security holes .

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Mar 12, 2010 Mar 12, 2010

This is insanity.  Sounds like the most viable plan would be to remove any previous installation and force installation to the newest version.  IF I could get the blasted thing to get past the 9.1.2 upgrade.

Hey Adobe, anyone paying attention?

It should not take a rocket scientist to figure out the simple way around this is to distribute full installers for any new version and allow for complete reinstall over the top of any previous version.  Done and done.  In what world does the current approach begin to make any kind of sense, especially in a managed desktop environment?

If I'm missing something here, someone please enlighten me.  The product simply does not work as advertised.

Openoffice.org is looking pretty attractive right now.  Does a fine job of building pdfs.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Mar 12, 2010 Mar 12, 2010

I understand.  But I cannot get it from 9.1.0 to 9.1.2  Fails with a dll dependency error.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Mar 14, 2010 Mar 14, 2010

This is what I ended up doing - works except that it borks the icons for the shortcust in the start menu.  FWIW this is a volume license version.

@echo off
net use <UNCPATH OF INSTALLER FILES> <PASSWORD> /user:<USERID>
q:

start /wait msiexec /i AcroPro.msi TRANSFORMS=AcroPro.mst REBOOT=REALLYSUPPRESS /qn
start /wait msiexec /update AcroProStdUpd910_T1T2_incr.msp;AcrobatUpd912_all_incr.msp;AcrobatUpd920_all_incr.msp;AcrobatUpd930_all_incr.msp;AcrobatUpd931_all_incr.msp REINSTALLMODE=vomus REINSTALL=ALL REBOOT=REALLYSUPPRESS /qn
c:
net use q: /delete

Adobe, your support on this, well, is just plain abysmal.  Hours wasted  googling for solutions, on the phone with "support", with people that  just don't get enterprise software distribution, with an accent and a  script.  They were polite and professional, but lacked the necessary knowledgebase/skillset to resolve the issue, which in this case was created by whomever packaged the installer, in my estimation.  I imagine I will be looking for a FOSS replacement in the very  near future, and do my level best to be sure people learn about it.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Apr 14, 2010 Apr 14, 2010

Been having the same issues for weeks and finally found this thread.

Same issue going from Pro and Std 9.0.0.332 to 9.3.0.148...must uninstall previous version.


Some instances of using the Customization Wizard I would notice that the uninstall previous versions would be checked and unchecked and always grayed out.

Using the same Wizard and redistributatble version of standalone Acrobat Reader has no problems going from 9.0 to 9.3 however 9.1 to 9.3 produces the same issues as above.

Just hoping to keep this thread alive

KNOCK!, KNOCK!  ADOBE....HELLOOO PAID CUSTOMERS HERE...LIL HELP

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Apr 14, 2010 Apr 14, 2010

So no response from 1-800-adobesupportsux, eh?

Are you rebuilding the administrative install from scratch?  I would (and will) try that.  I'm still recovering from the last effort.

Make sure you are including the right updates...  Terminology escapes me but you can't apply a major update over a security patch.  Guess it would be too easy.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Apr 14, 2010 Apr 14, 2010

Uh, I'm still on hold - sad face

When I decided to wrap up my patches is when I built the admin install fresh.

Then applied:

AcroProStdUpd910_T1T2_incr.msp

AcrobatUpd912_all_incr.msp

AcrobatUpd913_all_incr.msp

AcrobatUpd920_all_incr.msp

AcrobatUpd930_all_incr.msp

AcrobatUpd931_all_incr.msp

All took and updated fine.  Fresh install works great.


I'm not sure how to tell what updates are major vs. security.  I mean these are MSP patch files but I'm not sure if that is the indication you refer to as "Terminology".

-Mike

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Apr 14, 2010 Apr 14, 2010

Yes that's what I was talking about.  It may well be that a full rip and remove is necessary prior to installing.

When you DO install make sure you include the MST generated by the customization wizard.

I did my install w/a batch file as follows:

net use q: \\<path-to-aip> <password> /user:<uid>
q:
start /wait msiexec /i AcroPro.msi TRANSFORMS=AcroPro.mst REINSTALL=ALL REINSTALLMODE=vamus REBOOT=REALLYSUPPRESS /qn
c:
net use q: /delete

and THAT finally worked.

FWIW we use the KBOX-1000 mgmt appliance for deployment, you may have to adapt to whatever method you use (GPO, Landesk, whatever).

Software works well once installed but WHAT A BLOATED MONSTROSITY.

I think a root canal would have been more enjoyable and productive.  Just sayin'

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Apr 14, 2010 Apr 14, 2010

Also, build your AIP as follows...

At any rate it worked for me.  Adobe, feel free to add something AT ANY TIME....

C:
cd\AcroBatPro9
md \AcrobatPro9AIP
start /wait msiexec /a AcroPro.msi TARGETDIR=C:\AcrobatPro9AIP /Liv c:\AcrobatPro9AIP\install900.log /qn
cd \AcrobatPro9AIP
start /wait msiexec /p c:\AcrobatPro9\AcroProStdUpd910_T1T2_incr.msp /a AcroPro.msi TARGETDIR=C:\AcrobatPro9AIP PATCHAIP=1 /Liv install910.log /qn
start /wait msiexec /p c:\AcrobatPro9\AcrobatUpd912_all_incr.msp /a AcroPro.msi TARGETDIR=C:\AcrobatPro9AIP PATCHAIP=1 /Liv install912.log /qn
start /wait msiexec /p c:\AcrobatPro9\AcrobatUpd920_all_incr.msp /a AcroPro.msi TARGETDIR=C:\AcrobatPro9AIP PATCHAIP=1 /Liv install920.log /qn
start /wait msiexec /p c:\AcrobatPro9\AcrobatUpd930_all_incr.msp /a AcroPro.msi TARGETDIR=C:\AcrobatPro9AIP PATCHAIP=1 /Liv install930.log /qn
start /wait msiexec /p c:\AcrobatPro9\AcrobatUpd931_all_incr.msp /a AcroPro.msi TARGETDIR=C:\AcrobatPro9AIP PATCHAIP=1 /Liv install931.log /qn

This will build your AIP.  Copy it to your network share and do your transform with the customization tool kit from there.  IIRC there was some stupid little files you need to copy from the original install disk for it to save correctly.  It'll error if your missing it.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Guest
Apr 14, 2010 Apr 14, 2010

Major and security updates are not particularly differentiated. It's good to apply a newly available patch update

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Guest
Apr 15, 2010 Apr 15, 2010

milehighwelch wrote:

Uh, I'm still on hold - sad face

When I decided to wrap up my patches is when I built the admin install fresh.

Then applied:

AcroProStdUpd910_T1T2_incr.msp

AcrobatUpd912_all_incr.msp

AcrobatUpd913_all_incr.msp

AcrobatUpd920_all_incr.msp

AcrobatUpd930_all_incr.msp

AcrobatUpd931_all_incr.msp


You should check and follow this article : cpsid_49880.

You'll see the current 9.3.2 AIP should be done as follows:

Version 9 Current Recommended AIP Configuaration:

Acrobat:  9.0.0 > 9.1.0 > 9.1.2 > 9.2.0 > 9.3.0 > 9.3.2

(note : the misspelling of cofiguration was Adobe's, not mine)

You should not have been able to successfully install the 9.2.0 update onto your AIP with 9.1.3 installed to it. Likewize, you will not be able to install 9.3.2 to your AIP with 9.3.1 installed.

Per the cpsid page:

Unacceptable:  Acrobat 9.0.0  (Original Product) -> 9.1.0 (Quarterly) -> 9.1.2 (Quarterly) ->  9.1.3 (Security) ->

9.2.0 (Quarterly) ->  9.3.0 (Quarterly) -> 9.3.1(Security) -> 9.3.2(Quarterly)

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Guest
Apr 16, 2010 Apr 16, 2010

Yes, the recommendations for 9.3.2 in the http://kb2.adobe.com/cps/498/cpsid_49880.html is the way to go

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Apr 19, 2010 Apr 19, 2010

So if you should not apply a Quarterly Update to an AIP that had a Security Patch applied last and there is no differentiation between the Quarterly and Security Patch...you see where I'm going with this I'm sure.

Do you make an entire back up of your AIP prior to applying each .MSP?

Especially when Adobe is releasing patches every other month.  How do you keep your AIPs up to date and maintain administrative control?  Meaning not creating the issues that started this thread in the first place where you can't update an existing installation.

Regards,

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
Guest
Apr 19, 2010 Apr 19, 2010

The problem is Adobe's patch design:

They put out quarterly updates and security updates. The quarterly updates should be rolled into AIPs, the security updates should not. The quarterly updates, while including the same security updates, will not install on top of those security updates. This is by ADOBE'S design. They have stated in other places that they don't won't to deal with AIPs that have anything other than the quarterly updates, that admins should only worry about deploying the quarterly updates in AIPs, and that the autoupdater should be allowed to autoupdate the end PC whenever.

Adobe seems to believe that corporate network admins allow the end-users install software. Adobe needs to understand that was true -- YEARS ago, but certainly not now.

Nor does Adobe seem to grasp that many companies have to work under testing guidelines and demands, imposed by auditing processes and/or legislative rules such as HIPAA. In those regimes autoupdate=MEGA-BAD.

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Apr 20, 2010 Apr 20, 2010

So I spent most of yesterday rebuilding both my Acrobat Pro and Acrobat Std AIP per TechNote http://go.adobe.com/kb/ts_cpsid_49880_en-us using only Quarterly updates.  I did this in hopes of being able to successfully upgrading existing installs of the original product 9.0.0 to a patched AIP of 9.3.2.

It still does not work.  I am prompted to manually uninstall previous versions.  The posted "workaround" does still work of using REINSTALLMODE=vomus.  I'm curious as to what the next update will do..9.3.2 to 9.4?  Is this ever going to work as it is supposed to where the latest install will successfully manage what needs to happen with a previous install?

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Apr 27, 2010 Apr 27, 2010

Would anyone support the following as a recommended solution?

I was having undesired effects from the use of REINSTALLMODE=vomus.  So in an effort to get this figured out I took it upon myself to find out why the automatic removal of previous version was not working.

When you open the Customization Wizard there is a "Direct Editor" option.  One of the tables is "Upgrade", and I noticed my SID version was not listed as an "UpgradeCode", was close but not the same.  So I got the correct SID and added it using the data from similar rows.  Sealed it up...saved the updated transform and msi.

I then went to a PC that had 9.0.0.332 and ran my setup.exe from my AIP. Guess what happened?  It automatically uninstalled the old version rather than giving me the BS message about you must got to Add/Remove programs and uninstall the old versions.

So this worked perfectly, as one would suspect it should.  Should I processed in using this method for the rest of my environment?

What do you think?

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Apr 27, 2010 Apr 27, 2010

Well, it might explain some of those messages I got trying to upgrade from 9.3.1 to 9.3.2...

Sorry to be dense, but can you post additional detail on what you did, and how you determined the correct SID version?

Thanks

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines
New Here ,
Apr 27, 2010 Apr 27, 2010
LATEST

Browse in the registry to

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\

Highlight {AC76BA86-1033-0000-7760-000000000004} or {AC76BA… as Adobe stuff usually starts with that

On the right you will see stuff like

DisplayName = Adobe Acrobat…

DisplayVersion = 9.3.2

This confirms the product and version.  So in the above example if you want to uninstall it this would be the command

Msiexec.exe /x{AC76BA86-1033-0000-7760-000000000004}  and then /qb or /qb! For no cancel button etcetera

So once I found my 9.0.0.332 SID I opened Adobe Customization Wizard 9, opened my MSI with attached MST.  Clicked on the last option in the left column, “Direct Editor”, then on the table “Upgrade”.  I looked in the list for my SID and saw several close ones but not the same SID.  So I made note of the VersionMin, Attributes, and ActionProperty of the similar row.  I then added a new row with the known SID I wanted removed and with the noted info from the other row.

Clicked save, which updated my mst.  I’m using a command that launches setup.exe.  I find that the settings in the transform are more consistent than when running a full msiexec i/…transform=…command.

When I run the setup.exe I see the msiexec window startup saying configuring 9.3.2 and then it flash to an msiexec window saying removing older version of the product followed shortly by installing 9.3.2

Done

-Regards,

Translate
Report
Community guidelines
Be kind and respectful, give credit to the original source of content, and search for duplicates before posting. Learn more
community guidelines