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

Reader DC AIP install error 2753: The file 'rdrservicesupdater.exe' is not marked for installation

Community Beginner ,
Sep 13, 2022 Sep 13, 2022

Copy link to clipboard

Copied

We have been deploying Acrobat Reader 2017 by slipstreaming it into AIPs and installing using GPOs. Our systems are all Windows 10 Pro 21H2 64-bit boxes.

 

We are now switching to the DC (continouus) track and have been trying to create our very first AIP.

To do so we first downloaded AcroRdrDC2200220191_en_US.exe (SHA256: 0d434c796a37cfb648e7dbaf4219965076f034e5662a160ea5d626d19baf20b2).

 

First, we extracted its contents to c:\install :

AcroRdrDC2200220191_en_US.exe -nos_ne -nos_oC:\Extract

Proceeded to create a test AIP at c:\install with the following commands:

msiexec /a C:\Extract\AcroRead.msi TARGETDIR="c:\install"
copy c:\Extract\setup.ini c:\install\setup.ini
msiexec /a c:\install\AcroRead.msi /p c:\extract\AcroRdrDCUpd2200220191.msp

Before trying to do customizations with the Adobe customization wizard, we tried to make a test installation with:

msiexec /i c:\install\acroread.msi

Installation starts and fails with the error mentioned at the top.

Doesn't DC support this method of installation?

 

I made a test run with MSI logging enabled and I'm attaching the log in case it helps. Thanks in advance for any information provided.

TOPICS
Download and install

Views

1.5K

Translate

Translate

Report

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

correct answers 1 Correct answer

Community Beginner , Sep 13, 2022 Sep 13, 2022

Well, the issue was actually of an uninstallation gone wrong in two (out of two) of our test machines. Before, Reader 2017 was installed, however we made sure to uninstall properly via add-remove programs.

In any case, oil's well, case solved.

Votes

Translate

Translate
Community Beginner ,
Sep 13, 2022 Sep 13, 2022

Copy link to clipboard

Copied

LATEST

Well, the issue was actually of an uninstallation gone wrong in two (out of two) of our test machines. Before, Reader 2017 was installed, however we made sure to uninstall properly via add-remove programs.

In any case, oil's well, case solved.

Votes

Translate

Translate

Report

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