We have had an automatic Active Directory/Windows password change thrust upon us, and consequently our TFS2008 build server has broken. I have changed the password for the TFSERVICE account it runs under, and updated the Visual Studio Team Foundation Task Scheduler Service to use the correct password, and checked that the underlying Sql Server is running okay. However attempts to connect to TFS are now met with the message '..HTO Status 503: Service unavailable'.
What else needs to be started to get this up and running again?
You need to always change the password using the tools in the box. You can use the TFS Administration Console that you can launch from the start menu. Or you can use the tfsconfig.exe located in the TFS install folder.
This applies to all versions of TFS from 2010 on.
If you have TFS 2008/2005 you will need to use the tfsadminutil command: http://msdn.microsoft.com/en-us/library/bb552178(v=vs.90).aspx
Note: You need to upgrade your TFS server as soon as possible. Both the OS, SQL, and TFS pre-2010 is not well supported.
Related
Origin machine: TFS 2017 update 3 & SQL Server 2014
Destination machine: TFS 2018 update 2 & SQL Server 2017
Steps followed for a Dry-Run:
Followed the "Move or Clone Team Foundation Server from one hardware to another" and "Do a dry run of your upgrade". All databases are successfully restored on the same server (TFS_configuration, Tfs_collections, Tfs_Warehouse, ReportServer, ReportServerTempDB, Tfs_Analysis).
ChangeServerId and RemapDBs executed successfully.
When running the wizard to use the "Pre-production Upgrade Testing" we noticed the following:
When using "< nameofserver >\SSRS" (this is the default instance name for Reporting Services in SQL Server 2017) on "Reporting Services Instance" and the correct URLs are selected, these errors appear on the Readiness Checks:
It appears that the following best practices for this scenario have
not been implemented: VS403144: The warehouse database is currently pointing to the same database that was being used on your production deployment.
VS403140: The specified Analysis Services database is the same one being used in your production deployment.
When using "< nameofserver >" (this has been used in the past successfully with tfs2017) on "Reporting Services Instance" the following message pops up:
TF255186: The following SQL Server Reporting Services Instance could not be found: MSSQLSERVER. The server name is: "< nameoftheserver >"
Is the change of the instance name from "MSSQLSERVER" to "SSRS" causing this issue?
Thank you
This is most likely because you don't need to use ChangeServerID and ReMapDBs with the
Pre-production Upgrade Testing scenario. That scenario does those operations for you.
I'd reset the test instance, restore the databases, and try again without running changeserverID/remapDBs.
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.
I do not see an option to change the SQL instance in the Team Foundation Server Administration Console so I am assuming it is necessary to do so using TFSConfig. I am a little confused by the documentation as it states TFSConfig.exe /SQLInstance should only be used with /ResetOwner. I am not resetting the owner. If my old server instance is "Tfs" and my new instance is "TFS-SQL1\Tfs" how do I configure this in TFS?
If you are moving all the databases to a new instance or server, you can use the RegisterDb command.
"Use RegisterDB to update name of the server that hosts the configuration database in Visual Studio Team Foundation Server (TFS)."
In your case it would be something like this:
TFSConfig RegisterDB /SQLInstance:TFS-SQL1\Tfs /databaseName:Tfs_Configuration
The other option is the RemapDBs command.
"The RemapDBs command redirects Visual Studio Team Foundation Server (TFS) to its databases when they are stored on more than one server and you are restoring, moving, or otherwise changing the configuration of your deployment
TFSConfig RemapDBs /DatabaseName:TFS;TFS_Configuration
/SQLInstances:TFS-SQL1\Tfs
Personally I have found that a more fail safe way of doing it is to simple reconfigure TFS.
If you run
TfsConfig setup /uninstall:ApplicationTier
from the command line, it will set TFS application tier into a "un-configured" state which allows you to run through the setup / configuration wizard. Simply re-configure as an Application Tier and point it to the new server instance.
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.
After DCpromoing and then demoting the server that TFS runs on, we cannot use WSS ("Cannot connect to the configuration database") to manage team projects. I believe that if I could find the default permissions that are set up when TFS is first installed on a server that is joined to a domain - in terms of any service accounts that are created and which accounts various services should run as - I would be able to get it back up and running again. Does anybody know the default NT accounts and permissions for Team Foundation Server?
That error sounds like a SharePoint error. This technet article outlines the permissions (server, SQL, registry) that are required for a default WSS install.