Resolve LBD Export to Excel Issues

Submitted by Nathan Clouse on 08/01/19.

Last modified: 

08/01/19

Tags: 

Are you getting the following error when exporting to excel from Dynamics 365 for Finance and Operations: Local Business Data?

Could not upload to the storage location: Could not load file or assembly 'Microsoft.WindowsAzure.Storage, Version=5.0.0.0, Culture=neutral, PublicKeyToken=31bf3856ad364e35' or one of its dependencies.

This is a known issue that MSFT will hopefully address in the next week or two. In the mean time, you can do the following post deploy to address the issue. This will need to be after each deployment.

  1. On each AOS, go to task manage, click on the details tab, find AXService.exe, right click then go to open file location
  2. Find AXService.exe.xml and open in a text editor of your choice
  3. Find "<assemblyIdentity name="Microsoft.WindowsAzure.Storage" culture="neutral" publicKeyToken="31bf3856ad364e35" />"
  4. Replace with the following: 

<dependentAssembly>

      <assemblyIdentity name="Microsoft.WindowsAzure.Storage" culture="neutral" publicKeyToken="31bf3856ad364e35" />

<bindingRedirect oldVersion="0.0.0.0-8.1.1.0" newVersion="8.1.1.0" />

   </dependentAssembly>

  1. Like so: (quick note that your specific version may differ from the example. Look at Microsoft.WindowsAzure.Storage.dll in the same folder as the .xml file to determine its specific version and use that version for the .xml file update)

Before:

      <dependentAssembly>
        <assemblyIdentity name="Microsoft.WindowsAzure.Storage" publicKeyToken="31bf3856ad364e35" culture="neutral" />
        <bindingRedirect oldVersion="0.0.0.0-5.0.0.0" newVersion="4.3.0.0" />
      </dependentAssembly>

After:

      <dependentAssembly>
        <assemblyIdentity name="Microsoft.WindowsAzure.Storage" culture="neutral" publicKeyToken="31bf3856ad364e35" />
        <bindingRedirect oldVersion="0.0.0.0-8.1.1.0" newVersion="8.1.1.0" />
      </dependentAssembly>

  1. Restart the AOS Service in the fabric or just kill AXService.exe in task manager if no users are signed in and batch processing has been suspended as well as all batch jobs are complete.
  2. Sign in and test that the issue is resolved. If you have multiple AOSs, you will have to do this process for each AOS.