I am taking over the TFS 2015 a previous employee set up.
When trying to access the webapp I am getting an HTTP 500 error "The website is under maintenance".
When trying to open the Team Foundation Server Administration Console I am getting the "... TF246017: Team Foundation Server could not connect to the database..."
When looking at the SQL Server ERRORLOG I am seeing the "SQL Server evaluation period has expired."
It seems to me previous employee setup the trial version of TFS 2015.
How could I verify this is true and how can I upgrade the version to a purchased license?
Thanks
The root cause is "SQL Server evaluation period has expired."
You can try testing the SQL Server instance in TFS Administration Console (Generally the test connection should be failed if the SQL license expired) :
Select specific Collection --> Stop the collecion --> Edit Settings --> Test
To activate the SQL Server again, you need an edition upgrade for SQL Server . To upgrade, you need to have installation media of the destination version. SQL Server evaluation edition can be upgraded to standard, developer, enterprise editions.
Here are the steps:
From SQL Server installation media, launch setup.exe.
From the SQL Server Installation Center click Maintenance, and then
select Edition Upgrade
It would launch Wizard where you need to keep on pressing next, next
and finally “Upgrade”. Make sure that edition shown in the license
terms screen is what you purchased.
Please refer to SQL SERVER – Evaluation Period Has Expired – How to Activate SQL Server? for details.
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 have a small issue that is driving me crazy.
I'm trying to install TFS 2015 on a VM with Windows Server 2012 R2 and SQL SERVER 2016.
Everything is ok but my on Analysis Services Settings I get an error.
TF400069: When your configuration includes Reporting features on a
remote machine, you must install the "Client Tools Connectivity"
feature from SQL Server.
As you can see on the following screenshot "Client Tools Connectivity" is installed.
Am I doing something wrong?
Thanks
Please check the TFS requirements and compatibility, the supported SQL Server version is:
SQL Server 2014
SQL Server 2012 (minimum SP1)
SQL Server 2016 is not in the list yet. You need to use compatible SQL Server version.
I am trying to configure Release Management Client to work with a Release Management Server for Microsoft TFS 2013 on a Windows Server 2008 R2 Standard.
I installed (without any errors) the following two from our subscription downloads:
en_release_management_server_for_team_foundation_server_2013_with_update_4_x64_web_installer_5920525
en_release_management_client_for_visual_studio_2013_with_update_4_x86_x64_web_installer_5920526
I have not installed any Microsoft Deployment Agents.
I have installed and configured the RM server for a SQLExpress db (different from the TFS db in our case) and for now I used my own network credentials (being a member of Administrators group on the server and a member of Default Collection Administrators on TFS, with "Make requests on behalf of others" set to "Allow" on TFS).
When I copy the RM Server URL from "Configure Release Management Server" screen (http://xxx:1000/ReleaseManagement) and paste it into a browser, the page loads without any errors.
However, when the same URL is used in RM Client Configuration, I get an error: "The server specified could not be reached":
We have VS2012 on the server and VS2013 Ultimate on my own dev machine.
I tried installing and configuring the client on both the server (Win Server 2008 R2 Standard) and my dev machine (Win 8.1 Pro), and I still get the same error (so I assume the version of VS is not an issue).
Looking at the event log, I get two errors.
ERROR ONE:
The remote server returned an error: (404) Not Found.: \r\n\r\n at System.Net.HttpWebRequest.EndGetResponse(IAsyncResult asyncResult)
at Microsoft.TeamFoundation.Release.Data.WebRequest.PlatformHttpClient.EndGetResponse(IAsyncResult asyncResult)
at Microsoft.TeamFoundation.Release.Data.WebRequest.RestClientResponseRetriever.EndGetAsyncMemoryStreamFromResponse(IAsyncResult asyncResult, IPlatformHttpClient platformHttpClient)
.... [edited out for brevity]
Process Name: C:\Program Files (x86)\Microsoft Visual Studio 12.0\Release Management\Client\bin\ReleaseManagementConsole.exe
ERROR TWO:
Error communicating to the web server URL: http://xxx:1000/ReleaseManagement/account/releaseManagementService/_apis/releaseManagement/
Indeed, when I enter that URL in a browser, I get "404 - File or directory not found". Here is what the site structure is:
What I should do to be able to configure our Release Management Client without errors, please?
Additional observations:
I cannot see "Release Management" role on our server, but have seen in mentioned in relation to RM installs.
The client installer reads "Release Management Client for Visual Studio 2013 Update 4", whereas instructions here indicate it should be "Release Management Client for Team Foundation Server 2013 Update 4". Surprisingly, when I ran the installer recommended by that article, the title again read "...for Visual Studio" as opposed to "...for Team Foundation Server".
Many thanks in advance!
You're entering the wrong URL. The URL should be http://<RM Server Name>:<Port>. No /ReleaseManagement/.
The /ReleaseManagement/ folder is not for the desktop client, but rather for the approval dashboard.
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 haven't seen anything that says SQL Express 2005 is not supported for use with Team Foundation Server 2005.
However, when I attempt the installation I get all sorts of errors "SQL Agent service not installed", "SQL Server 2005 Analysis Services service is not installed", etc.
Is SQL Server Standard or higher, required?
Yes, SQL Server Standard or higher is required for current versions of TFS. When you purchase a full copy of Team Foundation Server it comes with a restricted use SQL Standard Edition license under the following terms:
You may only use the SQL Server
software with Visual Studio Team
Foundation Server; you may not use
it for any other purpose.
You may
only install SQL Server on one
physical device per Visual Studio
Team Foundation Server license.
Try SQL Server Express Advanced edition ... ( I don't remember if it has analysis services)
Analysis services are required to generate reports. Also after installation of 2005 remember to start SQL Agent service.