Getting Select Action error while using Visual Studio - visual-studio

I am getting the below alert on a certain interval while using VS Code have attached the SS of the same. Using VS for quite sometime but never encountered this issue before. Please help me to resolve the issue.

I was in trouble with the same issue recently. You can resolve it by simply granting full access to all users or running the vscode as an administrator. (This question was answered already. You can get more information from Visual Studio Code - access denied to unins000.exe)

Related

Visual Studio is unable to retrieve the service 'Microsoft.VisualStudio.WindowsAzure.Authentication.IAzureRMTenantService'

When i click Deploy, I get below error:
Visual Studio is unable to retrieve the service 'Microsoft.VisualStudio.WindowsAzure.Authentication.IAzureRMTenantService'
With just this error message , we will not be able to troubleshoot .
Someone from the community also reported the same issue , and he was able to resolve this issue by doing below work around
Workaround is to Sign out of Visual Studio by resetting the complete data. Once logged into Windows, launch Visual Studio - DO NOT SIGN IN. Open the solution, right click on the Deployment project. it should work.
here is a similar thread on the same issue:
https://social.msdn.microsoft.com/Forums/azure/en-US/3ce280c2-2ad8-4627-be6a-fba9dbb3c835/systeminvalidoperationexception-user-account-needs-to-be-authenticated-before-calling?forum=windowsazurewebsitespreview
Though the team is right now focusing on to resolve major issue with higher customer impact, if the workaround doesn't work for you, i would suggest you to report this issue in forum. you can see the details here
https://learn.microsoft.com/en-us/visualstudio/ide/report-a-problem?view=vs-2017#faq
also please provide as much detail as possible, it will help us to resolve the issue quickly.

Package management initialization failed: Access Denied Error when opening Visual Studio 2017

I'm getting the following error when opening VS 2017 on Windows 7 64-bit:
Package management initialization failed: Access Denied.
You can get more information by examining the file:
C:\Users\<username>\AppData\Roaming\Microsoft\VisualStudio\15.<version>\ActivityLog.xml
It all started after I added my solution to SVN. I had no problems until I tried to add a file and got the following error:
Value does not fall within the expected range
I followed the steps mentioned in this answer and did a 'devenv /setup', after that I started getting the Package management initialization failed: Access Denied. error when opening VS. Now Visual Studio doesn't even start.
Has anyone else experienced this problem and resolved it?
Edit:
I tried starting as an administrator and it worked. But otherwise it doesn't.
It turns out that this is a bug, that hasn't yet been resolved. This error also occurs when starting Visual Studio after an update.
But there is a workaround from this thread that worked for me,
Delete the privateregistry.bin file from the following folder:
C:\users\%username%\Appdata\Local\Microsoft\VisualStudio\15.0_<version id>\
This is however a temporary fix and resets the user's preferences. That's why it worked when I started it as an administrator, since the problem is user specific.
Update
This bug is supposedly fixed in the latest versions of Visual Studio. But for the bug fix to work, the old privateregistry.bin file still needs to be deleted.
#Xpleria, the answer works fine. To open the AppData folder, you can type:
%AppData%
directly in the Address bar.
https://support.pointlogic.com/faq/troubleshooting/accessing-the-appdata-folder
I had this issue after installing SSDT for VS 2017 in a new vs instance.
So it's like I have two visual studio in my machine.
To fix that, I uninstalled the SSDT package, restart my machine and reinstall it on the initial installed visual studio instance.
I had the same problem and when I looked at
C:\Users\UserName\AppData\Local\Microsoft\VisualStudio
I noticed that I had miltiple versions of visual studio meaning the current update might not have been successfull, as I was not able to delete the file that #Neil Patro says, I simply deleted the entire updates and all was ok.
I guess adding this as an answer might help.
Happened to me with an existing VS instance running, where I disabled an extension (VsChromium). Closing all VS instances solved the error and VS starts normally.
Env: VS 2019 Pro, Win 10 x64, running as current user.

Visual Studio error could not refresh credentials

Hi everyone this is my first post. I am having a major problem with visual studio I cannot log in to extend my 30 day trial period and have no access to using visual studio. So here is what is happening exactly I have been using visual studio 2017 community version for 30 days as a trial, they want me to log in to extend the use of visual studio but I get an error for almost everything. I will show some screenshots as to what specific errors.
Specific error with vs
So those are my errors and like anyone else here would do I have tried multiple ways to fix this myself. Here is what I have done.
I have gone into .Identityservice and cleared the cache that was there(there are multiple different forums and such detailing which cache to delete I only had one in the appdata/local/.identityservice which was IdentityServiceAdalCache.cache)
I have tried to go around going into the visual studio installer then to report a problem to sign into the developer community, it will let me sign in however as soon as I am done signing it is says that I have logged out and need to refresh my credentials which is why I cannot post on the developer community directly as well.
three clean reinstalls
repair option in installer
tried to see if updating would help
One more thing is that since visual studio provides error logs I have one here(or most of it anyway)
error log
I would really appreciate any help I can get, I have scoured the internet looking for answers but haven't been able to find much. Hopefully I have provided enough information. Thank you.

Visual Studio 2017 HRESULT: 0x80070005 / E_ACCESSDENIED on project creation

I'm running Visual Studio 2017, version 15.0.0+26228.9
When I'm trying to create a new project via File > New > Project... in Visual Studio 2017, I'm receiving the following error message and the project is not created:
Access denied (Exception from HRESULT: 0x80070005 (E_ACCESSDENIED))
Don't mind the german message text in the screenshot:
This happens for every project template I use (e.g. C# WPF, VB WPF, C# Console App...).
If I try to create a project via the quick search box on the starting page of visual studio, VS just crashes instantly with no exception message at all:
Has anybody else ran into this issue and might know how to fix it?
I had the same error.
I solved it by following the procedure :
Shutdown all instances of Visual Studio
Delete %LocalAppData%\Microsoft\VisualStudio\15.0_f4938f75\privateregistry.bin file (the ID after 15.0_ may be different per machines)
Start VS as normal user
all credit for this should go to https://developercommunity.visualstudio.com/content/problem/31188/access-denied-error-1.html
Ok, I fixed it.
Long story short, the reason for the problem was an incomplete and/or corrupted setup.
But it was a rather bumpy road to the solution, including several un-installations and re-installations until I eventually figured out why the setup was indeed faulty.
Sometimes I got an exception during the installation, other times it finished just fine, but the HRESULT-error persisted when I tried to create a new project.
I my special case, this was caused by the corporate firewall, that blocked some of the setup packets from being downloaded by the web installer. I solved the issue by connecting to an open WiFi, that's not filtered by the firewall.
As I'm working with a standard user, UAC kicks in when I start any installation routine. When I first started the setup via UAC and connected to the free WiFi, it wasn't able to find the packet servers.
It took me a minute to realize that the admin user I used for UAC had his own internet proxy settings, that wouldn't work with the open WiFi.
After I logged on as administrator, disabled the proxy and logged on as my main user again, I ran the setup again - and it failed again with a bunch of "incomplete workload" messages. As frustrated as I was at this point, I simply ran it again via the "Change" button without even closing the webinstaller and this time it finally completed without any errors!
After this, I could start VS just normally and creation of a new project was possible.
So, if you experiencing any troubles like this, I would strongly recommend to run a "Repair" or "Change" installation just over your existing one but try to avoid any firewalls between you and the internet.
1/ open control panel -> program and future - > IIS Express -> select Repair
2/ Refresh some time -> open Visual Studio
This 's about IIS Express in your computer . you only need to repair it in control panel is ok .
I tried and success.
My solution,
The Clang-format caused this. just disable clang-format:
Options->Text Editor->C/C++->Formatting->General->Eable ClangFormat Support
I had the same error when I tried to create a test certificate.
I have just launched VS as administrator.
And everything is Ok
The below solution worked for me
Make sure all the instances of Visual studio are closed.
Go to %LocalAppData%\Microsoft\VisualStudio\15.0_****
Delete the file privateregistry.bin
I tried changing the version of .Net Framework from 4.0 to 3.5 while creating the project. This solved my error.
enter image description here
Changing version of Net Framework

Error when generating database from model in Visual Studio 2013

I have installed VS2013 but still have VS2012. In VS2013 I cannot generate a database from a model in Entity Framework. I get the following error message:
The files in the error message do exist!
Does anyone have any idea how I can fix this?
Your tip about checking the drive made me see what I should have seen before.
The environment variable VS120COMNTOOLS had the wrong drive letter. Can't remember, but I initially installed VS2013 on another drive and then changed it back to C. Anyway setting it correctly fixed the problem.
/Peter
I believe VS is not updating the VS120COMNTOOLS variable correctly when reinstalling VS to a different drive. See this SO thread for an extended answer.

Resources