Small and medium business | Business Central, N...

BC DevOps - Facing issue while running pipeline

(7) Share

Report

Posted on by Crishmin

We have configured Business central Devops and When we run the pipeline it throws below error.

Error downloading symbols for Avalara_Avalara AvaTax_26.0.28.1.app. Error was: Exception calling "GetResult" with "0" argument(s): "Response status code does not indicate success: 404 (Not Found)." At C:\Users\VssAdministrator\AppData\Local\Temp\10a83c95-0177-4e60-8354-b677ce681b34\AppHandling\Compile-AppInNavContai ner.ps1:485 char:25 + ... throw "Error downloading symbols for $symbolsName. Error ... + ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ + CategoryInfo : OperationStopped: (Error downloadi...4 (Not Found).":String) [], RuntimeException + FullyQualifiedErrorId : Error downloading symbols for Avalara_Avalara AvaTax_26.0.28.1.app. Error was: Exception calling "GetResult" with "0" argument(s): "Response status code does not indicate success: 404 (Not Found)."

Categories:

Dynamics 365 Business Central

I have the same question (0)

All responses (5)

Answers (0)

Suggested answer

OussamaSabbouh 12,766 Super User 2026 Season 1 on at

Like (4)

Report
Copy link

Link copied!

Hello,

The 404 error means the Avalara AvaTax symbols aren’t found.

Make sure the app.json dependency version matches the installed Avalara app.

Install the app in your build container or sandbox before downloading symbols.

Check your al.packageCachePath and clear .alpackages if needed, then rebuild.

Regards,

Oussama

1 people found this reply helpful.

Was this reply helpful? Yes No
Suggested answer

Aman Kakkar 2,977 Super User 2026 Season 1 on at

Like (4)

Report
Copy link

Link copied!

Hi,

This means that the DevOps build agent could not find or download the .app symbol file for the Avalara AvaTax extension from the Business Central service or artifact feed.

The Avalara app must be installed and published in the Business Central environment (sandbox or container) before symbol download can succeed.

Also, you can try cleaning up symbols folder or restarting the agent.

For debugging purposes, you can remove dependencies temporarily from your app.json for the Avalara app to test if build process is successful.

Hope this helps.

Aman K

Was this reply helpful? Yes No
Suggested answer

Khushbu Rajvi. 22,106 Super User 2026 Season 1 on at

Like (4)

Report
Copy link

Link copied!

The error occurs because the pipeline can’t find the Avalara_AvaTax_26.0.28.1 app to download its symbols. This usually means the Avalara extension isn’t installed or published in the build container, or the version in your app.json doesn’t match what’s available. Make sure the correct Avalara app version is published in your container or environment, and update the dependency version in app.json if needed. If it’s an AppSource app, contact Avalara for access to its symbols.

Was this reply helpful? Yes No
Suggested answer

Jeffrey Bulanadi 9,112 Super User 2026 Season 1 on at

Like (2)

Report
Copy link

Link copied!
Hi,

This you're seeing is a common DevOps issue when working with BC extensions. The pipeline is trying to download symbols for Avalara_Avalara AvaTax_26.0.28.1.app, but the response returns a 404, meaning the file is not found in the expected location.

Let’s move ahead with this:

1. Check Artifact Feed or App Source

Confirm that the .app file for Avalara AvaTax version 26.0.28.1 is present in your artifact feed, source repository, or local package folder.

If you're using a private NuGet feed or Azure Artifacts, make sure the app was published correctly and is accessible to the pipeline.

2. Verify Symbol Generation

Symbols are generated during packaging using alc.exe or Compile-AppInNavContainer.ps1.

If the .app was compiled without symbols (-DoNotGenerateSymbolFile), the pipeline won’t be able to resolve dependencies.

Rebuild the app with symbol generation enabled and republish it to the feed.

3. Check Dependency Declaration

In your app.json, ensure the Avalara AvaTax dependency is declared correctly with the exact name and version:
"dependencies": [ { "id": "Avalara_Avalara AvaTax", "publisher": "Avalara", "name": "Avalara AvaTax", "version": "26.0.28.1" } ]

4. Use Correct Container Image

If you're using a container, make sure the image includes the Avalara extension or that the .app is installed before symbol resolution.

You can use Get-BcContainerAppInfo to verify installed apps in the container.

5. Fallback: Remove Dependency Temporarily

If the extension is not critical for the current build, you can temporarily remove the dependency from app.json to allow the pipeline to proceed.

This is not recommended for production builds but can help isolate the issue.

Helpful Reference
Troubleshoot pipeline runs - Azure Pipelines | Microsoft Learn
navcontainerhelper/AppHandling/Compile-AppInNavContainer.ps1 at main · microsoft/navcontainerhelper · GitHub
Dynamics 365 Business Central: subfolding AL symbols

If you find this helpful, feel free to mark this as the suggested or verified answer.

Cheers
Jeffrey

1 people found this reply helpful.

Was this reply helpful? Yes No
Crishmin 25 on at

Like (0)

Report
Copy link

Link copied!

How can I install it in the container? In my scenario, the pipeline creates a container and installs Business Central. The Avalara extension is a third-party app available on AppSource.

Was this reply helpful? Yes No