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

Acrobat Customization Wizard DC Error - Unable to Submit Changes, MSI Set Value failed, Error Code = 6

New Here ,
Jun 12, 2018 Jun 12, 2018

Hello all,

Attempting to customize an installation of Acrobat Standard 2017.  I am using the DC customization wizard (filename CustWiz1502020039_en_US_DC.exe ) and attempting to customize the latest version downloaded by the Acrobat_2017_Web_WWMUI.exe extractor.  Any attempts, however small, to generate a Transform end with the error message "Unable to Submit Changes, MSI Set Value failed, Error Code = 6."

Suggestions?

3.3K
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

correct answers 1 Correct answer

Adobe Employee , Jun 13, 2018 Jun 13, 2018

Is this a newly created MST or is this one that you have used previously in a different version of Acrobat?  If it is previously used one, then create one from scratch.

If this is a newly created MST, make sure that you are on the local machine and not on a server share.  Make sure the permissions in the area you have the flat files located have READ/WRITE/EXECUTE  for everyone.

You may want to re-download the 2017 ESD executable and re-extract the flat files to the desktop.

Translate
Adobe Employee ,
Jun 13, 2018 Jun 13, 2018

Is this a newly created MST or is this one that you have used previously in a different version of Acrobat?  If it is previously used one, then create one from scratch.

If this is a newly created MST, make sure that you are on the local machine and not on a server share.  Make sure the permissions in the area you have the flat files located have READ/WRITE/EXECUTE  for everyone.

You may want to re-download the 2017 ESD executable and re-extract the flat files to the desktop.

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 ,
Jun 14, 2018 Jun 14, 2018
LATEST

Thanks Steve.  The issue seems to stem from working with server shares.  I installed locally and used a local source and ran into the error a few more times, but a couple more attempts after a restart seemed to have finally let it through.

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