i have installed TFS 2010 on WS 2008 R2 more than two years and every things worked fins till i have installed an app on the server which i think it change some seting on IIS/server. and after that i can not access tfs web services even on the TFS server localy!!.
what is the problem.
after that for resolving all security issues I changed TFS applicaion pool's identification to network administrator. tfs account is NT AUTHORITY\NETWORK SERVICE. i can create team project collection from the tfs administration console. i checked network traffic with fiddler for accessing http:///tfs and response was:
HTTP/1.1 404 Not Found
Server: Microsoft-IIS/7.5
Persistent-Auth: true
X-Powered-By: ASP.NET
Date: Tue, 16 Dec 2014 11:49:24 GMT
Content-Length: 0
If you have broken the server by installing something then I would recommend building a new dedicated TFS server.
Option 1) Create a new clean server for TFS. Install SQL and restore all of the databases from your old server. Then install TFS 2013.
Option 2) if you do not have room for a dedicated TFS server you should create a temporary instance to get working and then push all of your data to VSO (http://tfs.visualstudio.com)
If you run TFS locally you should be aware that TFS owned both the server and the database server that it is installed on. It is an application that includes those components.
Related
When I try to integrate TFS 2017 U3 with SQL Server 2017 Reporting Services, from TFS Administration Console, an error appear. Please see screenshot.
In the event viewer of TFS server, I see registered this error:
DCOM was unable to communicate with the computer servername using any of the configured protocols; requested by PID
1080 (C:\Program Files\Microsoft Team Foundation Server 2018\Tools\TfsMgmt.exe).
Error Image
I have had checked the following:
Windows Firewall is not blocking port 80
Reporting service is started
User Account has required permissions
WMI is running on the report Server
TFS databases are in the same server than reporting services and the TFS service is running without any problem.
Please, any idea how to revolve this error will be very appreciated
I was wrong when placing the error text messaage. I had performed a test from TFS 2018 that's the reason why I wrote with that description eror, but the productive environment is with TFS 2017 U3 and the error message is the same thing; the difference is the path where TfsMgmt.exe is located.
Thanks for your attention.
Audberto
i would like to upgrade my production TFS 2017 to TFS 2018.
according to the requirement, it need SQL Server 2016 SP1, because some reason, i decide use a new production server for it.
Before doing the production upgrade, i do the upgrade test in my testing enviroment, the step is
Install SQL Server 2016 SP1
Restore the TFS 2017 Database
Install TFS 2018 Update 1
Start the TFS Upgrade Wizard using my existing db
Confirm the 8080 port is allow to connect
After finish, i can access the TFS web on the testing environment server by using http://localhost:8080/tfs or http://SERVERNAME:8080/tfs (btw Chrome only can access using localhost)
When i connect http://SERVERNAME:8080/tfs on client pc, it doesn't work, it show me
ERR_CONNECTION_REFUSED
All my server have join domain and i try troubleshoot from tfs application to firewall, no any result on it.
Is there any step wrong or other problem on it?
UPDATE:
After i reinstall Windows OS, it's work.
Try below items to narrow down the issue:
Using IP instead of the SERVERNAME in the URL, then try it
again.
Clean local caches from the client machine (TFS caches, Browser
caches)
Restart the TFS wensite from IIS manager.
Restart IIS with command: iisreset /noforce
Try changing the port number for you TFS
Rebuild the client cache.
After you move, restore, rename, or fail over a data-tier or
application-tier server, you must refresh the cache for tracking work
items and users must refresh the version control cache on client
computers.
UPDATE1:
Just try below things:
Add the client machine name/IP to the hosts file. (The hosts file should be located under c:\windows\system32\drivers\etc\hosts)
Try to detach the collection then reattach it again
Try to reconfigure the TFS.
UPDATE2:
Based on geraldlim's comment below : Turn out that after reinstalling the OS and install IIS and TFS in a clear environment, it's working.
Is there a document on how to enable extranet access to TFS 2017? I have a VPS that I use and want to enable external access to TFS 2017 that is installed on this VPS.
Thank you
You can try below methods:
Maintain a connection between the client and the server by using a
VPN if you have to access Team Foundation Server from outside the
local intranet.
Through a Reverse Proxy
Locating TFS in an Extranet
Please refer to Chapter 17 – Providing Internet Access to Team Foundation Server for details. It's still available for TFS 2017 even though it's an old document.
We just upgraded our TFS 2013 to TFS 2015. We use VS2015 to communicate with it(we were already using it with our TFS2013). The server was not available during the time our IT made the upgrade.
After the ugprade, everybody started to work again with the server but I was seing it as Offline and I finally decided to remove the server and add it again.
When I add it again(200% sure of all the settings), I get this error:
I finally tried to do the same on our "old" installation of Visual Studio 2013(same computer, same account), and it works. I was at least capable to commit all my changes to the server.
I tried to go on the portal and click on `Open in Visual Studio", and I got another error(TFS400324):
Now I'm trying to regain access to TFS2015 with my VS2015. I can access the web portal.
Here is what I tried after some research:
Do a Repair of Visual Studio 2015
Check that I've no weird proxy
Check that there is no available update(already at VS2015 UPD 1)
Clear the cache of all my Internet explorer
Cleared %LocalAppData%\Microsoft\Team Foundation\*.*\Cache
Run VS2015 in admin
Disable my antivirus
Delete registry key HKEY_CURRENT_USER\Software\Microsoft\VSCommon\*.*\ClientServices\TokenStorage
Check that I've no proxy declared in: C:\Windows\Microsoft.NET\Framework\v*.*\Config\machine.config
I did a windows update.
I ran the command devenv.exe /resetuserdata
Any clue what is happening and how to solve it?
VS 2013 can connect to TFS 2015, but VS 2015 can't. So the issue is on client side. Try on another client machine to connect TFS 2015 with VS 2015 to check the result.
Clean the client cache: C:\Users\username\AppData\Local\Microsoft\Team Foundation\5.0\Cache and C:\Users\username\AppData\Local\Microsoft\Team Foundation\6.0\Cache. Make sure both 5.0 and 6.0 folder are cleaned.
Clean server cache on AT machine: C:\Program Files\Microsoft Team Foundation Server 12.0\Application Tier\Web Services_tfs_data, and C:\TfsData\ApplicationTier_fileCache
Remove all credentials in Control Panel\All Control Panel Items\Credential Manager.
Remove TFS server in Team Explorer: go to Manage Connections--Connect to Team Project--Servers, select TFS 2015, remove it and add it.
Connect TFS 2015 with it's IP address, not server name.
This answer will not please to anybody coming here for an answer, but I had to format my computer and do a whole clean install on it.
A little trick might help.
Change port 8080 to another port. I've changed to port 5000
I hope to be useful.
I am trying to determine what SQL Server edition will be installed with Team Foundation Server 2013 if it is installed on Windows Server 2012 R2 using the Standard Configuration. The install guide is vague about this. Will it be Express or Standard? It appears to be different than with TFS 2012.
You can use the basic configuration of Team Foundation Server, automatically with SQL Server Express SP1.
or install manually other versions.
link : http://msdn.microsoft.com/en-us/library/vstudio/dd631889.aspx
Only the Basic Configuration of TFS 2013 automatically installs SQL Server and it installs the Express version. This from:
Sql Server Requirements
From the same article: You can pre-install one of the supported editions Sql2012.sp1+ or Sql2014
During installation, you are required to select a configuration (basic, standard etc). If you choose standard and the installer can't find an existing SQL Server instance you can not proceed.