I am trying to install the tfs2015.4.2patch7 on my server.
I found the .exe of the patch here.
When I execute it as administrator on the server, I get the following error message:
Logging to 'C:\ProgramData\Microsoft\Team Foundation\Server Configuration\Logs\Patch_2022-04-26_09-21-28.log
Checking SOFTWARE\Microsoft\TeamFoundationServer\14.0 to see if TFS is installed
Found InstallPath: F:\Program Files\Microsoft Team Foundation Server 14.0\
Found InstallVersion: 14.102.25423.0
Could not find Patch version in registry, no patches installed.
The Application Tier is configured.
The search Tier is not configured.
The proxy Tier is not configured
This patch does not apply to Tfs version 14.102.25423.0.
Hit Enter to Exit
I don't see what is wrong, and why the patch could not be applied, since it has been released precisely for this version of TFS.
Could you please help me?
Related
I've installed TFS 2017 in Windows server 2016. I just want to know the following
where are the installation logs stored in server?
Where are the transaction/history logs stored in server?
Correct me if am wrong, is it possible to backup history of logs and attach to TFS upgrade [in case of TFS version upgrade]?
The installation log file generally store in temp folder.
Typically this folder is : C:\Users\{name}\AppData\Local\Temp
And the Configuration logs stored in:
C:\ProgramData\Microsoft\Team Foundation\Server Configuration\Logs
The logs should be stored accordingly in case of TFS version upgrade.
Please refer to below articles for details(Even documented with old version of TFS and it's still apply for the new versions):
Where to find the TFS installation log?
I’m having problems with TFS install/upgrade/repair/uninstall –
where are the log files?
Trace/logging configuration in Team Foundation Server 11
My customer is installing Team Foundation Server Office® Integration 2017 tools on their isolated environment. for the similar environment, which is windows 7 sp1 64bit, some succeed, some failed. for the failed, An install window just flash before it disappears. how to check it? is there any place we can find the installation log file? thanks.
and where can I find the requirement document for Team Foundation Server Office® Integration 2017? does it require the similar environment as Visual studio 2017.
Try to log on to the TFS server with the setup user’s account and open the user’s temp folder. Typically this folder is C:\Users\{username}\AppData\Local\Temp. And find TFS installation log file name should resemble “dd_tfs_{}_{}.log”.
In addition, you need to check Requirements and compatibility for TFS installation at website below:
https://learn.microsoft.com/en-us/vsts/tfs-server/requirements?view=vsts
My system is an on-premises setup for TFS 2015 and I am trying to get Release Management working with my Jenkins continuous integration system. I have recently added the ""Visual Studio Team Services Continuous Deployment" plugin to Jenkins. After finding out that I need to have Basic Authentication enabled on my TFS server to avoid a 401 - Unauthorized: Access is denied due to invalid credentials. error I am getting to the next error: NullPointerException.
I have looked through the code for the vsts-cd-plugin to see that there is an explicit reference to this API call that I don't believe is in TFS 2015 Update 3...
"/_apis/release/releases?api-version=3.0-preview.2"
Has anyone been successful in using the vsts-cd-plugin with Jenkins and an on-premises TFS 2015 setup? Does anyone have a suggestion on how I can fix this problem to create a TFS Release from Jenkins?
The API version 3.0-preview.2 is for Visual Studio Team Services, it is not included in On-premise TFS. In On-premise TFS, you need to use 2.2-preview.1.
api-version = 3.0-preview.1
Using on-premises: An earlier, and slightly different, version of this
Release Management API is available in Team Foundation Server 2015
Update 2. To use, you must specify an API version of 2.2-preview.1.
New release references a release definition to deploy an application
comprising of one/
You can try to download the source code of the plugin and update the API version and then build it on your local machine and install it in Jenkins.
I am trying to install TFS Server 2010 on Windows Server 2008 R2 (Standard Edition). When I Start Configuring TFS on The Advanced Tab it gives a Warning and says that it requires a cumulative update for TFS - called KB2580221.
When I downloaded and tried to run the update, it gives:
KB2580221 does not apply, or is blocked by another condition on your computer.
How do I solve this issue?
KB2580221 is "Team Foundation Server 2010 SP1 Cumulative Update 1". Service Pack 1 is a pre-requisite for it, that is why you are receiving the error message.
"Cumulative Update 2" has since been released, and since it is cumulative, you don't need to install Cumulative Update 1 first. (But just to make it confusing, you DO need to install Service Pack 1 first).
So, what you need to do is:
Run the installer for TFS 2010 RTM (you've done this), but don't run the 'configure' wizard
Download and install: Team Foundation Server 2010 SP1 (477 MB)
Download and install: Team Foundation Server 2010 SP1 Cumulative Update 2 (23 MB)
Open the 'Team Foundation Server Administration Console' and select 'Configure installed features'
You will then have a new server running the latest version of TFS 2010.
Take a look at this blog post for a comprehensive list of patches and more information: TFS 2010: What Service Packs and Hotfixes should I install?
I am trying to build a project using TFS2010 Build.TFS resides on its own server, and i am trying to build to a directory on the same machine. The Server does not have VS2010 installed on it.
When the build runs it fails and gives me this error:
c:\Windows\Microsoft.NET\Framework64\v4.0.30319\Microsoft.Common.targets (1558): Task failed because "AxImp.exe" was not found, or the correct Microsoft Windows SDK is not installed. The task is looking for "AxImp.exe" in the "bin" subdirectory beneath the location specified in the InstallationFolder value of the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Microsoft SDKs\Windows\v7.0A. You may be able to solve the problem by doing one of the following: 1) Install the Microsoft Windows SDK. 2) Install Visual Studio 2010. 3) Manually set the above registry key to the correct location. 4) Pass the correct location into the "ToolPath" parameter of the task.
Then I get a whole bunch of errors saying the namespaces of the project I am building cannot be found. I am not sure if that is all linked to the above mentioned error however.
Thank You!
It is recommended to have Visual Studio 2010 installed on your build machine but it is not a requirement. Since the error message indicates that it didn't find AxImp.exe, can you verify if this file exists on the build machine? The location is C:\Program Files (x86)\Microsoft SDKs\Windows\v7.0A\Bin (if you're on a 64-bit Windows).
If the file doesn't exist, installing .NET Framework SDK will probably help to resolve that specific error.
Regarding installing Visual Studio on the build machine, Visual Studio is licensed per user, not per machine, so as long as the build machine owner is licensed, you should not need extra license for Visual Studio. But you probably should look at the licensing papers for your edition of Visual Studio 2010 to make sure.
Here's a table in the white paper on licensing:
You need to have the same software running on the build server as you would if building locally. This means you need Visual Studio 2010, and possibly even the same edition of Visual Studio 2010, depending on what you're trying to build.
IMPORTANT REMINDER: Visual Studio is licensed PER USER. This means that as long as you as a user have a license, you can use that SAME LICENSE on your build Machine.
The only "problem" would be if you actually had "No licenses" - meaning you do not own a copy of Visual Studio at all, but have a legal copy of TFS.