Fix 401 Unauthorized on sa3client install- private Azure DevOps feed

Fix 401 Unauthorized on sa3client install- private Azure DevOps feed

Posted by: enrique.pv-ext on 13 October 2026, 6:27 am EST

• 

  enrique.pv-ext

  • Post Options:
  • Link
    Copy

  Posted 13 October 2026, 6:27 am EST

  Please, can you fix your tools (ComponentOne Control panel and extension MESCIUS for create runtime license in VS 2022) for “The 401 Unauthorized on sa3client install”

  Install using default public nuget feed:
  
  dotnet tool install -g sa3client --add-source https://api.nuget.org/v3/index.json

  You say:
  
  "A 401 from dotnet tool install usually means dotnet is using a NuGet source that needs credentials, such as a private Azure DevOps feed defined in a nuget.config, instead of nuget.org. Please run this on your partner’s machine and share the output:

  dotnet nuget list source
  
  Then try installing from nuget.org explicitly, from a folder that has no nuget.config:

  dotnet tool install -g sa3client --add-source https://api.nuget.org/v3/index.json
  
  After it installs, make sure ‘%USERPROFILE%.dotnet\tools’ is in your PATH, then reopen VS 2022 and the command prompt. Run ‘sa3client list’ and share its output too."

  please, can be fix it for avoid do it manually ? there are another partners that will activate and generate runtime license sa3licx in project…for avoid this error confusing.

  Thanks friends !!

• 

  uttkarsh.matiyal

  

  • Post Options:
  • Link
    Copy

  Posted 14 October 2026, 12:08 am EST

  Hello Enrique,

  This seems similar to your other Forum thread we recently responded: Working with Git and Developer Licenses, .sa3licx file VS 2022

  The 401 does not come from sa3client or the nuget.org feed. It comes from the nuget.config in your repository. That file clears the default sources and adds the private CommonBIDll feed on Azure Artifacts. When dotnet tool install runs from inside the repo folder, NuGet also queries that feed, and it returns 401 because it needs credentials. Because of this, the --add-source option I suggested earlier does not help from inside the repo. It adds a source, but it does not remove the ones from nuget.config. Sorry for the confusion on that.

  To avoid the error on your partners’ machines, one of the following should work:

  • Run the install from a folder outside the repository, for example “C:”:

  dotnet tool install -g sa3client
  

  • If you need to run it from inside the repo, skip the failing feed:

  dotnet tool install -g sa3client --ignore-failed-sources
  

  • Or sign in to the Azure Artifacts feed with the Azure Artifacts Credential Provider, so the private feed no longer returns 401.

  sa3client is installed globally, so this only needs to be done once per machine. After that, make sure %USERPROFILE%.dotnet\tools is in PATH, reopen VS 2022, and run sa3client list to confirm.

  Regarding your request to fix this in the License Manager and the Visual Studio extension: we’re sorry but the 401 is caused by the private feed in your repository’s nuget.config, not by sa3client or nuget.org, so it is not something that can be changed on the product side.

  Regards,
  
  Uttkarsh