Answered by:
Error when starting Adobe reader 11 App-V package

Question
-
How do I disable Acrobat reader for checking if the ARM Service is present?
I have created an app-v 5.0 package for Acrobat reader 11. When I run the package on the sequencer I don't have any issues. When I run it on my test machine I get a pop-up stating "There was an error during installation. An internal error occurred."
I have already tried removing the reg keys in the package that refer to ARM, but this hasn't worked.
Is there a step I need to take before sequencing that will resolve this?
Thanks for the help. Event log entry follows.
The event viewer gives me further details on the event:
Log Name: Application
Source: AdobeARMservice
Date: 10/31/2014 3:53:38 PM
Event ID: 0
Task Category: None
Level: Information
Keywords: Classic
User: N/A
Computer: some-machine
Description:
The description for Event ID 0 from source AdobeARMservice cannot be found. Either the component that raises this event is not installed on your local computer or the installation is corrupted. You can install or repair the component on the local computer.
If the event originated on another computer, the display information had to be saved with the event.
The following information was included with the event:
Service started
Event Xml:
<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
<System>
<Provider Name="AdobeARMservice" />
<EventID Qualifiers="0">0</EventID>
<Level>4</Level>
<Task>0</Task>
<Keywords>0x80000000000000</Keywords>
<TimeCreated SystemTime="2014-10-31T19:53:38.000000000Z" />
<EventRecordID>1666</EventRecordID>
<Channel>Application</Channel>
<Computer>swv-w2k12r2-102</Computer>
<Security />
</System>
<EventData>
<Data>Service started</Data>
</EventData>
</Event>
Thanks
Friday, October 31, 2014 8:11 PM
Answers
-
Just checked out my last notes from when I sequenced it, try this:
When installing the MSI, add this property to the property table via the Adboe customisation tool:
DISABLE_ARM_SERVICE_INSTALL=1
And add the following registry key:
[HKLM\SOFTWARE\Adobe\Adobe ARM\1.0\ARM]
"iCheckReader"=dword:00000000That should both disable the service and stop Adobe from trying to update itself (the other commonly used key to disable updates is stored under policies and therefore ignored by default in App-V).
- Edited by Dan Gough Tuesday, November 4, 2014 1:04 PM
- Proposed as answer by kirk_tnModerator Wednesday, November 5, 2014 6:59 AM
- Marked as answer by cslish Tuesday, November 11, 2014 6:09 PM
Tuesday, November 4, 2014 1:04 PM
All replies
-
It's been a while since I sequenced it but I think I disabled the service during sequencing...
Also check out: http://support.microsoft.com/kb/2900929
PLEASE MARK ANY ANSWERS TO HELP OTHERS Blog: rorymon.com Twitter: @Rorymon
Friday, October 31, 2014 10:17 PM -
Adobe has an how-to for that;
http://www.adobe.com/devnet-docs/acrobatetk/tools/AdminGuide/appv.html, though it doesn't refer to the ARm service. Firthermore it is written for App-V 4.x, so the steps may be a little bit different.http://stealthpuppy.com/adobe-reader-xi-deployment/ a first-stop-source.
Falko
Twitter @kirk_tn | Blog kirxblog | Web kirx.org | Fireside appvbook.com
- Proposed as answer by znack Monday, November 3, 2014 7:54 PM
Monday, November 3, 2014 11:11 AMModerator -
Just checked out my last notes from when I sequenced it, try this:
When installing the MSI, add this property to the property table via the Adboe customisation tool:
DISABLE_ARM_SERVICE_INSTALL=1
And add the following registry key:
[HKLM\SOFTWARE\Adobe\Adobe ARM\1.0\ARM]
"iCheckReader"=dword:00000000That should both disable the service and stop Adobe from trying to update itself (the other commonly used key to disable updates is stored under policies and therefore ignored by default in App-V).
- Edited by Dan Gough Tuesday, November 4, 2014 1:04 PM
- Proposed as answer by kirk_tnModerator Wednesday, November 5, 2014 6:59 AM
- Marked as answer by cslish Tuesday, November 11, 2014 6:09 PM
Tuesday, November 4, 2014 1:04 PM -
Thanks Dan,
That worked.
Thanks
Tuesday, November 11, 2014 6:09 PM