Error in Connecting to TFS Server(TF31001) - tfs

I am unable to connect to the server which is located remotely and required connection to OpenVPN.
I would have concluded that its some sort of Authentication issue, but it seems that my teams mates using similar Working Environment to mine are able to establish connection. I am able to log in from their PC using my Credentials. Looks like this could be due to my local settings.
I have cleared the Cache as suggested in MSDN sites. Also, Firewall and Antivirus are off.
I also get prompted for the User/Name password when I click Team Explorer Icon on Visual Studio. Invalid credentials show error messages as expected, on entering proper credential information, I get the following message:
TFS31001: Team Foundation cannot
retrieve the list of team projects
from Team Foundation Server. The Team
Foundation Server returned the
following error: Team Foundation
services are not available from the
server.
What could be the reason for this?


That error message is always due to a security issue but that doesn't tell you "why" there is a security issue. Can you take a look at the event log for more details- not sure what else might be in there but it might be a good starting point.
I had this issue a long time ago when working remotely and it was a trial and error thing but in my case clearing cache then removing the TFS Team Project and re-adding it fixed the issue. You can try that. I see you did clear cache but I am not sure from reading this if you removed and re-added. If settings are cached and you dont do that I doubt you will see a change.
Another more aggressive solution would be to uninstall and reinstall Team Explorer. Also, make sure your up to date on SPs. Permissions could have been messed up somehow with TFS installation and this could potentially resolve the issue.
Anyway, I know this isn't a cut and dry answer but I hope it helps. I just spent the last three days upgrading all our company Team Projects from 2008 to 2010 so I feel your pain :)


It was problem at my end. Using a Different Gateway did the trick.


I've got this error once my TFS database server ran out of diskspace.


I encountered same error.
I found this which looked like a viable solution. :
http://social.msdn.microsoft.com/Forums/en-US/tfsversioncontrol/thread/f681a2d6-eca9-4488-96a3-ed979a545a9b
I ended up just turning my proxy settings of in IE and it started working instantly.


The same story occured with tfs 2012 - it was installed and configured properly, local network has domain and all users in domain correctly connected and worked with tfs projects.
But once the connection denied all tries for connection, all credentials were correct, but connections has been refused. Tried to configure tfs clients access, to reboot client machines... but worthless.
Only server service/machine rebooting helped. Good luck!


I fixed by clearing the cache at:
C:\users{yourusername}\Appdata\Local\Microsoft\Team Foundation{version e.g.3.0}\Cache
Quit any open instance of visual studio first.

Related

how to fix Error TF30063: You are not authorized to access VS2017

I changed my password for my TFS. But when I try to reconnect I receive the TF30063 unauthorized error.
There are many issues like this and I tried everything I could find from this solution and other forums
Solve this issue by using the VS browser
The right click on the connection
The windows 10 manage user accounts edit and even the remove
Deleted every VS cache file from appdata
Deleted the whole connection in VS & tried to readd a new one
Deleted all my Internet explorer cookies, passwords cache etc.
None of them work... Can't figure out what the issue is.
PS: it works within the browser.

It should be a Visual Studio 2017 credential cached token issue. You could try below ways to clear cache:
Close all Visual Studio instances.
Delete %LOCALAPPDATA%.IdentityService.
There are some identity related caching going on in there, deleting the folder will force the identity system to rebuild its cache.
Also Clear TFS related caches %LOCALAPPDATA%\Microsoft\Team Foundation\x.0\Cache
Run Visual Studio as another user:
cd C:\Program Files (x86)\Microsoft Visual Studio\2017\Enterprise\Common7\IDE
runas /netonly /user:<account> devenv.exe
Enter the user password, then Team Explorer > Manage Connections
If the issue still exists, also take a look at this blog for more ways.

Based on developer community there is a timing issue during visual studio start up that can cause the Source Control Explorer window to grab and then hang on to an invalid version of the connection to your team project. Details visit developer community.
https://developercommunity.visualstudio.com/content/problem/93366/tf30063-you-are-not-authorized-to-access-visualstu.html
Following work around steps help me to resolve the issue
Close all visual studio 2017
Start Visual studio 2017
If you see source control explorer at start up, then close source control explorer and Team explore and close visual studio 2017
Open visual studio 2017, ensure no source control explorer opened at start up
Go to View menu and click on team explorer
Then connect to TFS server.

I've gotten the above error (TF30063: You are not...) numerous times and the following three resolutions worked for me at different times:
Simplest: I've seen "Source Control Explorer" referenced numerous times, but I never leave that open. I resolved the above error by closing Team Explorer and reopening. I then loaded my solution, and then reopened Team Explorer. It opened without issues and I could contact the server (ie, I ran a code comparison in the Solution Explorer on a file I'd edited) -VS Pro 2017 v 15.8.0
Middle complexity:
I was able to reconnect with the following steps:
-Open Team Explorer (View menu => Team Explorer)
-Click "Manage Connections" which is the plug shaped button at top
-Click the text "Manage Connections" which is actually a drop down menu
-Select "Connect to a Project"
This brings up a new window that shows hosted repositories for your account. After several seconds the window displayed the desired projects. I just had to click the desired one and click the "Connect" button at the bottom. Once I did this, I was able to access all TFS features (ie I checked in some work) -VS Enterprise 2017 v15.9.3
Last resort:
I loaded VS2017 Community onto another machine and logged in on that machine using my regular login. I'm not sure why, but as soon as I logged in on this new installation my other two computers had no problem connecting. No additional steps were needed, though I may have restarted VS on those machines.

I will be facing this issue every six times a year. Because domain account password gets expired every 2 months 0 days or 8 weeks 5 days or 61 calendar days interval due to business security policy.
Follow these steps to change/set Password of TFS from IDE
Delete TeamExplorer.config from
%AppData%\Microsoft\VisualStudio\15.0_xxxxxxxx\Team Explorer.
(So after establishing a successful connection, it'll try to recreate
again with the same data)
Add or change the TFS account Credential from Windows Credential Manager. So it won't prompt to enter a password again whenever when a connecting is established from IDE to TFS
If the above doesn't work close the Visual Studio IDE. Delete all the files inside %LocalAppData%\.IdentityService and %LocalAppData%\Microsoft\Team Foundation\7.0\Cache and on elevated prompt execute runas /netonly /user:<user domain account> devenv.exe navigating from "C:\Program Files (x86)\Microsoft Visual Studio\2017\<Professional>\Common7\IDE\"

I had this same problem, and the solution I finally found was when VS asked if this was a "Work or school account" or a "Personal account" I chose "Personal account", and that fixed it even though it is a work account. This used to work fine, but it seems with some recent updates it causes an issue if you select "Work or school account"

I also had this problem with VS2017, version 15.9.4.
Common fixes are detailed here and here. And the majority of pages talking about this problem reference those solutions or sub-sets in some combination or another. (And often to fix login bugs introduced in one of the 15.5.* versions of VS2017)
None of those solutions worked for me either and after researching for 2 days, I found a couple of fringe-reasons why VS 2017 will not refresh/store credentials.
The 2 main "fringe" problems/fixes I've found are:
Connecting through certain proxy setups
Cryptography store not allowing for local storage, see also here
For myself it was the second problem, a good indicator of the issue is a log entry in %TEMP%\servicehub\logs with the error: "The requested operation cannot be completed. The computer must be trusted for delegation and the current user account must be configured to allow delegation."
It might also be a Windows 7/8.1 known issue carried over to Windows 10 upgraded machines. The problem only happened on a machine that joined the domain after doing the Windows 10 upgrade.
The fix is to add the following registry entry:
[HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Cryptography\Protect\Providers\df9d8cd0-1501-11d1-8c7a-00c04fc297eb]
"ProtectionPolicy"=dword:00000001
Setting that immediately fixed the issue with VS2017 connecting to the Microsoft Account. (And some other applications that would not persist credentials between launches)

After you have tried making changes to default browser and installing new browser like firefox or chrome, if still doent work, then you might have to check with network team of your organization on proxy settings that should be allowed in internet options. We have tried the above and it worked.

Maybe this only happened to me but I always used the wrong credentials (wrong username or wrong password). On Windows 11 I was only using my PIN, so it took automatically a user and password. I had to use different credentials to change my name and password.

TFS Error: Source Control Explorer - Unable to read data from transport connection

When I try to get latest version of project in TFS it does not work and produces this error:
'Source Control Explorer. Unable to read data from transport connection. The connection was closed.' How do I fix this so I can get the latest version of the project's code?

According the error message seems like the connection to the server was made but since the service was not available on machine, then the sever canceled the request.
You could try below ways to narrow down the issue:
First check the event view on the TFS server if there are some
related error info.
Try to get another team project in some collection and different team
project collection.
Try to use another account to get latest on your machine.
Try to use your account to get latest on another machine. If the
issue only occurs on your machine, you may need to clear TFS and VS
cache which may do the trick.
If you are using Window Server 2008R2. Maybe it's related this
issue. Applied the HotFix and try the workaround.

TF400324 : Team foundation server not available from server (Some server IP). Technical information(for administrator):

While connecting to tfs server I am getting this issue.
"Team foundation server not available from server ... (Some server IP). Technical information(for administrator): the underlying connection was closed: An unexpected error occurred on a receive"
I am facing this issue in one machine but in other machine its working fine. and I am not using any VPN.

This is likely a firewall/port issue. You can run WireShark (or something similiar) on both machines and compare the network route. Then talk to you network admins about removing the block.

I don't have much technical knowledge about TFS, but everyday i have to check-in my code from Visual Studio and recently i came across this issue. I tried a simpler way:
-> Logged out then logged in into the TFS again through Team-> Manage Connections.
-> Mapped my project again.
And Voila! it worked. Maybe this will help others

Team Foundation Server Access to the Path ... is denied

I just got assigned at my job to figuring out Team Foundation Server as we are switching to it from PVCS. I was messing around with the source control features, trying to get gated check-in to work, as that is something we will be using in my job. I am pretty sure I set up the build definition correctly, as far as I can tell that is, and I turned MSBuild Multi-Proc to false as I have seen suggested online.
My problem is that when I try to check in a file I get an error for every file in my project stating
C:\Builds\1\TFSTestProject\Gated\src\TFSTestPrograms\TFSTestPrograms\{File} Access to the path 'C:\Builds\1\TFSTestProject\Gated\src\TFSTestPrograms\TFSTestPrograms' is denied.
I don't understand why I would have any access denied and I have looked for solutions all over google and have not found anything that has fixed this issue. My server url is just http://localhost:8080/tfs so I should have access to everything (at least I think i should...)
Another thing is that there is no 'Builds' folder on my C:\ drive like in the path they give
I am very confused about this issue and I have no idea how to fix it.

If you have installed a build server the path that it is objecting to is on the build server itself. You should review the installation instructions for the build server and the account used to set up the build server.
Two lengthy to repost but ben day has an excellent TFS installation guide here: http://www.benday.com/BlogFiles/Tfs2012InstallGuide/BenDay-TFS2012-Install-Guide-v1.0.pdf

Make sure that whatever account you configured TFS and, more importantly, the Team Build service to run as, has full control access to the C:\Builds folder.

Issues with duplicating TFS 2005 to a virtual server

We have a problem with our current TFS installation. For some reason, which I won't get into, the Sharepoint DBs (sts_content, sts_config) got corrupted. So now, none of our team-project sites work, we have no access to our documents and can't create new team projects. We can still work with the version control, though.
We wanted to "play" with the server and try to fix it, without affecting the users. So we duplicated the server to a virtual one. We now continued and changed all of the relevant configuration to point to the new server, as explained in the MSDN article.
The step of rebuilding the warehouse (with setupwarehouse) failed. Also, we can't access the VersionControl web service (ourserver:8080/VersionControl/v1.0/repository.asmx). We are seeing errors in the EventLog:
TF53002: Unable to obtain registration data for application Build.
TF53005: Unable to retrieve the Team Foundation Server installed UI culture.
TF53002: Unable to obtain registration data for application VersionControl.
TF30040: The database is not correctly configured. Contact your Team Foundation Server administrator.
The solutions suggested in this blog post did not assist. So now we're kind of stuck.
Any assistance will be appreciated.

This is a really old question, but what I would suggest doing is installing a fresh copy of Team Foundation Server 2010, then in the configuration wizard, select 'Upgrade' and choose your existing TFS2005 databases. This will allow you to get a working server up and running, without SharePoint and the Cube/Warehouse configured. You can then tackle each of those problems separately via the TFS Administration Console.

Resources