Sa3client is not recognized as an internal or external command after upgrade to

Sa3client is not recognized as an internal or external command after upgrade to

Posted by: chris.eaton on 25 March 2026, 12:09 pm EST

• 

  chris.eaton

  • Post Options:
  • Link
    Copy
  • Jump To Answer

  Posted 25 March 2026, 12:09 pm EST

  Subject says it all. I upgraded from AR 18 to 20, migrated a project to AR 20 using the conversion tool, and now I get told that it can’t find sa3client when trying to build.

  Does this have to be installed separately?

  Thanks.

• 

  prabhat.sharma

  

  • Post Options:
  • Link
    Copy

  Posted 26 March 2026, 12:23 am EST

  Hello Chris,

  Thank you for reaching out to Mescius Support.
  
  This is quite strange as installing the latest version should install the sa3client automatically at your end. Please check if the tool is present or not at the following location on your machine:
  
  C:\ProgramData\SA3

  If it is present, please try activating your key as suggested here and cleaning and rebuilding your project:
  
  https://developer.mescius.com/activereportsnet/docs/developers/ar-how-licensing-activereports/licensing-developer-machine

  If it is not present, then you can use the following command to install the tool, and then follow the activation instructions:

  1. Run the command prompt or VS with Admin rights.
  2. Run the following command to install sa3Client:
     
     dotnet tool install -g sa3client

  If you face any issues, please create a case on our private portal and share the following information for further investigation:

  1. Are you facing this issue with the new project or with the existing sample?

  2. A screenshot of the activated licenses on your machine. [run sa3client list command]

  My support portal Link: https://developer.mescius.com/my-account/my-support

  Regards,
  
  Prabhat Sharma.

• 

  joachim

  • Post Options:
  • Link
    Copy

  Posted 29 March 2026, 1:40 pm EST - Updated 29 March 2026, 1:46 pm EST

  Hi,

  When I try to install the tool via commandline, I’m getting:

  Unhandled exception: Response status code does not indicate success: 401 (Unauthorized).

  Thank you,
  
  Joachim

• 

  prabhat.sharma

  

  • Post Options:
  • Link
    Copy

  Posted 29 March 2026, 11:31 pm EST

  Hello Joachim,

  Apologies for the inconvenience caused to you.
  
  This is a known issue when .NET CLI tries to contact any authenticated feed configured somewhere on your machine.

  You can check out the following public link to see how to resolve this issue:
  
  https://stackoverflow.com/questions/37956817/unauthorized-nuget-package-from-visual-studio-team-services-using-asp-net-core-r

  If you still face the issue, you can force the install to use only the public NuGet.org source:
  
  dotnet tool install -g sa3client --add-source https://api.nuget.org/v3/index.json

  If you still face any issues, please let us know.

  Regards,
  
  Prabhat Sharma.

• 

  chris.eaton

  • Post Options:
  • Link
    Copy

  Posted 30 March 2026, 8:23 am EST - Updated 30 March 2026, 8:23 am EST

  Hi. I have “sa3client-ui.exe” in c:\programdata\sa3 . It looks like visual studio is looking for sa3client.exe, which I don’t have.

  Installing it using dotnet tool did work. So the reports are working again now. I just find it strange that it had to be installed manually.