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.
Related
I'm doing both a hardware and a domain migration, as well as upgrading my TFS instance from 2015.3 to 2017.1. I first discussed this project (and received some VERY helpful suggestions) here.
Here’s the infrastructure I’ve got right now:
Hostname Operating System
SERVER1 Hyper-V Host 2012 r2
SERVER2 Server Essentials 2012 R2
SERVER3 Server 2012 R2 (TFS 2015.3)
DB Windows 10 (SQL 2014)
...and here’s what’s planned:
Hostname Operating System
SERVER1 Hyper-V Host 2016
SERVER2 Server Essentials 2016
SERVER3 Server 2016 (TFS 2017.1 & SQL 2016)
The old and new domains carry the same descriptive name (e.g. DOMAIN). For the purposes of this Q&A, henceforth I'll refer to any VM on the old domain with a leading underbar (e.g. _SERVER3).
My problem is that the guidance for the hardware migration doesn't indicate whether the TFS Restore action can be run on a machine with a different NETBIOS name than the name of the machine on which the backup was taken.
I've set up a temporary _SERVER4 for this project, which I will join to the new domain as SERVER4 as part of the domain migration, but I don't know whether this will work. _SERVER3 has a different machine/domain SID, of course, which may confuse TFS if I restore to _SERVER4.
I'll then build up a new, clean SERVER3 on the new domain and restore from the backup taken on SERVER4. Same issue.
Is this really a problem—restoring a backup to a different machine name, same domain—or am I being too cautious and simply imagining a problem where one doesn't exist?
OK, this can work.
I'm now running a restored TFS instance error-free on _SERVER4, from a backup that was taken on _DB. It didn't come without a few hitches, though:
TFS backup/restore doesn't touch the Analysis Services database, so we have to manage that manually
RS configuration by default requires a secure connection, a requirement which must be disabled:
In Windows Explorer, locate the ReportServer directory. The following path is the default path of this directory: C:\Program Files\Microsoft SQL Server\MSRS10.MSSQLSERVER\Reporting Services\ReportServer
Right-click RSReportServer.config, click Open With, click Notepad and then click OK.
Locate the following Add Key entry: <Add Key="SecureConnectionLevel" Value="2"/>
Change the Value setting from 2 to 0
When the database server name changes as well, we must perform a bit of a hack:
DELETE FROM [ReportServer].[dbo].[Keys] WHERE MachineName = 'YourSourceServerName'
None of these requires an OS or service restart. Just apply the changes and try again.
As #jessehouwing indicates, there are some stops along the way in the Configuration Wizard where we have to update the server name. But all in all, other than the few little bumps listed above, the process went pretty smoothly. (And frequent checkpoints were absolutely vital to this success.)
Now for the domain migration... extra thanks to Jesse for all of his help with this.
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.
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.
I have this scenario in my local network:
[picture] http://fekt.datagrid.sk/DATA/stackoverflow/scenario.PNG
Windows 2012:
Only IIS installed and configured, TFS installed and configured.
TFS configuration:
[picture] http://fekt.datagrid.sk/DATA/stackoverflow/config.PNG
When I run Visual Studio 2012 on win2012 machine, everything works perfect.
I can check-in, check-out changes, i can go to web access(http://win2012:8080/tfs)
From Desktop PC (Win8, VS2012) I can not connecto to TFS.
Do you have any ideas?
Thanks.
It is most likely the windows firewall.
I would suggest you add the port in question and application to the windows firewall exception rules.
You can quickly test by turning it off but remember to turn it on again once you have tested.
Is it a DNS or WINS issue?
Try to ping win2012 from your desktop PC.
Maybe you can try use IP to access the TFS by http://xx.xx.xx.xx:8080/tfs
I have a TFS 2010 application installed on server1. I have the data tier on server2. We are going to get rid of the server1. I want to install the TFS application on Server2 (same server as data tier). First of all, which configuration option do I pick during the install? Do I have to bring my server1 down before installing application on the data tier server2?
You can find all the information you need at MSDN: http://msdn.microsoft.com/en-us/library/ms404879.aspx