Visual Studio 2017 can't connect to TFS 2017: LoadCachedCredentialsFormRegisterdProviders Method not found
We are using Visual Studio 2017 & TFS 2017.
I have access to TFS web portal & TFS server (remote, share, db,..) & ... and everything works, but I can't connect with Visual Studio (just in my pc).
Error is:
Server 'http://tfs:8080/tfs' was not added.
Method not found:
'Microsoft.VisualStudio.Services.Common.VssCredentials
Microsoft.VisualStudio.Services.Common.VssCredentials.LoadCachedCredentialsFromRegisteredProviders(System.Uri, Boolean ByRef)'.
- Firewall is Off
- Antivirus is Disable
- Remove All Credentials in Credential Manager
- Check port access with telnet
- VS Version is 15.5.6
- TFS Version is 15.117.26714.0
Any advice?
Screenshot
visual-studio tfs
|
show 3 more comments
We are using Visual Studio 2017 & TFS 2017.
I have access to TFS web portal & TFS server (remote, share, db,..) & ... and everything works, but I can't connect with Visual Studio (just in my pc).
Error is:
Server 'http://tfs:8080/tfs' was not added.
Method not found:
'Microsoft.VisualStudio.Services.Common.VssCredentials
Microsoft.VisualStudio.Services.Common.VssCredentials.LoadCachedCredentialsFromRegisteredProviders(System.Uri, Boolean ByRef)'.
- Firewall is Off
- Antivirus is Disable
- Remove All Credentials in Credential Manager
- Check port access with telnet
- VS Version is 15.5.6
- TFS Version is 15.117.26714.0
Any advice?
Screenshot
visual-studio tfs
Seems it's the VS issue, try to repair VS, or reset user data :C:Program Files (x86)Microsoft Visual Studio2017EnterpriseCommon7IDEdevenv.exe /resetuserdata
. It that still not work, just try to install the standalone Team Explorer 2017, then try it again.
– Andy Li-MSFT
Feb 20 '18 at 3:33
I tried all of that!!
– Shahram Vafadar
Feb 21 '18 at 12:36
I try VS 2015 and can be connected without problem!
– Shahram Vafadar
Feb 21 '18 at 13:07
So, it proves that it's an issue with the installation of VS 2017. I tested on my side, can not reproduce this issue. You can check if this issue occurs on other machines, also try to uninstall it completely then reinstall.
– Andy Li-MSFT
Feb 22 '18 at 1:54
I try that. Uninstall > Restart > Install. I probably have to reinstall Windows.
– Shahram Vafadar
Feb 24 '18 at 8:48
|
show 3 more comments
We are using Visual Studio 2017 & TFS 2017.
I have access to TFS web portal & TFS server (remote, share, db,..) & ... and everything works, but I can't connect with Visual Studio (just in my pc).
Error is:
Server 'http://tfs:8080/tfs' was not added.
Method not found:
'Microsoft.VisualStudio.Services.Common.VssCredentials
Microsoft.VisualStudio.Services.Common.VssCredentials.LoadCachedCredentialsFromRegisteredProviders(System.Uri, Boolean ByRef)'.
- Firewall is Off
- Antivirus is Disable
- Remove All Credentials in Credential Manager
- Check port access with telnet
- VS Version is 15.5.6
- TFS Version is 15.117.26714.0
Any advice?
Screenshot
visual-studio tfs
We are using Visual Studio 2017 & TFS 2017.
I have access to TFS web portal & TFS server (remote, share, db,..) & ... and everything works, but I can't connect with Visual Studio (just in my pc).
Error is:
Server 'http://tfs:8080/tfs' was not added.
Method not found:
'Microsoft.VisualStudio.Services.Common.VssCredentials
Microsoft.VisualStudio.Services.Common.VssCredentials.LoadCachedCredentialsFromRegisteredProviders(System.Uri, Boolean ByRef)'.
- Firewall is Off
- Antivirus is Disable
- Remove All Credentials in Credential Manager
- Check port access with telnet
- VS Version is 15.5.6
- TFS Version is 15.117.26714.0
Any advice?
Screenshot
visual-studio tfs
visual-studio tfs
edited Feb 19 '18 at 11:34
RobC
6,51392539
6,51392539
asked Feb 19 '18 at 11:24
Shahram VafadarShahram Vafadar
396
396
Seems it's the VS issue, try to repair VS, or reset user data :C:Program Files (x86)Microsoft Visual Studio2017EnterpriseCommon7IDEdevenv.exe /resetuserdata
. It that still not work, just try to install the standalone Team Explorer 2017, then try it again.
– Andy Li-MSFT
Feb 20 '18 at 3:33
I tried all of that!!
– Shahram Vafadar
Feb 21 '18 at 12:36
I try VS 2015 and can be connected without problem!
– Shahram Vafadar
Feb 21 '18 at 13:07
So, it proves that it's an issue with the installation of VS 2017. I tested on my side, can not reproduce this issue. You can check if this issue occurs on other machines, also try to uninstall it completely then reinstall.
– Andy Li-MSFT
Feb 22 '18 at 1:54
I try that. Uninstall > Restart > Install. I probably have to reinstall Windows.
– Shahram Vafadar
Feb 24 '18 at 8:48
|
show 3 more comments
Seems it's the VS issue, try to repair VS, or reset user data :C:Program Files (x86)Microsoft Visual Studio2017EnterpriseCommon7IDEdevenv.exe /resetuserdata
. It that still not work, just try to install the standalone Team Explorer 2017, then try it again.
– Andy Li-MSFT
Feb 20 '18 at 3:33
I tried all of that!!
– Shahram Vafadar
Feb 21 '18 at 12:36
I try VS 2015 and can be connected without problem!
– Shahram Vafadar
Feb 21 '18 at 13:07
So, it proves that it's an issue with the installation of VS 2017. I tested on my side, can not reproduce this issue. You can check if this issue occurs on other machines, also try to uninstall it completely then reinstall.
– Andy Li-MSFT
Feb 22 '18 at 1:54
I try that. Uninstall > Restart > Install. I probably have to reinstall Windows.
– Shahram Vafadar
Feb 24 '18 at 8:48
Seems it's the VS issue, try to repair VS, or reset user data :
C:Program Files (x86)Microsoft Visual Studio2017EnterpriseCommon7IDEdevenv.exe /resetuserdata
. It that still not work, just try to install the standalone Team Explorer 2017, then try it again.– Andy Li-MSFT
Feb 20 '18 at 3:33
Seems it's the VS issue, try to repair VS, or reset user data :
C:Program Files (x86)Microsoft Visual Studio2017EnterpriseCommon7IDEdevenv.exe /resetuserdata
. It that still not work, just try to install the standalone Team Explorer 2017, then try it again.– Andy Li-MSFT
Feb 20 '18 at 3:33
I tried all of that!!
– Shahram Vafadar
Feb 21 '18 at 12:36
I tried all of that!!
– Shahram Vafadar
Feb 21 '18 at 12:36
I try VS 2015 and can be connected without problem!
– Shahram Vafadar
Feb 21 '18 at 13:07
I try VS 2015 and can be connected without problem!
– Shahram Vafadar
Feb 21 '18 at 13:07
So, it proves that it's an issue with the installation of VS 2017. I tested on my side, can not reproduce this issue. You can check if this issue occurs on other machines, also try to uninstall it completely then reinstall.
– Andy Li-MSFT
Feb 22 '18 at 1:54
So, it proves that it's an issue with the installation of VS 2017. I tested on my side, can not reproduce this issue. You can check if this issue occurs on other machines, also try to uninstall it completely then reinstall.
– Andy Li-MSFT
Feb 22 '18 at 1:54
I try that. Uninstall > Restart > Install. I probably have to reinstall Windows.
– Shahram Vafadar
Feb 24 '18 at 8:48
I try that. Uninstall > Restart > Install. I probably have to reinstall Windows.
– Shahram Vafadar
Feb 24 '18 at 8:48
|
show 3 more comments
1 Answer
1
active
oldest
votes
I recently ran into this issue and after hours and hours of searching on the Internet, I found a post suggesting to install the Microsoft.TeamFoundationServer.ExtendedClient package from Nuget. I added this package to the project that connected to the TFS server and the error went away.
I should note that I tried pretty much everything else I found, including reinstalling VS2017 on my original machine, then installing VS2017 on a fresh VM and getting the same exact error.
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f48865136%2fvisual-studio-2017-cant-connect-to-tfs-2017-loadcachedcredentialsformregisterd%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
1 Answer
1
active
oldest
votes
1 Answer
1
active
oldest
votes
active
oldest
votes
active
oldest
votes
I recently ran into this issue and after hours and hours of searching on the Internet, I found a post suggesting to install the Microsoft.TeamFoundationServer.ExtendedClient package from Nuget. I added this package to the project that connected to the TFS server and the error went away.
I should note that I tried pretty much everything else I found, including reinstalling VS2017 on my original machine, then installing VS2017 on a fresh VM and getting the same exact error.
add a comment |
I recently ran into this issue and after hours and hours of searching on the Internet, I found a post suggesting to install the Microsoft.TeamFoundationServer.ExtendedClient package from Nuget. I added this package to the project that connected to the TFS server and the error went away.
I should note that I tried pretty much everything else I found, including reinstalling VS2017 on my original machine, then installing VS2017 on a fresh VM and getting the same exact error.
add a comment |
I recently ran into this issue and after hours and hours of searching on the Internet, I found a post suggesting to install the Microsoft.TeamFoundationServer.ExtendedClient package from Nuget. I added this package to the project that connected to the TFS server and the error went away.
I should note that I tried pretty much everything else I found, including reinstalling VS2017 on my original machine, then installing VS2017 on a fresh VM and getting the same exact error.
I recently ran into this issue and after hours and hours of searching on the Internet, I found a post suggesting to install the Microsoft.TeamFoundationServer.ExtendedClient package from Nuget. I added this package to the project that connected to the TFS server and the error went away.
I should note that I tried pretty much everything else I found, including reinstalling VS2017 on my original machine, then installing VS2017 on a fresh VM and getting the same exact error.
answered Nov 21 '18 at 1:32
Robert YarbroughRobert Yarbrough
1
1
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f48865136%2fvisual-studio-2017-cant-connect-to-tfs-2017-loadcachedcredentialsformregisterd%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Seems it's the VS issue, try to repair VS, or reset user data :
C:Program Files (x86)Microsoft Visual Studio2017EnterpriseCommon7IDEdevenv.exe /resetuserdata
. It that still not work, just try to install the standalone Team Explorer 2017, then try it again.– Andy Li-MSFT
Feb 20 '18 at 3:33
I tried all of that!!
– Shahram Vafadar
Feb 21 '18 at 12:36
I try VS 2015 and can be connected without problem!
– Shahram Vafadar
Feb 21 '18 at 13:07
So, it proves that it's an issue with the installation of VS 2017. I tested on my side, can not reproduce this issue. You can check if this issue occurs on other machines, also try to uninstall it completely then reinstall.
– Andy Li-MSFT
Feb 22 '18 at 1:54
I try that. Uninstall > Restart > Install. I probably have to reinstall Windows.
– Shahram Vafadar
Feb 24 '18 at 8:48