Office 2019 failing 0-2054 (0) error

Aaron Peay

July 23, 2021 16:57

Using PDQ Deploy to uninstall Office 2013, check for Visio, shutdown -r -f.

Everything to this point works fine, but the install wont go.

I watched the very helpful 40 minute on youtube about it.

Here are my script details:

Any thoughts to why its failing? Wont run from a Cmd either.

Many thanks

And my config.xml:

<Configuration ID="6aefc3cd-4f3e-479c-9e94-461fb2dda470">
  <Add OfficeClientEdition="32" Channel="PerpetualVL2019" SourcePath="\\POPEYE\O19" Version="16.0.10376.20033" AllowCdnFallback="FALSE">
    <Product ID="ProPlus2019Volume"PIDKEY="XXXX">
      <Language ID="en-us" />
      <ExcludeApp ID="Groove" />
      <ExcludeApp ID="Lync" />
    </Product>
  </Add>
  <Property Name="SharedComputerLicensing" Value="0" />
  <Property Name="SCLCacheOverride" Value="0" />
  <Property Name="AUTOACTIVATE" Value="1" />
  <Property Name="FORCEAPPSHUTDOWN" Value="TRUE" />
  <Property Name="DeviceBasedLicensing" Value="0" />
  <Updates Enabled="TRUE" />
  <AppSettings>
    <Setup Name="Company" Value=" Texas" />
  </AppSettings>
  <Display Level="None" AcceptEULA="TRUE" />
</Configuration>

Comments

7 comments

Mike Kercher
July 23, 2021 17:00

Maybe try clicking the Include Entire Directory option. I had a similar issue yesterday with a different package.

0
Aaron Peay
July 23, 2021 17:09

I dont think thats it. I cant get the installation to run even without PDQ. Using the MS recommended command line method

0
Mike Kercher
July 23, 2021 17:33

I'd still give it a try.

I wonder if you were to test this on one machine:

Copy the source folder contents to the local disk and run it locally. If it runs successfully, selecting the option to include the entire directory should fix it.

The package I was having a problem with could not find a data file when running from my DFS repository. After I included the whole folder, it ran without a hitch.

0
Aaron Peay
July 24, 2021 16:25

I tried including the directory.

The error is now 0-2039 (0)

It looks like it will run if I pull from the CDN. Man what a waste of BW and time.

Id love to find a solution pulling from a local source

0
Colby Bouma
July 24, 2021 18:13
There might be remnants of the previous Office installation. Try enabling "Uninstall any MSI versions" under "Update and upgrade". That adds the following line to the XML:
```
<RemoveMSI/>
```
0
Robert Johnson
July 26, 2021 12:14

Here is my working deployment, for example.

Configure.xml

and PDQ:

0
Dirk Buender
July 27, 2021 07:47 (Edited July 27, 2021 07:48)

Hi,

our Remove Script (xml) looks like this

<Configuration>
<Display Level="None" AcceptEULA="True" />
<Property Name="FORCEAPPSHUTDOWN" Value="True" />
<Remove All="TRUE">
<Product ID="ProPlus2019Volume">
<Language ID="de-de" />
<Language ID="en-us" />
</Product>
</Remove>
</Configuration>

0

Please sign in to leave a comment.

Didn't find what you were looking for?

New post