Issues after installing TFS 2015(Update3) - tfs

Recently I have installed TFS 2015 in DEV environment by restoring the Databases from PROD.
After installing and configuring all the necessary steps in TFS admin console, now I am facing issues. In the TFS web,I am able to see source code but not workitems. when I click on the workitems and settings it throws me an SQL error.
I tried to installed from the scratch and reconfigured databases but I still face the same issues.
Below is the error:
TF246021: An error occurred while processing your request. Technical information (for administrator): SQL Server Error: 1224

Related

"The patch does not apply to Tfs version 14.102.25423.0" when trying to apply the patch 7 on TFS 2015 v4.2

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?

TFS SQL Upgrade Error TF400787: The 'DefaultCollection' cannot be started

I setup a 3 tier TFS preprod environment that includes: an application server, a build server and one database server (SQL Server 2016).
I restored SQL Server databases from the production environment to the preprod environment, installed TFS 2017 on the app server, attached the database and tested successfully.
I then upgraded TFS 2017 to TFS2018 and tested successfully. I restored the databases from SQL Server 2016 to SQL Server 2017, updated compatibility mode on the databases to SQL Server 2017, stopped the collection in preprod environment, edited settings to point to the new SQL Server 2017 instance, clicked Test (which was successful), saved, clicked Start Collection and got an error
TF400787: The host 'DefaultCollection' cannot be started. The servicing needs to be scheduled and completed before the host can be started.
The TFS account I'm using to run TFS Admin Console is a sysadmin on all databases: TFS_Configuration, TFS_DefaultCollection and TFS_Warehouse.
How can I resolve this error and attach "DefaultCollection?"
How can I resolve this error and attach "DefaultCollection?"
The cause of this problem seems to be the loss of data in the database.
Generally, there will be backup database when using tfs or before tfs upgrade. You could use the backup of the databases to restore the database.
Here are the steps to re-configure the TFS:
Step1: Unconfigure the TFSfeature. You could use the "Remove feature" option in Administration console to remove feature or use the TfsConfig setup / uninstall:All
Step2: Restore the database from the backup.
Step3: Configure the TFS again in Administration Console.
In addition, you could go to TFS Administration Console -> the target collection -> Status tab. Then you could find the job that is failed, try to click the Rerun Job button and check the result.
Here is the ticket with a similar issue, you can refer to it

TFS Build failed due to InstallShield Exception

We are using InstallShield 2013 Limited Edition with TFS 2013 Build Server.
Occasionally our tfs XAML builds failed with error:
C:\Program Files (x86)\MSBuild\InstallShield\2013Limited\InstallShield.targets (108): Exception Caught
License of InstallShield 2013 Limited Edition is successfully activated on Build Server Machine(WIN 7 machine).
Due to this error, complete build failed. To fix this, we need to restart tfs build server machine.
Please suggestion some permanent fix for this issue. Let me know if need any additional information.
If you get error saying InstallShield.Tasks.dll was not found or could not be loaded like screenshot below:
Solution:
Set the MSBuild Platform on your Build Definition to “X86” as shown
below:
If you get error saying InstallShield Licence has expired like screenshot below:
Solution:
Set your Build Service to run with a domain account instead of
“NT_AUTHORITY\Network Service”.

TFS 2013 web access errors

Our group recently completed an upgrade from TFS 2010 to TFS 2013 during a server migration. After completing the migration we are unable to use a number of the web-accessable features and get the following error TF51541: The Node ID is not recognized.. I have read a few links where other people have encountered a similar error but have so far been unable to resolve the issue.

TF30279: Plug-in with ID "Microsoft.ProjectCreationWizard.Build" of type "Project Creation Plugins" could not be loaded

When attempting to create a new TFS Team Project from VS2012 I received the following error after pressing finish.
TF30279: Plug-in with ID "Microsoft.ProjectCreationWizard.Build" of type "Project Creation Plugins" could not be loaded
TFS and VS were both installed on a Windows 7 laptop for evaluation. When setting up TFS I configured the build server without error.
In attempting to get round the problem I uninstalled all 2012 components VS, TFS and Sql Server, then reinstalled them. I tried both TFS express and VS2012 for web express and full TFS trial and VS2012 premium trial (to rule out that it wasn't an issue with the express versions)
Each time the error would persist across re-installs.
Although I could not find why the problem has occurred I did eventually manage to fix the issue after reading up on process templates and understanding where the plugin models were sourced from.
1) I opened VS2012 command prompt and ran as admin
2) changed dir to %programfiles%\Microsoft Visual Studio 11.0\Common7\IDE\CommonExtensions\Microsoft\TeamFoundation\Team Explorer
3) ran gacutil /i for each dll in the folder that looked like it was anything to do with build.

Resources