Skip to content
This repository has been archived by the owner on Nov 6, 2020. It is now read-only.

TFS 2017 on premise #65

Closed
Lawrence-Brad opened this issue Jan 4, 2017 · 7 comments
Closed

TFS 2017 on premise #65

Lawrence-Brad opened this issue Jan 4, 2017 · 7 comments
Labels

Comments

@Lawrence-Brad
Copy link

Lawrence-Brad commented Jan 4, 2017

We have TFS 2017 on premise and I am not able to sign in. It says I am unauthorized, to check my credentials and to try again. I've tried multiple times, but it won't connect. I am trying to connect with the Visual Studio Team Services extension which states that it should work with TFS 2015 Update 2 and later.

@jeffyoung
Copy link
Contributor

HI @LawrenceBr.

I'd like to know if you could retry with some diagnostic logging enabled? The authentication actually happens in the vsts-node-api package (which the vsts-vscode extension uses to communicate to TFS/Team Services) and I don't think there's any logging there. However, we might get something that'll help. If you're interested, here's how you can enable it and get the log file I'll need.

In addition, are you attempting to access the server with HTTP or HTTPS?

@Lawrence-Brad
Copy link
Author

Lawrence-Brad commented Mar 3, 2017 via email

@jeffyoung
Copy link
Contributor

Hi @LawrenceBr. It appears you must have replied to the GH email with the logs. I didn't get the attachments in the mail but you can send them to me at jeyou at microsoft dot com. Thanks!

@dsolodow
Copy link

Having the same issue; extension version 1.116.0, Code version 1.11.1, TFS version 2017 Update 1.
Log file attached.

team-extension.txt

@dsolodow
Copy link

Still present in 1.116.1 it seems. :(

@jeffyoung
Copy link
Contributor

Thanks for the log file earlier @dsolodow. After taking a look at it, I see that you're attempting to connect to the TFS server via HTTPS. I've been tracking that issue at #59 and should be able to have a look at it soon.

Thanks for letting me know that you're using TFS 2017 U1. That's helpful.

@jeffyoung
Copy link
Contributor

With regards to HTTPS, I just pushed a change in v1.119.0 that should help connections to on-prem servers using HTTPS. If you're still interested, I'd be happy for you to try it out (if you haven't already).

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

No branches or pull requests

3 participants