Recently I changed my password for TFS service and started facing below issue
Error encountered while fetching: Git failed with a fatal error.
Authentication failed for 'http://Path'.
- Worked fine with Visual Studio 2019 but failed with Visual Studio 2017
Things I tried to resolve this issue:
- Updated password in Credential Manager
- Clearing visual studio cache
Thanks for your help.
Update:
Instead of update password in Credential Manager try to remove it. When connect git in VS2017, you should be able to enter it again. More ways for troubleshooting, pleas take a look at weiwei's answer in this similar question Git failed with a fatal error.Authentication failed when clone repository from VS 2017
Besides, as a workaround, you could also try to use Personal Access Token and use that to connect directly. For details please refer https://stackoverflow.com/a/56028075/5391065
According to your description and situation, since it worked fine with VS2019 and not work with VS2017, this maybe with some Credential cache.
Make sure you have clean clear for the cache with Visual Studio 2017.
Besides, you could also try to run Visual Studio under sign-in credentials that are different from your signed-in Windows account, open the context menu for devenv.exe to access your run as options. If you don't see the run as option as shown in the following example, you may need to press SHIFT before right-clicking to see the run as options.
You can locate the executable in the following folder: *Drive*:\\Program Files (x86)\Microsoft Visual Studio xx.0\Common7\IDE\
Which may do the trick.
Close all Visual Studio instances.
Delete %LOCALAPPDATA%\.IdentityService.
If the issue still persist, call devenv /resetuserdata to clear user's data.
Related
On a Windows machine, I'm heavily using the "open folder in container" functionality of Visual Studio Code, with Docker managed by Rancher Desktop.
For this to work, I always run Visual Studio Code as administrator.
Since today, however, it doesn't work any more, and the "Docker returned an error code EACCES, message" is reported.
As a workaround, I changed the properties of
C:\Users\<userName>\AppData\Local\Programs\Rancher Desktop\resources\resources\win32\bin\Docker.exe
by unchecking the "Run this program as an administrator" checkbox:
This, however, seems to me not to be a good solution to the problem.
What is the proper way of fixing the issue?
In general, there is a website(ASP .NET MVC 5) that I run in Visual Studio.
The first time everything starts clearly, and if you restart the debug session, then the second time it does not start. If you look at the tray, then IIS Express is absent there.
Only restarting Visual Studio solves the problem, but again, only 1 time and you have to restart the studio each time.
What could be the problem?
This happened exactly to me when I upgrade a solution from VS 2010 to VS 2017.
I searched for solutions and only found: remove the .vs directory from the solution, remove the IIS Express directory from the documents or reinstall VS.
The problem was that the solution has multiple web projects that can run. And in one of them, in the .csproj, there was this configuration:
<UseIISExpress>false</UseIISExpress>
<UseIIS>False</UseIIS>
When I set it to true, the problem was gone.
Regards.
I am working on .Net core Microservices. I installed Docker Toolbox containing docker cli and kitematics. After that i created a simple (.Net core) web api project in visual studio 2017 and also enable docker support.
But when i hit F5 to run the program it shows following error and doesn't run.
Visual Studio Container Tools requires Docker to be running before building, debugging or running a containerized project.
Please review the attached image.
Visual studio error on running the project
If i build and run the project using docker cli, it's working. The problem is with visual studio 2017.
In my case I had an erroneous reference in Dependencies > Packages to Microsoft.VisualStudio.Azure.Containers.Tools.Targets
Removing the reference fixed the error.
The problem occurs because Visual studio container is unable to connect to docker for windows and solution for this is to open the visual studio 2017 from Docker CLI using following command.
/c/Program\ Files\ \(x86\)/Microsoft\ Visual\ Studio/2017/Community/Common7/IDE/devenv.exe C:\\PATH\\TO\\MY\\SOLUTION.sln
Here:
C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\Common7\IDE\devenv.exe
is the location of my devenv.exe file and 2nd parameter
C:\\PATH\\TO\\MY\\SOLUTION.sln
shows the path of solution file.
For further details of this solution, click Here.
In my case, this issue was caused by a disabled BIOS Virtualization. To enable Virtualization, see here. In order to check whether Virtualization is already enabled, start Task Manager > Performance > find Virtualization. If you are hosting your docker container application in full feature IIS, make sure you start Visual Studio as an Administrator.
I was getting the same error when I was trying to rebuild my solution after changing my .Net Core 2.0 application to .Net Core 2.2. As I reset my windows, there was no docker installed on my machine. To fix this all I had to do is to install the docker for desktop as I wanted to containerize my applications.
Once you install the Docker, it will ask you to enable Hyper-V and Container features. By clicking the Ok button in the pop up as preceding, will enable this features for you.
Your computer will be restarted automatically and once it is done, you should be able to see that the Virtualization is enabled in the task bar.
After this I was not facing this error.
Check shared folders inside the default virtual machine setting in Virtual box to make sure you shared the disk where you project located. By default shared only C:\Users. So alternatively you can move your project somewhere inside C:\Users folder (for example in Desktop folder)
I was facing the same issue and I resolved it by switching to IIS Express instead of Docker in debug menue on visual studio 2017
I have Jenkins CI server which builds various .net projects. The server is on Virtual Machine, connected to ActiveDirectory and Jenkins is running in the context of domain user which is also a local administrator.
Software used:
Windows 10 Professional
Visual Studio 2015 14.0.25431.01 Update 3
Jenkins 1.625.3
Solutions are build using devenv.com (currently msbuild is not an option), e.g.:
"C:\Program Files (x86)\Microsoft Visual Studio 14.0\Common7\IDE\devenv.com" "xxxxx.sln" /rebuild "Release|Any CPU"
My issue is, that quite often I receive an error, just after running devenv.com:
Microsoft Visual Studio has detected a configuration issue. To correct this, please restart as Administrator. For more information please visit: http://go.microsoft.com/fwlink/?LinkId=659046Build
It started to happen after one of Windows 10 updates. I found out, that when someone is log in to build server with the remote desktop using the same domain account, the builds run OK. After logout, the builds run OK for some time and then the errors are back.
Any clue what's going on?
It may be related to this apparent bug in a recent Windows update:
Connect: Visual Studio 2015 and SSMS 2016 RTM (VS 2015 shell) not running under "Run as different user" on Windows 10 Anniversary, Windows 2016 CTP 5
UPDATE 2017-09-08
As #Florian points out, the above link is broken. I can't even find the Connect issue cached on Google, Bing or archive.org.
The Connect issue Unable to start SSMS as another user (cached copy on archive.org) makes me think it would be worth checking whether the problem resolves after updating Windows 10 to 1703 (Creators Update) and ensuring that April 25, 2017—KB4016240 (OS Build 15063.250) has been applied. If this works, anyone running Jenkins on Windows Server 2016 will have to wait for Microsoft to publish 1703 and KB4016240 (or equivalent) for that OS.
Excerpts from Connect page "Unable to start SSMS as another user". I have bolded the error details, which match those in the original question (except for the LinkId in the supplied URL) even though the product is SSMS rather than VS:
Version: SQL Server 2016 CTP3
Operating System: Windows 10
Steps to Reproduce:
Right-click SQL Server Management Studio, select "More", then "Run as
a different user"
Actual Results:
Error message: "This task requires the application to have elevated
permissions" with two options: Restart under different credentials,
and Cancel the task and return to Microsoft SQL Server Management
Studio. Pressing either option closes the window with no further
result. Error information is:
Microsoft SQL Server Management Studio has detected a configuration issue. To correct this, please restart as Administrator. For more information please visit: http://go.microsoft.com/fwlink/?LinkId=647011.
When I go to that page and try the fix suggested there, I can't find
ieproxy.dll. The fix is for Windows 7 / Internet Explorer 8, and I'm
on Windows 10 with Internet Explorer 11, so that may be why it's not
there.
[...]
Posted by Microsoft on 4/28/2017 at 6:26 PM
Hi Jake, It turned out that this issue has been resolved (on the Windows side) very recently - like 3 days ago :)
If you are running Win10 "1703", just make sure you get the latest
updates (specifically, KB4016240) and you should be able to run
ssms.exe using "runas" just fine. This will work with any version of
SSMS.
Currently, the fix is not available on older versions of Win10 (e.g.
1607) or WS2016 (also 1607).
Thanks,
-Matteo
[...]
Posted by Microsoft on 4/27/2017 at 7:35 PM
Hi Jake, Yes, we are aware of this issue (in Windows 10).
We've engaged with the Visual Studio and Windows folks (which is there
the issue is) and hopefully will have a way to fix this issue in SSMS
(you should not need an updated SSMS, just an update in Windows 10).
I'm going to keep this issue open until I have more concrete updates
on it.
Thanks,
-Matteo
If the Windows updates do not solve the problem or are not available to you, I would suggest trying repair operations on Windows as well as Visual Studio.
I'm running into the same error after updating my Windows 10 to 1607, in that I cannot run Visual Studio as a different user. I'm not building solutions at the time though, but still running the VS program as I think you would be calling.
Using this command: runas /netonly /user:domain \ account devenv.exe
as outlined here Unable to launch Visual Studio 2015 as a different user works for me. Not as convenient but does the trick.
Quick background. My client uses Visual Studio 2010 for their website. It was ported onto a new machine, and I had to do some extensive work to get all of the 3rd party controls and add-ons to work. They then requested source control, so using their MSDN license I pulled down and installed TFS 2012 on their machine. Everything installed correctly, and seemed to work until I went to add the existing VS2010 project to TFS2012, and I got an error that when traced back, basically told me that I would not be able to use TFS 2012 and VS2010 together. I weighed the choices, updating the project to VS2012, or uninstalling TFS 2012 and installing TFS2010, and decided the TFS route was the way to go, as I did not want to screw around with all the add-ons again. TFS2012 uninstalled fine, and TFS2010 installed fine.
When I went to start configuring TFS2010, I got an error ([ Application Tier ] TF255297: The Web site found has bindings that conflict with the bindings chosen for the Web site for Team Foundation Server. You must manually resolve the conflict between the bindings.) basically telling me the binding were not removed for the TFS2012 install. I looked in IIS and there is nothing in there using port 8080.
So my question is, how do I find out where the bindings are in use. I tried the netstat commands, and did not find anything using port 8080. I am kind of dead in the water here, so any help that is offered would be greatly appreciated.