TFS 2018 RC1 is now available and you can download it from https://www.visualstudio.com/downloads/. Release note here explains the new features you can expect in TFS 2018. Below features are going to be removed from TFS with this version.
- SharePoint Extensions
- XAML Builds
- Team Rooms
- Lab Center and automated testing flows in Microsoft Test Manager support
Requirements for TFS 2018 can be found here. Let’s look at the installation experience with TFS 2018 RC1 on Windows 2012 Server with SQL 2016 SP1.
Install SQL 2016 SP1 and reporting services should also be configured in native mode.
Download and install TFS 2018 RC1, setup will show below error on Windows Server 2012.
The .NET Framework 4.7 installation (required by this version of Team Foundation Server) cannot continue because of a missing update. Install the update from https://go.microsoft.com/fwlink/?LinkId=854151 (https://go.microsoft.com/fwlink/?LinkId=854151) and then try installing Team Foundation Server again.
To fix this required to install an update to windows. Go to the https://go.microsoft.com/fwlink/?LinkId=854151 and get the update by clicking on the link “The .NET Framework 4.7 installation is blocked on Windows 7, Windows Server 2008 R2 and Windows Server 2012 because of a missing d3dcompiler update” (https://support.microsoft.com/en-us/help/4020302/the-net-framework-4-7-installation-is-blocked-on-windows-7-windows-ser)
Then click download link (http://go.microsoft.com/fwlink/?LinkId=848160)
Install Update for Windows (KB4019990)
After install no restart needed to the machine you can now rerun TFS setup.
After setup completed restart the machine. Then let the TFS configuration wizard to run when prompted. Select Configure Team Foundation Server and click Start Wizard.
Proceed to next step.
Select new Team Foundation Server deployment and click Next.
Select start trial check box and click Next.
Go with New Deployment – Advance option.
Select the preferred language and proceed.
Specify the SQL Server instance and click Next.
Provide a service account or use system account NT AUTHORITY\NETWORK SERVICE and click Next.
You can edit the setting and add FQDN if required.
Select to install and configure search and provide a service account for search service or use system account NT AUTHORITY\NETWORK SERVICE.
Select check box to Configure Reporting services for TFS.
Populate reporting services URLs from the installed reporting services.
Verify analysis services are running.
Provide a service account for report reader account.
Specify a collection name or leave it with DefaultCollection (default collection name).
Review the settings and click on Verify for readiness checks.
Java Runtime Environment (JRE) is required for Search service, error will be shown. Select the check box to download and install it with the setup and click on Configure.
Java runtime downloads and installs for search service, but configuring fails at Search Service, if you have specified an account other than NT AUTHORITY\NETWORK SERVICE as the service account for the search service.
[Info @07:14:13.319] Adding JAVA_HOME to the environment of child process, value: C:\Program Files\Microsoft Team Foundation Server 2018\Search\Java\jre1.8.0_144
[Info @07:14:13.319] Process starting: fileName=cmd.exe arguments=service.bat start
[Info @07:14:16.203] Process finished: fileName=cmd.exe arguments=service.bat start exitCode=0 in 2883 ms
[Info @07:14:16.203] Failed starting 'elasticsearch-service-x64' service
[Info @07:14:16.205] Waiting for Elasticsearch operation to complete...
[Warning@07:14:16.216]
Exception Message: Elasticsearch operation was timedout. (type ElasticsearchOperationTimedoutException)
Exception Stack Trace: at Microsoft.TeamFoundation.Admin.Search.ElasticsearchInstaller.<>c__DisplayClass3_0.<Start>b__0()
at Microsoft.TeamFoundation.Admin.Search.ElasticsearchInstaller.<>c__DisplayClass5_0.<InvokeServiceBatCommand>b__0()
at Microsoft.TeamFoundation.Common.RetryManager.Invoke(Action action)
[Info @07:17:16.206] Adding JAVA_HOME to the environment of child process, value: C:\Program Files\Microsoft Team Foundation Server 2018\Search\Java\jre1.8.0_144
[Info @07:17:16.206] Process starting: fileName=cmd.exe arguments=service.bat start
[Info @07:17:18.442] Process finished: fileName=cmd.exe arguments=service.bat start exitCode=0 in 2236 ms
[Info @07:17:18.442] Failed starting 'elasticsearch-service-x64' service
[Info @07:17:18.443] Waiting for Elasticsearch operation to complete...
[Warning@07:17:18.443]
Exception Message: Elasticsearch operation was timedout. (type ElasticsearchOperationTimedoutException)
Exception Stack Trace: at Microsoft.TeamFoundation.Admin.Search.ElasticsearchInstaller.<>c__DisplayClass3_0.<Start>b__0()
at Microsoft.TeamFoundation.Admin.Search.ElasticsearchInstaller.<>c__DisplayClass5_0.<InvokeServiceBatCommand>b__0()
at Microsoft.TeamFoundation.Common.RetryManager.Invoke(Action action)
As confirmed by Microsoft support this is due to a bug in TFS 2018 RC1 and options to setup search for TFS are as below as per the instructions by Microsoft support.
“There is a bug in TFS 2018 RC1, which causes this failure when search service is configured to run under account other than NT AUTHORITY\NETWORK SERVICE. The issue will be fixed in TFS 2018 RC2. For now, you can either use NT AUTHORITY\NETWORK SERVICE or configure search after you configure TFS.”
With this information letting the search service configure with NT AUTHORITY\NETWORK SERVICE worked fine. Or first configuring TFS 2018 RC1 without search and then configuring search for TFS with other domain service account or NT AUTHORITY\NETWORK SERVICE works fine as well.
Without search service configuring TFS.
Then Search service can be configured by selecting Search tab in TFs admin console and clicking on configure installed features. Select Configure Search in the Configuration Center and Start Wizard.
You can select to download install JRE if not already installed in the server.
In the settings now you can specify NT AUTHORITY\NETWORK SERVICE or other domain account as the service account for Search service. Both works fine if you are configuring Search service after configuring the TFS.
Let’s explore new features and improvements in TFS 2018 in next posts.
No comments:
Post a Comment