Thursday, April 05, 2012 7:52 AM
We have set up TFS 2010 in one server and its databases in another server.
Its notification URL was http:servername:8080/tfs and TWA is http:servername:8080/tfs/web.
We want to change TWA to https:domain/tfs/web and tfs url to https:domain/tfs.
For that we have added below in site binding of Team foundation Server site in IIS
also selected SSL Certificate
Then in TFS application tier, Clicked on Change URL gave https:domain/tfs as notfication URL.
Then When I am accessing TWA using https:domain/tfs/web. I have been asked to enter username and password and logged into the page. But no data is populated
and I am getting the below error message in the data section.
"Team Foundation services are not available from server https://servername/tfs. Technical information (for administrator): The underlying connection was
closed: An unexpected error occurred on a send."
In Change Url section in TFS application Tier; on testing the connection of notification URL,I am getting the error: "tf30063 you are not authorized to access https:domain/tfs". But I am able to login tot he page as mentioned above , the data is not loading.
- Edited by Rose 25 Wednesday, April 11, 2012 7:16 AM removed system specific information
Friday, April 06, 2012 1:59 AM
Please check out the guide below and see if you miss any steps:
You may also consider choosing hosted TFS.
Wednesday, April 11, 2012 7:15 AM
I am yet to secure sharepoint web application for tfs project portal and reporting service.
Now I am able to connect the url https:freindly servername/tfs from team explorer. able to view source code, work items etc.
But not able to connect the URL https:servername/tfs. and getting the error code TF31002.
Also when I am getting when I am accessing TWA using https:freindly servername/tfs, I am able to login to TWA. But in the contents pane, getting error message that TF31002: Unable to connect to this Team Foundation Server: https://servername/tfs. Team Foundation Server Url: https://servername/tfs. Possible reasons for failure include: - The name, port number, or protocol for the Team Foundation Server is incorrect. - The Team Foundation Server is offline. - The password has expired or is incorrect. Technical information (for administrator): The request failed with HTTP status 404: Not Found.
So in short https:servername/tfs is not accessible but https:freindly servername/tfs is accessible.
I am not sure how it is going for https:servername/tfs when I actually logged in https:freindly servername/tfs. Please help me to fix the issue.
Wednesday, April 11, 2012 6:09 PM
The reason the Test fails on the notification URL is because of the Loopback check issue (using the friendly name on the server itself). Follow the directions in this KB: http://support.microsoft.com/kb/896861
Thursday, April 12, 2012 6:35 AM
Thanks a lot Wes.
Followed your reply and passed the test connection of notification URL.
But I am not sure why it is going for https:servername/tfs when I actually logged in to https:freindly servername/tfs (which is the url will be used by users) and why https:servername/tfs is not accessible. The issue specified in the screen shot given earlier still exists.
Please help me to fix the issue.
Thursday, April 12, 2012 8:47 AM
We have added below entry in the tfsservers node in webconfig file (Drive:\Program Files\Microsoft Team Foundation Server 2010\Application Tier\Web Access\Web)
<add name="https:freindly servername/tfs" />
Now When I am accessing TWA using https:freindly servername/tfs/web I am getting data.