Connect TFS 2017 create external TFS connection for TFS 2013 - http-status-code-401

How can I add an external TFS Connection to TFS 2017 to allow it to connect to TFS 2013?
I navigated to http://tfsserver:8080/tfs/collection/team_project_name/_admin/_services?_a=resources and clicked New Service Endpoint. I selected External TFS
When I go to verify the connection after entering all the relevant information, I get the below error.
Failed to query service endpoint api: http://tfsserver:8080/tfs/collection/_apis/projects. Error Message: The remote server returned an error: (401) Unauthorized..
Here is a screenshot of the error.
The odd thing is that if I make a GET request to http://tfsserver:8080/tfs/collection/_apis/projects without any authentication I get a 200 OK response back with project information.
I have configured basic authentication per the tfs cli guide. How can I verify that basic authentication is configured correctly? When I try to login with tfx, I get the following screen.
I have the following extensions installed on the TFS 2017 instance.
Package Management
Release Management Utility tasks
TFS artifacts for Release Management
I am using Microsoft Visual Studio Team Foundation Server Version 15.105.25910.0

According to the screenshot, you are using TFS artifacts for Release Management extension to connect to another TFS instance.
Make sure the things below:
Make sure the collection URL you enter is correct. In your screenshot, the URL you enter is ended with "_home".
Make sure Basic Auth is enabled on TFS server.

Seems you are using the extension TFS artifacts for Release Management which provides a service endpoint to connect to an external TFS or VS Team Services Collection.
After test with TFS2013, I could reproduce your issue and got the same error information. The solution please see below:
Since you are connecting to TFS2013, it works with basic
authentication only. You’ll need to enable basic authentication
support for the TFS Server which handling TFS2013.
Also please make sure the username to connect to the external TFS
collection are with Domain in front of. Then will get a green
verfifed status.

Related

Internal Server Error Azure Dev Ops Server 2019

I have inherited an non working AzureDev Ops 2019 server.
I have been tasked to fix it.
The only thing I seem to be able to access is the Administration console.
The site collections (which I am guessing the should look like websites) just show a web structure.
It is like it is missing the default page.
When I try to modify the "group membership" or "administer security" I get "Http 500 internal server error. Please contact your administrator. There was an error contacting the server".
I have tried repairing Azure DepOps but to no wail.
Can anyone please point to information on how to fix or trouble shoot issues on a DevOps 2019?
I have looked at application logs and IIS logs but there is nothing useful there.
thank you for your help in advance

Connect to Azure Sql Database in Visual Studio Code using Active Directory Authentication

I am looking to connect to azure sql server in Visual studio code using one of the Active Directory connection modes. However seems only sql authentication is supported as of now in visual studio code. Any help here is appreciated.
Tried checking in visual studio code documentation but didn't find any mention of active directory authentication
Please consider using Azure Data Studio, which is derived from VS Code for use with SQL Azure and other Azure Data services. It supports Azure Active Directory authentication (which is a bit different than traditional integrated authentication against a local AD. Given that SQL Azure isn't domain joined to your local domain, you would not be able to use it to authenticate anyways.
Here's the release notes where they mention AAD auth supportRelease Notes.

MIcrosoft Feedback Client can't connect to Team Foundation Server

I have a problem with the MIcrosoft Feedback Client, and in general the Request feedback option in VSTS.
If I try to open a request from the notification email, the Feedback Client displays the following error:
Cannot connect to Team Foundation Server. Verify the network connection and try again.
However, if I simply launch it as an application, I got a popup first, where I need to pick the server, the team project collection and finally the project I'd like to connect to (it doesn't ask for login). This works just fine and the submitted feedback is displayed in VSTS, it can be queried, etc.
I removed all cookies and cleared browser cache from all browsers I use, also I checked if there's a false entry in Windows Credential Manager.
Any suggestions what I should try next?
update
We use Feedback Client for Microsoft Visual Studio Team Foundation Server 2015 downloaded from here
Make sure the account you use have the permission to access to the project and view the work items.
Feedback client use the credentials stored in Team Explorer. Try to delete the stored credentials from "Visual Studio -> Team -> Manage Connections -> Manage Connections -> Servers -> Remove" and then launch Feedback Client from email. A sign in dialog will pop up after this and you can enter your credential in it.
If it still does not work, clean all the TFS cache from "%LocalAppData%\Microsoft\Team Foundation\x.0\Cache" folder.
And also, check the link in the email to make sure it is correct. The link should like following:
mfbclients://xxxxxx.visualstudio.com/DefaultCollection/p:ProjectName?rid=FeedbackID
What version of the TFS Client are you using 2012, 2013 or 2015? I ran into a similar issue when we were using this on premise and I had to bump down to a lower version of the TFS Feedback Client.
Here is the TFS 2015 client.
https://www.microsoft.com/en-us/download/details.aspx?id=40768
I just tested mine to VSTS and it worked as expected.

Connecting to TFS 2010 from Eclipse using Team Explorer Everywhere 2010 SP1: Access Denied

I am trying to connect to my company's TFS 2010 server from eclipse using Team Explorer Everywhere 2010 SP1.
I have successfully installed the plugin and am attempting to create the connection to our server through the "Add New Server" dialogue. Entering the server https://tfs.<ourServer>.com/tfs along with my Active Directory credentials creates the error:
Access denied connecting to TFS server... <server> (authenticating as <DOMAIN>\<user.name>
I can connect to this same server from Visual Studio 2010 without a problem using the same credentials, and I can also connect to the web client by browsing the the server using IE.
I have also used the command line tool to define a profile which appears in the Eclipse plugin but creates the same error.
Have I missed something obvious? Is there a setting on the TFS server I need to change?
I had the same issue but changing the Eclipse proxy to native solved the issue in my case.
Can you connect successfully if you use the URL of your Team Project Collection, for example:
http://tfs.mydomain.com:8080/tfs/DefaultCollection

Nuget Server returning 403's and 404's

I'm trying to host nuget on my Amazon EC2 VPS, and I'm having issues.
I've followed the instructions here ( Hosting your own NuGet Feeds )
I've read this thread ( NuGet: remote server returned an Error(403) Forbidden ) along the same lines.
I'm not running TFS
It "could" be a proxy issue, but I'm not entirely sure how to check.
My NuGet feed is located at http://nuget.infinitas.ws. You'll notice that both http://nuget.infinitas.ws/nuget/Packages and http://nuget.infinitas.ws/Packages are throwing errors.
Any help with this will be greatly appreciated.
You are probably running the NuGet.Server in a Web Site-project. Try to run it via an ASP.NET Web Application instead (in Visual Studio you can create one via File -> New -> Project -> ASP.NET Web Application)
Have you tried the latest version (1.5)?
The release notes include some changes related to proxy authentication:
Support for Proxies that require authentication
When using NuGet behind a proxy that requires authentication, NuGet will now prompt for proxy credentials. Entering credentials allows NuGet to connect to the remote repository.
I realize I'm a little late to the party but I've just spent a frustrating couple of hours with the same problem.
I found that switching the Application Pool from "Classic" to "Integrated" fixed the problem