I keep getting "the feature you are trying to use is on a network resource that is unavailable. Click OK to try again or ener an alternate path to a folder containing the installation package 'AdbeRdr1010_en_US.msi' in the box below.

Any Work Arounds?? We deployed the Application via SCCM and Disabled all updates for the package using ACW but still I am geting this ?? 


Answer Summary:
Alright Thank you so much for the great Info, I figured out the Problem exactly!! The Previous version which is 10.0 was not deployed as Packaged application so the auto updates were enabled and it is making a registry entry Here HKLM\Software\Adobe\Adobe ARM\1.0\ARM iCheck=3 iCheckReader=3 That Means Auto updates enabled Now My package 10.1.3 is un installing the old version but not deleting the registry entry which I mentioned so Thats why the usewrs still getting updates option Now I changed them to 0. That did the Job for me REF: http://kb2.adobe.com/cps/837/cpsid_83709/attachments/Acrobat_Reader_Updater.pdf In that Page 15 & 16 got the clear Info Thanks
Cancel
0 Comments   [ + ] Show Comments

Comments

Please log in to comment

Community Chosen Answer

3

It looks like the installer is looking to that folder to find the older versions msi to uninstall first. 

If this is running as the logged in user could also be they have no rights to this folder.

Answered 09/18/2012 by: SMal.tmcc
Red Belt

  • Hmm, We have deployed Reader 10.1.3 via SCCM and We used to have 10.0.1 before. That 10.0.1 got uninstalled and installed the latest 10.1.3 but in some machines now I am getting that error...
  • Before SCCM deployment of Package 10.1.3 the previous package was not update disabled... So is that might be the reason??
  • Could well be, ARM is a seperate app, did you uninstall arm seperatly when you pushed 10.1.3?
  • Yes the ARM application I dont See in my Control Panel and HKLM\Software\Microsoft\Windows\Currentversion\Uninstall\ Entry ...
  • we ran into this with zenworks once, could not figure where it was getting the call from so we resolved it by giving it what it wants and used a batch that put the msi back in the location it was looking for it in, run the update and then deleting it again afterwards.
  • Okay the Solution Here you are mentioning here is Just go for the Deployment of Latest Patch what it is asking for which is 10.1.4.. Am I right?? For that I need to Uninstall and Install again with Patch updated as Admin guide mentioned :((
    http://helpx.adobe.com/acrobat/kb/enterprise-administration-acrobat-products.html
  • I found the needed file the new install was complaining about missing on a machine and created a batch file.
    step 1 recreate the missing structure and place the missing msi in the folder. (c:\programdata\abobe\arm\reader_10.0.1\adbrdr1010_en_us.msi)
    step 2 run the upgrade install 10.1.4
    step 3 delete the structure and file you created in step 1
  • Alright Perfect Sir...I will make sure to do that. If I do not wanna go for Quarterly update which is 10.1.4. and I wanna keep my users in 10.1.3 and get rid of that message what ever it is in Screenshot.. Is it possible to Suppress that ?? Just because as I said we went to upgrade jus 2 weeks ago!!!
  • Okay, Here I found something. When I install my 10.1.3 package in Clean VMMachine I am not getting this entrees HKLM\Software\Adobe\Adobe ARM\1.0\ARM Hives but in the User Machine who got that Message box I can see those entrees !!! So is there any thing we can do with those regestry keys ?
    these are the values there
    iCheck=o
    iLastID=10e
    iLastY=7db

    So Any Work arounds here ??
  • Since those are left from 10.0.1 I would export the keyset (for backup) and delete them and see if problem goes away. The worst case is remerge or push 10.1.4 again with a repair switch.
  • on the ones already pushed you may need to run fixit.
    http://support.microsoft.com/kb/971187
    http://support.microsoft.com/kb/2438651
  • Alright Thank you so much for the great Info, I figured out the Problem exactly!! The Previous version which is 10.0 was not deployed as Packaged application so the auto updates were enabled and it is making a registry entry Here HKLM\Software\Adobe\Adobe ARM\1.0\ARM
    iCheck=3
    iCheckReader=3
    That Means Auto updates enabled Now My package 10.1.3 is un installing the old version but not deleting the registry entry which I mentioned so Thats why the usewrs still getting updates option Now I changed them to 0.
    That did the Job for me
    REF: http://kb2.adobe.com/cps/837/cpsid_83709/attachments/Acrobat_Reader_Updater.pdf
    In that Page 15 & 16 got the clear Info
    Thanks
Please log in to comment

Answers

2

Disabling autoupdate in the package would not affect the patching of the application manually.

I suspect that your issues relate to Adboe's methods of releasing updates.

You can't apply a quarterly update (10.1.4) over a previous quarterly update (10.1.3).

Adobe's recommended approach is to patch your base (10.0.1) AIP to the new patch level, uninstall previous version and perform a new install of the the latest release.

 

This link will provide more info - http://www.itninja.com/question/trying-to-deploy-adobe-acrobat-x-standard-update-10-1-3-file-is-a-msp-and-wont-install

Hope that helps,

Dunnpy

Answered 09/18/2012 by: dunnpy
Red Belt

  • So to get rid of it, What should I do?? Create a New Package again for 10.1.4. Uninstall Previous versions and Deploy the New one?? We Deployed 10.1.3 very recently :(((
    • my guess is the 10.1.3 push removed that structure
  • I would try to get that msi file from a machine, run a silent uninstall (either as a push or from a share) on machines that have it installed on yet prior to the 10.1.4 push. The existing reader will still work without arm installed.
Please log in to comment
2

You should always customize the base package separately and then install the patch over it. Do not apply patch onto the base package and then install it.

We have done the same way and it installs beautifully over any previous patch.

Answered 09/18/2012 by: piyushnasa
Red Belt

  • The approach should be, you have to patch the base msi through Admin Installation and then create transform and customize it..
Please log in to comment
Answer this question or Comment on this question for clarity

Share