![]() Once source tree has generated a new key the save option is still greyed out. It will ask for a pass phrase which can be whatever and will never ask for it again and then sometimes brings up another window where you’ll have to type your atlassian password. Hold option to change the button (where copy to clipboard usually is) to show generate new bit bucket key, with option held click that new button. ![]() Then in sourcree accounts it reverts to another. The way I do this is by searching for a folder in finder (shift + command + g) ~/.ssh/ and delete the bitbucket files. On my Mac for the past 3 or 4 weeks I have had to reset my. Then I asked my credentials and it all suddenly worked again, creating a new passwd file. I renamed the file C:\Users\USER\AppData\Local\Atlassian\SourceTree\passwd. But I did not have other installation files.įinally I found this post which saved my day, after hours of frustration. I was thinking of reinstalling an old version of Sourcetree, assuming some automatic update had messed things up.After which they SEEMED to be copied from the ones checked in Visual Studio. Why are there 2 right away with a single repository anyway? Resulting in a bunch of saved passwords with different names. I suddenly had authentication problems while contacting a remote git repository from Sourcetree, possible initiated by a password change on Windows.Ĭontacting over a web interface and from Visual Studio did WORK.īut trying all sorts things within Sourcetree did NOT change a damn thing. So here we are in 2022, and these problem are still present! I might have entered the wrong password, but didn't see any problems at that time (I haven't pushed/pulled since then, so wouldn't have seen any problems until today). I'm not sure why it stopped working (I haven't changed my VSTS password and all my private access tokens are still valid), but I seem to recall an odd password box that popped up a week or so ago that I believe came from SourceTree. origin server is Visual Studio Team Services I saw a similar question that mentioned " There is a SourceTree Application password stored in the login keychain." But I have no idea what the login keychain is or how I can fix it in SourceTree. I've updated my Git username every place I've been able to see something that resembles a username, I've gone to Tools > Options > Authentication > and set the password (which is a private access token). However, nothing I've tried will allow me to use the push/pull buttons in SourceTree. The Git terminal from SourceTree asks for my username/password and, when I enter it, it works correctly (I'm able to do a push/pull anyway). You can use the SysInternals MoveFile tool for that.In SourceTree, I'm getting the "fatal: Authentication failed for." error when I try to Push/Pull from origin. If you cannot find any process accessing the file, or closing them all still results in an access denied error, and you are definitely trying the deletion from an elevated command prompt, then you might want to try telling Windows to delete the file the next time it is rebooted. If you think it's a service, hover the mouse over it and a tooltip will appear telling you the name(s) of any services it is running.) ![]() (Ensure View->Show Processes for All Users is ticked, then find the process in question via the PID column. If it's a process running as another user/account, it might be a service which you can stop. If one or more processes are listed, confirm the full file path in the list (in case some other file on disk has a similar name).Ĭlose any processes which have the file open. The command prompt should say "Administrator:" in its window title if it is properly elevated, unless UAC is off entirely. If you just changed to an admin account, but didn't use "Run as Administrator" on the command prompt, then that could be why the takeown command failed. ![]() I assume you're already familiar with this from running the command prompt as admin. Right-click procmon.exe and choose the "Run as Administrator" option. Windows 7's UAC means Administrator accounts don't run things with full admin access by default. I don't just mean when logged in as Administrator. ![]() If that's not the case then I may be wrong.)Īs a first step, run Process Explorer as Administrator and push Ctrl-F to open a window where you can type the filename and see which processes (if any) have that file open. (I'm assuming GIT is like SVN where every file in the repository is created by your own account with standard permissions. An access denied error may mean the file is in use by another process and, for a GIT repository, that seems more likely than a file permissions issue. ![]()
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |