Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

dotnet tool install fails without explanation on dotnet 6 #679

Closed
carlin-q-scott opened this issue Aug 8, 2022 · 2 comments
Closed

dotnet tool install fails without explanation on dotnet 6 #679

carlin-q-scott opened this issue Aug 8, 2022 · 2 comments

Comments

@carlin-q-scott
Copy link

When I try to install the dotnet cli tool globally

dotnet tool install --global dotnet-script

I get this response:

Failed to install tool package 'dotnet-script': Access to the path 'C:\Users\me.dotnet\tools.store.stage\yz1gqtsw.afe' is denied.
Tool 'dotnet-script' failed to install. This failure may have been caused by:

  • You are attempting to install a preview release and did not use the --version option to specify the version.
  • A package by this name was found, but it was not a .NET tool.
  • The required NuGet feed cannot be accessed, perhaps because of an Internet connection problem.
  • You mistyped the name of the tool.

For more reasons, including package naming enforcement, visit https://aka.ms/failure-installing-tool

  • I installed dotnet-ef globally without issue.
  • I've deleted my tools folder to see if that was the issue, and it was not.
  • I watched the .stage folder during install and it did indeed download and extract the nuget package before failing and deleting the folder.

dotnet --version 6.0.302
dotnet nuget --version 6.2.1.7

@filipw
Copy link
Member

filipw commented Feb 1, 2023

I am sorry you are running into this but this is a bug in https://github.com/dotnet/sdk and not related to the tool.
It was previously mentioned that this might be due to intermittent problems with Nuget dotnet/sdk#9381 (comment)

@carlin-q-scott
Copy link
Author

They have indeed fixed this issue.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants